Salesforce Plat-Arch-205 Practice Exam Questions & Answers

Comprehensive and Detailed 150 to 250 words of Explanation From Platform Sharing and Visibility Architect/Course Guide/topics:

A Sharing Set is the standard declarative mechanism for Customer Community users whose Case access can be derived from their Account or Contact relationship. The user's external identity is linked to a Contact and therefore to an Account; the Sharing Set can map that user relationship to the Account relationship on Case and grant access when they match. This is especially appropriate for high-volume external users because it avoids building a conventional role hierarchy merely to express simple account-based access. A normal sharing rule is not the best fit for that license model, and Apex sharing would add code and maintenance even though Salesforce already provides a native relationship-based mechanism. The architect should configure the Sharing Set for the applicable external profile, include Case as the target object, select the appropriate access mapping, and grant only the level of access required. Study Guide reference: Access to Records - Customer Community security, Sharing Sets, high-volume external users, account/contact mappings, and Case access.

Comprehensive and Detailed 150 to 250 words of Explanation From Platform Sharing and Visibility Architect/Course Guide/topics:

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.

Comprehensive and Detailed 150 to 250 words of Explanation From Platform Sharing and Visibility Architect/Course Guide/topics:

The requirement is an authorization requirement, not merely a page-design preference. Removing the Work Order Edit object permission from the Sales Representative permission model prevents those users from updating Work Orders regardless of which UI, API, automation entry point, or page layout they use. Page layouts can make fields appear read-only, but they are presentation controls and should not be relied on as the security boundary. A sharing rule is also the wrong tool because sharing rules add record-level access; they do not reduce the CRUD capabilities a user already has. In a modern Salesforce permission architecture, the organization should remove Edit from the relevant profile or baseline permission set and verify that no other assigned permission set or permission set group grants it back, because permissions are additive. The page can still be configured to present an appropriate read-only experience, but enforcement belongs at the object-permission layer. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - object CRUD, profiles, permission sets, page-layout limitations, and least-privilege authorization.

Comprehensive and Detailed 150 to 250 words of Explanation From Platform Sharing and Visibility Architect/Course Guide/topics:

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.

Comprehensive and Detailed 150 to 250 words of Explanation From Platform Sharing and Visibility Architect/Course Guide/topics:

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.

Comprehensive and Detailed 150 to 250 words of Explanation From Platform Sharing and Visibility Architect/Course Guide/topics:

A file uploaded to Files Home is private by default until it is explicitly shared. Current Salesforce behavior allows the file owner and users with the powerful View All Data permission to access such private files. The ordinary role hierarchy does not automatically expose a private Salesforce File merely because another user is the owner's manager. Files have their own visibility and sharing model and should be evaluated separately from standard business-object sharing. View All Data is a very broad administrative permission and should not be granted merely to solve a file-sharing requirement; this question describes its effect, not a least-privilege recommendation. When collaboration is needed, the appropriate design is to share the file through the supported Salesforce Files mechanisms with the intended people, records, groups, or libraries. Study Guide reference: Access to Other Data - Salesforce Files, Files Home, private files, View All Data, file-sharing semantics, and least privilege.

Comprehensive and Detailed 150 to 250 words of Explanation From Platform Sharing and Visibility Architect/Course Guide/topics:

Among the supplied choices, cloning the Sales Rep profile is the only option that can both grant the pilot functionality and remove legacy functionality for only the selected users. Salesforce permissions are additive: a normal permission set can grant more access, but it cannot negate an existing permission already supplied by the user's profile or another permission set. Option B would revoke legacy access from the shared Sales Rep profile and therefore affect the entire sales population, not just the pilot. Option C can add access to the new application, but a standalone permission set cannot hide functionality that the users already receive elsewhere. In a modern design, permission set groups with muting can provide a more composable persona model, but that architecture is not one of the available choices. For the stated options, the separate profile gives the pilot population an independently controlled baseline. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - profiles, permission sets, additive permissions, pilot access strategies, and permission-set-group concepts.