HOTSPOT
You have an Exchange Server 2013 organization that contains 10 mailbox servers. You have a custom
workload management policy named App1Policy. App1Policy is applied to three Mailbox servers.
You deploy a new Mailbox server named EX11. You need to ensure that App1Policy is applied to
EX11. Which command should you run? (To answer, configure the appropriate options in the answer area.)
Answer: 
Explanation:
An Exchange workload is an Exchange Server feature, protocol, or service that’s been explicitly
defined for the purposes of Exchange system resource management.
Each Exchange workload consumes system resources such as CPU, mailbox database operations, or
Active Directory requests to run user requests or background work. Examples of Exchange workloads
include Outlook Web App, Exchange ActiveSync, mailbox migration, and mailbox assistants.
There are two ways to manage Exchange workloads: by monitoring the health of system resources
or by controlling how resources are consumed by individual users (sometimes called user throttling
in Exchange 2010).
Managing workloads based on the health of system resources is new in Microsoft Exchange Server
2013. Controlling how resources are consumed by individual users was possible in Exchange Server
2010, and this capability has been expanded for Exchange Server 2013.
You can customize the workload management settings if you want to change the default behavior of
the feature for the needs of your environment.
SECTION1
Use the Set-ExchangeServer cmdlet to set Exchange attributes in Active Directory for a specified
server.
(EX11)
Not a throttling policy
Scenario details a workload management policy
Use the Set-ResourcePolicy cmdlet to set the properties of a custom resource policy.
SECTION2
The Identity parameter specifies the GUID, distinguished name (DN), or name of the server.Need EX11 as it is the name of the server
SECTION3
The WorkloadManagementPolicy parameter specifies the name of a workload management policy
to apply in Active Directory. (App1Policy)
Not a throttling policy
The correct answer is:
Set-ThrottlingPolicyAssociation -Identity EX11 -ThrottlingPolicy App1Policy
Continue reading if you want to see why
Set-ExchangeServer does not have the WorkloadManagementPolicy parameter so the given answer is incorrect.
https://technet.microsoft.com/en-us/library/Bb123716(v=EXCHG.150).aspx
Set-ResourcePolicy has been deprecated, but I could still find a version in french. (not this answer but if you know french you can read why it’s not…)
https://technet.microsoft.com/fr-fr/library/jj215690(v=exchg.150).aspx
An overview of Workload Management can be found here:
https://technet.microsoft.com/en-us/library/JJ150503(v=EXCHG.150).aspx
Use the Set-ThrottlingPolicy cmdlet to modify the settings for a user throttling policy.(we already have App1Policy so we don’t need this either)
https://technet.microsoft.com/en-us/library/Dd298094(v=EXCHG.150).aspx
Use the Set-ThrottlingPolicyAssociation cmdlet to associate a throttling policy with a specific object.
https://technet.microsoft.com/en-us/library/Ff459231(v=EXCHG.150).aspx
You’ll need two parameters to finish out the command, here is what’s listed on the Identity and ThrottlingPolicy parameters from the above link:
1) The Identity parameter specifies the object to which you want to associate a throttling policy. The object can be a user with a mailbox, a user without a mailbox, a contact, or a computer account.
2) The ThrottlingPolicy parameter specifies the throttling policy that you want to be associated with the object specified by the Identity parameter.
0
0
I am not sure.
When you lookup the Set-ExchangeServer cmdlet, you cannot find the WLM parameter.
But, wen you check the New-WorkloadManagementPolicy, you can see that MS proposed to use Set-ExchangeServer in the examples_
https://technet.microsoft.com/de-de/library/jj215703(v=exchg.150).aspx
Did anybody try to apply such as Res WLM policy?
0
0
I ran these commands in my test lab (Win 2012 R2 – Exchange 2013 SP1 CU10):
[PS] C:\Windows\system32>Set-ExchangeServer -Identity Exc01 -WorkLoadManagementPolicy Test
A parameter cannot be found that matches parameter name ‘WorkLoadManagementPolicy’.
+ CategoryInfo : InvalidArgument: (:) [Set-ExchangeServer], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Set-ExchangeServer
+ PSComputerName : exc01.mydomain.local
Then I tested Hammer’s method:
[PS] C:\Windows\system32>New-ThrottlingPolicy -Name Test -PushNotificationRechargeRatePerDevice 100
Name ThrottlingPolicyScope IsServiceAccount
—- ——————— —————-
Test Regular False
[PS] C:\Windows\system32>Set-ThrottlingPolicyAssociation -Identity Exc01 -ThrottlingPolicy Test
[PS] C:\Windows\system32>
So, my guess: the WorkloadManagementPolicy parameter was part of the original Exchange 2013 but has been removed afterwards:
http://blogs.technet.com/b/ashwinexchange/archive/2012/12/17/3541156.aspx
Looks like an extreme tricky question to me.
Thanks Hammer for pointing that out!
Rgds,
Guy
0
0
Logical when you read the question and think – “You need to ensure that App1Policy is applied to EX11” practically gives you the answer:
Set-ThrottlingPolicyAssociation (applied)
-Identity EX11 (to EX11)
-ThrottlingPolicy App1Policy (App1Policy)
0
0