You need to ensure that User1 can add User2 to DLL What…

You have an Exchange Server 2013 organization named fabrikam.com.
You have a distribution group named DL1 and a user named User1. The managedBy attribute of DL1 is
fabrikam.com\\users\\User1.
User1 attempts to add a user named User2 to DL1 and receives the following error message: “Changes to the
public group membership cannot be saved. You do not have sufficient permissions to perform this operation on
this object.”
You need to ensure that User1 can add User2 to DLL
What are two possible ways to achieve this goal? (Each correct answer presents a complete solution. Choose
two.)

You have an Exchange Server 2013 organization named fabrikam.com.
You have a distribution group named DL1 and a user named User1. The managedBy attribute of DL1 is
fabrikam.com\\users\\User1.
User1 attempts to add a user named User2 to DL1 and receives the following error message: “Changes to the
public group membership cannot be saved. You do not have sufficient permissions to perform this operation on
this object.”
You need to ensure that User1 can add User2 to DLL
What are two possible ways to achieve this goal? (Each correct answer presents a complete solution. Choose
two.)

A.
From Exchange Management Shell, run New-ManagementRoleAssignment -Name “Default Role
Assignment Policy- MyDistributionGroupMembership” -Policy “Default Role Assignment Policy” -Role
“MyDistributionGroupMembership

B.
From Exchange Admin Center, edit the Default Role Assignment Policy and select MyDistributionGroups

C.
From Exchange Management Shell, run New-ManagementRoleAssignment -Name “Default Role
Assignment Policy-MyDistributionGroups” -Policy “Default Role Assignment Policy” -Role
“MyDistributionGroups”.

D.
From Exchange Admin Center, edit the Default Role Assignment Policy and select
MyDistributionGroupMembership.

Explanation:
http://technet.microsoft.com/en-gb/library/jj657511(v=exchg.150).aspx
Role Assignment Policies cannot be managed via the EAC.



Leave a Reply 0

Your email address will not be published. Required fields are marked *