You have an Exchange Server 2013 organization that contains a server named EX1. Your network
contains a non-critical internal application that regularly connects to the POP3 Service on EX1. Users

report that Outlook Web App performs more slowly than usual. You discover that EX1 frequently has
a CPU utilization that is greater than 85 percent. You need to configure EX1 temporarily to allocate
more processor resources to Outlook Web App and to allocate less processor resources to POP3.
Which two new policies should you create? (Each correct answer presents part of the solution.
Choose two.)

A.
a throttling policy that sets OWAMaxConcurrency to 25

B.
a workload policy for POP3 that sets the WorkloadClassification to Discretionary

C.
a workload policy for Outlook Web App that sets the WorkloadClassification to Discretionary

D.
a throttling policy that sets PopMaxConcurrency to 25

E.
a workload policy for POP3 that sets the WorkloadClassification to CustomerExpectation

F.
a workload policy for Outlook Web App that sets the WorkloadClassification to
CustomerExpectation

Explanation:
A workload policy
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.
Workload classifications
Each Exchange workload (for example, the Calendar Synchronization Assistant workload), is assigned
a classification.
Workload policy settings are used to group each workload into a class. Classification is used to
control both priority and target resource usage.
Exchange workloads can be assigned one of the following classifications:
Urgent
Customer Expectation
Internal Maintenance
Discretionary
Workloads in a higher classification group are given preference as resource health shows signs of
degrading.
For example, when a resource such as local server CPU reaches high usage, workloads classified as
Internal

Maintenance may continue to run, while workloads classified as Discretionary may be stopped.
NOT A D
A throttling policy is related to Exchange 2010
NOT C
Do not need to allocate less priority to Outlook Web App, but more
NOT E
POP3 is allocated too much resources with a WorkloadClassification of CustomerExpectation
B
Need to allocate less priority to POP3
F
Outlook Web App is allocated the appropriate amount of resources with a WorkloadClassification of
CustomerExpectation