Pass the Salesforce Architect Exams Plat-Arch-205 Questions and answers with CertsForce

The Partner Community role hierarchy naturally models the relationship between service agents and their dealer manager. Agents can occupy a lower partner role and the dealer manager a higher role within the same partner account, allowing record visibility to roll upward while users at the same lower level remain isolated from one another under a Private sharing model. This is more efficient than creating a separate sharing rule for every dealer-manager relationship because the management structure itself already expresses who should inherit access. A sharing group is associated with other Experience Cloud access patterns and does not replace the partner role hierarchy for this requirement. The architect should ensure that the partner roles are correctly assigned and that the underlying Case object permissions support the access the manager needs. Study Guide reference: Access to Records - Partner Community roles, external role hierarchy, Private Case sharing, manager access, and scalable Experience Cloud design.

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 finance analyst receives parent implicit access to the Account because she has been granted access to the related Opportunity. Salesforce provides Read Only access to the parent Account when a user has legitimate access to certain standard child records such as Opportunities, Cases, or Contacts. This lets the user understand the customer context of a record the user is authorized to work with. The same rule does not mean that Opportunity access automatically grants visibility to every Contact associated with that Account; Contact access depends on the organization ' s Contact sharing configuration and other applicable access mechanisms. The role hierarchy is also not the cause described here, because the new visibility appears specifically after the Opportunity was shared to the analyst. The scenario is testing standard implicit sharing rather than a deliberately configured sharing rule. Study Guide reference: Access to Records - implicit sharing, parent implicit access, Opportunity-to-Account relationships, standard-object sharing behavior, and Private OWD.

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.

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.