A client wants to create a custom view-only security role that allows users to view the customer list in the accounts receivable module. You create a security role named Read Only UserAR and add the…

Question

Options

• AAdd the CustCustomerMasterinquire duty to ReadOnlyUserAR.
• BAdd ReadOnlyAR to users.
• CAdd the Customers privilege to CustCustomerMasterinquire.
• DAdd CustomerViewList to ReadOnlyUserAR.
• EAdd the Customers privilege to CustomerViewList.
• FAdd the Customers privilege to the CustCustomer

• A
  11% (3)
• B
  70% (19)
• C
  15% (4)
• F
  4% (1)

Explanation

Dynamics 365 security follows a strict hierarchy: Role → Duty → Privilege → Permission. To build a view-only role for the customer list: (E) The Customers privilege (which grants read access to the customer list) must be added to the custom duty CustomerViewList - this is the lowest-level building block. (D) The custom duty CustomerViewList must then be added to the security role ReadOnlyUserAR - duties are assigned to roles. (B) The role ReadOnlyUserAR must be assigned to users - roles are the final object assigned to users. Option A is incorrect because CustCustomerMasterinquire is an existing standard duty, not the custom one created for this scenario. Option C is incorrect because the Customers privilege should go to the custom duty (CustomerViewList), not the standard duty. Option F is incomplete as written.

No community discussion yet for this question.