Plat-Arch-205 Exam Questions & Answers

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

Salesforce provides parent implicit sharing for several standard Account relationships. When a user has access to an Opportunity, Case, or Contact, Salesforce can grant Read Only access to the related parent Account so the user can understand the business context of the child record. In this scenario, the sales representative owns the Opportunities, so the representative has direct access to those records and receives implicit Read access to the parent Account even though the Account OWD is Private. That implicit access does not grant Account edit rights. Create/Edit permission on Opportunity determines what the user can do to Opportunity records; it does not translate into Create or Edit access on Account. Object permissions and record access must still be evaluated independently. This behavior is native to standard relationships and should not be confused with a manually created sharing rule. The important exam distinction is that child-record access can produce limited parent visibility, but the inherited access is Read Only unless another mechanism grants more. Study Guide reference: Access to Records - implicit sharing, parent implicit access, Account/Opportunity security, record ownership, and OWD interaction.

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

A Salesforce File posted to a record inherits visibility from the record context according to the file-sharing configuration. The file owner retains access, and users who can access the associated record can generally access the file at the level permitted by the file's visibility settings. The object's Private OWD therefore matters because only users who obtain access to the specific record through ownership, hierarchy, teams, sharing rules, or another valid mechanism fall within the record audience. A shared Chatter post link does not by itself bypass the underlying record and file security model. Architects should treat file security as a related but distinct layer: the ContentDocument and ContentDocumentLink model determines where a file is shared, while record access and file visibility determine who can actually open it. Study Guide reference: Access to Other Data - Salesforce Files, record-associated file visibility, Chatter feeds, ContentDocument access, and record sharing. 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:

Salesforce supports experience-specific standard-action overrides, so the Case Edit action can be customized for the Salesforce mobile app while the desktop Lightning Experience continues to use the standard page. That directly satisfies the requirement to add image capture for field consultants without retraining the large desktop service population or replacing their existing Lightning pages. A mobile-specific Lightning component override keeps the customization localized to the form factor that needs it and maximizes reuse of standard platform behavior elsewhere. Creating a separate Edit in Mobile button would introduce a parallel workflow that users must remember and maintain. Overriding the desktop Lightning Experience and then detecting form factor in code would be more complex still: it would add routing logic, testing surface, and code merely to reproduce the existing desktop behavior. The architectural preference is to constrain customization to the user experience that actually needs it and avoid custom code when standard Salesforce configuration can isolate the behavior cleanly. Study Guide reference: Implications of Security Model Choice - Lightning action overrides, mobile versus desktop behavior, reusable components, maintainability, and declarative-first design.

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:

For custom objects, a dedicated Apex Sharing Reason should be used when programmatic shares must survive a change of record owner. Apex-managed shares that use a custom sharing reason are designed to represent access granted by business logic independently of ownership. A share created with RowCause Manual is different: manual shares can be removed when ownership changes, so they are not reliable for persistent application-managed access. The with sharing keyword also does not control the persistence of share-table rows; it controls whether Apex respects the current record-sharing model when executing queries and DML. A custom sharing reason has an additional operational advantage because it gives the application a stable way to identify, update, or remove only the shares created for that business process. Study Guide reference: Access to Records - Apex-managed sharing, Apex Sharing Reasons, RowCause, ownership changes, and custom-object share lifecycle. 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.