Correct Answer:
Explanation/Reference:
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
Set-ExchangeServer: Exchange 2013 Help