PLAT-ADMN-202 practice question 10 of 35

A Service Coordinator (SC) for Ursa Major Solar (UMS) does a final review of work orders owned by a technician for a specific region before the…

Full set: 311 questions

Domain Configuration and Setup

A Service Coordinator (SC) for Ursa Major Solar (UMS) does a final review of work orders owned by a technician for a specific region before the records are submitted for an invoice. Beforeclosing out the work order, the SC needs to modify data or remove attachments that were added by mistake. The SC also needs access to any other related records owned by the technician. What solution would provide the required access, given a private data model?
Answer options
A: Give the SC a permission set with the Modify All Data system permission.
B: Put the SC in the role hierarchy above the technicians whose work orders they review. Correct answer
C: Create a workflow rule that updates records owned by technicians in that regionwith the SC.
D: Change work order access on the SC's profile to 'Modify AIl.
Correct Answer:
B. Put the SC in the role hierarchy above the technicians whose work orders they review.
Explanation

In a private sharing model, the role hierarchy is the standard mechanism for granting managers or supervisors vertical access to records owned by their subordinates. Placing the Service Coordinator (SC) in a role above the technicians ensures the SC can view, edit, and report on all records owned by those technicians, including work orders and other related records. This solution directly addresses the need to modify data and access related records owned by the technicians without granting excessive, org-wide permissions, thus adhering to the principle of least privilege.

Why Incorrect

A. Give the SC a permission set with the Modify All Data system permission. This permission grants access to all data in the entire organization, which is excessive and violates the principle of least privilege. The requirement is limited to a specific region's technicians.
C. Create a workflow rule that updates records owned by technicians in that region with the SC. Workflow rules automate processes like field updates or sending emails; they are not a mechanism for granting record access or managing visibility in the sharing model.
D. Change work order access on the SC's profile to 'Modify All'. This grants access to all work order records, not just those of the specific technicians. It also fails to provide access to "any other related records owned by the technician."

References

1. Salesforce Help, Control Access Using Hierarchies: "The role hierarchy enables users above another user in the hierarchy to have the same level of access to records owned by or shared with the users below them. ... For most objects, you can disable this access for a specific object in your organization’s sharing settings." This confirms that placing the SC above the technicians grants the required access.

2. Salesforce Security Guide, Page 11, "Access Control": "The role hierarchy gives managers access to their direct reports’ data. For example, a sales vice president can see the records of all the sales managers, and the sales managers can see the records of all their sales reps." This document explicitly states the primary function of the role hierarchy aligns with the scenario.

3. Salesforce Help, Object Permissions: "Modify All: View, edit, delete, transfer, and approve all records of a specific object type, regardless of sharing settings." This explains why option D is incorrect, as it grants access to all work orders, not just the subordinates', and doesn't cover other related objects.

4. Salesforce Help, System Permissions: "'Modify All Data' permission: Create, edit, and delete all organization data, regardless of sharing settings." This highlights why option A is overly permissive for the stated requirement.

Scroll to Top