Salesforce Plat-Arch-205 Exam Questions

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

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.

===============

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

Field-Level Security is the authoritative mechanism because Banking Reps must be able to see the Date of Birth value while Customer Support Reps must additionally be able to edit it. Configuring the field as Visible but Read-Only for Banking Reps and Visible/Edit for Customer Support Reps enforces the requirement across Salesforce interfaces rather than only on one page. Search layouts and page layouts are presentation controls; they cannot override restrictive FLS and should not be used as the sole security boundary. A validation rule tied to a profile name would be brittle, would not address field visibility, and would embed authorization logic in a business rule that becomes difficult to maintain. The architect should implement the field permissions through the organization's profile/permission-set strategy and verify that no other permission set grants unintended edit access. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - Field-Level Security, search visibility, read-only fields, profiles, permission sets, and enforceable field authorization.

===============

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

The decisive requirement is that temporary deal access must expire automatically at a known future date. Salesforce sharing mechanisms such as manual or Apex-created shares can grant the temporary access, but a standard share entry does not carry an automatic expiration date. A Scheduled Apex job can therefore implement the lifecycle requirement by running after the specified fiscal-year date and removing only the temporary shares that were created for this collaboration program. Apex sharing by itself describes how access could be granted but not how it expires, while a sharing rule is population-based and is poorly suited to temporary per-deal collaboration with individual expiration. A production design should mark the temporary grants in a reliable way so the scheduled process removes only those shares and leaves ownership, hierarchy, teams, and unrelated sharing intact. Study Guide reference: Access to Records - temporary record sharing, Apex/manual shares, scheduled revocation, share lifecycle, and least-privilege collaboration.

===============

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

For custom objects, Salesforce allows the administrator to disable automatic upward access through the role hierarchy by clearing Grant Access Using Hierarchies. With the NPS object's OWD set to Private and hierarchy access disabled, a manager does not gain access simply because the manager occupies a role above the record owner. This is the correct pattern for sensitive employee information when the reporting hierarchy itself must not imply visibility. Apex sharing should not be used to subtract access that is granted by another mechanism; Salesforce sharing is fundamentally additive. Removing all object permissions from managers would be too broad because it would block every NPS record, including records a manager might legitimately need through another explicit authorization process. The secure design establishes a restrictive baseline and then opens only the records that a specific business requirement justifies. Study Guide reference: Access to Records - Private OWD, Grant Access Using Hierarchies, custom-object hierarchy behavior, sensitive-record isolation, and least-privilege sharing.

===============

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

Price Books use specialized access semantics rather than the same generic sharing pattern as ordinary business objects. The High Risk Price Book should be the authorization boundary for the sensitive product catalog. UC can maintain broad View Only access where users need to inspect pricing while explicitly sharing the High Risk Price Book with trained staff at the level required to use it during the Opportunity sales process. Users need appropriate Price Book use access to select that Price Book and add its products to an Opportunity. This approach keeps the high-risk product entitlement centralized in the pricing catalog instead of trying to enforce it through page layouts, validation rules, or a broad Opportunity permission. Standard sharing rules are not the normal way to express this Price Book access model, and a solution that grants the entitlement to all sales users would violate the requirement. The architecture should pair the specialized Price Book access with normal Opportunity and Product permissions so only the trained population can transact with the restricted products. Study Guide reference: Access to Other Data - Price Book security, View Only, Use access, product visibility, pricing governance, and least-privilege sales access.

===============