Plat-Arch-205 Exam Dumps - Salesforce Certified Platform Sharing and Visibility Architect

The relevant Experience Cloud capability is Super User access, which gives selected external users broader visibility to records belonging to other users associated with the same external account. For Customer Community Plus, the modern terminology commonly used is Portal Super User; the answer choice uses the broader or legacy Partner Super User wording, but it represents the same architectural concept being tested. Delegated external-user administration focuses on managing external users rather than granting broad same-account Case visibility, and a generic community-administration permission is not the record-sharing mechanism required. Super User access should be assigned only to carefully selected agents because it materially expands what they can see within the distributor account. The organization ' s external OWD can remain restrictive between distributors while the elevated user receives the intended same-account visibility. Study Guide reference: Access to Records - Customer Community Plus, Super User access, same-account Case visibility, external-user administration, and Experience Cloud least privilege.

A Public Group is the standard reusable container for users who need common record access but do not share a natural position in the role hierarchy. Public groups can include individual users, roles, roles with subordinates, and other groups, then be referenced by sharing rules or manual sharing. The role hierarchy is intended for vertical access based on organizational responsibility, so forcing unrelated users into one role would distort the security model. Sharing Sets serve a different purpose: they are relationship-based Experience Cloud mechanisms that map an external user ' s Account or Contact relationship to target records. For unrelated internal users, the architect should create a public group and then use that group as the recipient in the appropriate sharing mechanism. This centralizes membership management and lets the record-sharing rule remain stable even as individual users change. Study Guide reference: Access to Records - Public Groups, sharing-rule recipients, cross-functional access, role hierarchy, and scalable record-sharing design.

Public Read-Only gives John baseline Read access to every Account, but it does not let him edit Paul ' s Account. When Paul manually grants John Edit access, Salesforce adds an explicit AccountShare entry representing that exceptional access. The new share has a Manual row cause and a Read/Write access level; it does not transfer ownership and it does not convert the existing OWD-derived access into an owner share. Salesforce evaluates all applicable access mechanisms and gives the user the highest effective access, so the explicit manual share raises John ' s effective access on that record from Read Only to Read/Write. The design illustrates the additive nature of Salesforce record security: OWD establishes the baseline and explicit shares can open a specific record further. Ownership remains with Paul, and the manual share should be used only where a deliberate exception to the baseline is required. Study Guide reference: Access to Records - manual sharing, AccountShare, RowCause, OWD, additive record access, and effective access calculation.

The record must be shared with a dynamically determined user: the manager of the person identified on the Case. A criteria-based sharing rule can evaluate Case fields, but its recipient is a fixed role, group, or other supported target; it cannot resolve a different manager for every record and share only to that person. Programmatic sharing is therefore the appropriate pattern. A trigger can inspect the Legal SME or complaint-agent field, determine the required manager or specialist, create the corresponding Case share, and remove or replace that share when the relationship changes. Making the subject of the complaint the owner would expose the sensitive Case to exactly the person who must not see it, while removing Case object permission from the entire support-agent population would be far broader than required. The design should keep the Case baseline restrictive and grant access only to the HR owner plus the dynamically determined authorized user. Study Guide reference: Access to Records - programmatic Case sharing, dynamic recipients, user lookup relationships, sensitive-record isolation, and least privilege.

Apex-managed sharing gives the development team substantial control over who receives record access, so it must be tested from the perspective of different users. System.runAs() is the appropriate test technique among the choices because it allows the test to execute sharing-sensitive behavior under representative user contexts and verify both positive and negative access outcomes. The test suite should include users who are supposed to receive access and users who must remain restricted, then confirm that the managed share entries produce exactly the intended visibility. A keyword such as without sharing would weaken record enforcement rather than validate it, and with sharing does not enforce Field-Level Security. In production code, record sharing, object CRUD, and FLS still have to be handled as separate concerns; runAs() simply provides a reliable way to exercise user-context behavior in tests. Study Guide reference: Access to Records - Apex-managed sharing, System.runAs(), Private OWD, user-context testing, and validation of least-privilege access.

The requirement follows a direct manager-to-subordinate relationship, so the role hierarchy is the native record-access mechanism. By placing the operations users below the operations manager and enabling Grant Access Using Hierarchies for the custom Scheduled Course object, Salesforce can automatically provide the manager access to records owned by those subordinate users. The manager must also have the necessary object-level Edit permission because hierarchy access cannot create object capability that the user lacks. A public group alone does not share records; it is simply a reusable collection that must be referenced by another sharing mechanism. An ownership-based sharing rule could create access, but it would duplicate a relationship already expressed by the hierarchy and add unnecessary maintenance across hundreds of regions. Study Guide reference: Access to Records - Role Hierarchy, Grant Access Using Hierarchies, custom-object sharing, manager access, and object permissions. The implementation should also be validated with representative users so effective permissions, sharing inheritance, and any cross-object access behave exactly as designed before production release.

Mary has no effective access because object-level Read permission is a prerequisite for every record-level access mechanism. Public Read-Only OWD and the role hierarchy can determine which Invoice records a user may see only after the user is authorized to read the Invoice object itself. Mary ' s profile does not grant that permission, so neither the public OWD nor her position above Joe can make Joe ' s Invoice records available. Record sharing never substitutes for object CRUD. This is a core Salesforce security-order concept: object permissions establish whether a user can use an object, Field-Level Security determines which fields are available, and OWD, hierarchy, sharing rules, teams, and manual sharing determine which records are visible. Granting Read through a profile or permission set would be required before Public Read-Only or hierarchy-derived access could take effect. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - object CRUD, profiles, permission sets, OWD interaction, role hierarchy, and layered security evaluation.

Custom Apex that serves a Lightning component must not assume that the client-side component has already enforced the user ' s data access. Apex can execute in system context, so the development team must explicitly preserve record visibility and enforce the user ' s CRUD and Field-Level Security where appropriate. The record-level requirement can be handled with the correct sharing declaration or user-mode operations, while object and field authorization can be enforced through user mode, Security.stripInaccessible(), or valid Schema Describe checks. Creating runAs tests is valuable for verification but does not secure production execution. Likewise, method names such as isShareable are not valid substitutes for the platform ' s real security APIs. The architectural principle is to treat the LWC-to-Apex boundary as a server-side trust boundary: every Apex entry point should return only records and fields that the running user is entitled to access. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - system-mode Apex, record-sharing enforcement, CRUD/FLS, user-mode operations, and Lightning/Apex security boundaries.