You have an Exchange Server 2013 organization that contains five servers. Your company has a
finance department, a marketing department, and a research department. Users in the marketing
department are prevented from creating more than two Exchange ActiveSync device associations.
You have a user named User5 in the finance department. You need to prevent User5 from creating
more than two Exchange ActiveSync device associations. Which cmdlet should you use?
A.
Set-ThrottlingPolicyAssociation
B.
Set-ResourcePolicy
C.
Set-ActiveSyncMailboxPolicy
D.
Set-CASMailbox
Explanation:
The Set-ResourcePolicy cmdlet sets the performance thresholds for a resource policy. If you don’t set
a value for a workload classification, the value remains at the default level.
Note:
* Exchange workloads are managed by default workload management policy settings that are
installed during Exchange Server 2013 Setup.
* An Exchange workload is an Exchange server feature, protocol, or service that has 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 Managed Folder Assistant.Incorrect:
Not A: Use the Set-ThrottlingPolicyAssociation cmdlet to associate a throttling policy with a specific
object. The object can be a user with a mailbox, a user without a mailbox, a contact, or a computer
account.
The Set-ThrottlingPolicyAssociation cmdlet defines quota limits for specific objects. For example, if
you notice that a user or other object is using excessive bandwidth, you can associate that object
with a throttling policy that’s more restrictive.
wrong
0
0
Safe to say the answer is “A”?
Since a policy exists to limit the Marketing group to 2 device associations, you can associate the same policy to User5.
0
0
I think it’s A
0
0
A (set-throttlingpolicyasociation) is the correct answear, her are some lines from technet about throttling 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.
You manage Exchange workloads by controlling how resources are consumed by individual users (sometimes called user throttling in Exchange 2010). Controlling how Exchange system resources are consumed by individual users was possible in Exchange Server 2010, and this capability has been expanded for Exchange Server 2013.
0
0