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

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.

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.

Salesforce can make a custom list view visible to a role and its internal subordinates, which is appropriate when the intended audience already aligns with the role hierarchy. Using that audience avoids maintaining dozens of list views against individual users and allows the hierarchy to represent the geographic or organizational population naturally. A queue is intended for supported record ownership and workload distribution, not for governing list-view visibility. Direct sharing to arbitrary individual users is also not the standard list-view model; when the population does not correspond to a role, a public group is typically the better abstraction. The architect must distinguish list-view visibility from record visibility: being able to select a view does not grant access to the Opportunities that satisfy its filter. Each user still sees only records allowed by object permissions, OWD, hierarchy, sharing rules, teams, and other record-level mechanisms. Study Guide reference: Access to Other Data - list views, roles and internal subordinates, public groups, scalable view administration, and separation of view access from record access.

A public group provides the cleanest reusable security boundary for report and dashboard folder access. UC can create a Sales Managers public group and maintain the appropriate managers as members, then grant that group the required folder access. Folder sharing remains attached to the group instead of being maintained user by user, which removes the recurring monthly administration described in the scenario. Enhanced folder sharing supports audiences such as users, roles, territories, and public groups, with the folder access level determining whether members can view, edit, or manage the content. Profiles are not the normal sharing target for public report and dashboard folders, so changing a profile does not solve the folder-membership problem. The role hierarchy also should not be treated as though folder access automatically rolls upward in the same way as record access. Folder security is a separate authorization layer. Public groups are particularly effective when a functional population must receive identical access even though membership changes over time. Study Guide reference: Access to Other Data - report and dashboard folders, enhanced folder sharing, public groups, analytics permissions, and scalable administration.

The requirement cuts horizontally across a role hierarchy that is intentionally organized by country, so the solution belongs in the sharing-rule layer rather than in a redesign of the hierarchy. A sharing rule can open the relevant Accounts to sales managers in other countries without collapsing distinct regional roles. Among the supplied choices, the owner-based sharing-rule option represents the correct architectural family. If the business condition is literally based on an Account Segment field, a criteria-based sharing rule would be the more precise Salesforce mechanism because criteria-based rules select records by field values whereas owner-based rules select records by the owner ' s role or group. A permission set cannot grant access to selected Account records, and a public group contains users rather than Account records. Putting U.S. and Canadian managers in the same role would not cause peers to inherit one another ' s records and would distort the hierarchy ' s organizational meaning. Study Guide reference: Access to Records - cross-hierarchy sharing, owner-based versus criteria-based rules, roles, public groups, and record-level access.

The users can open the Invoice record, which proves that object and record access are already sufficient to reach the record. The fact that only a small set of system fields is visible while the administrator sees the full detail strongly indicates a Field-Level Security difference. If the Sales Users profile lacks visibility to the remaining fields, Salesforce suppresses those fields even though the page layout contains them. A page layout marked Read-Only would still display the fields; it would only prevent editing. A role-based sharing rule also cannot grant field visibility because sharing rules operate at the record level. The correct troubleshooting path is therefore to review the Invoice object ' s field permissions for the affected profile and any assigned permission sets, using Field Accessibility where useful to understand the effective result. The scenario reinforces that object permission, record sharing, and Field-Level Security are separate controls and must be diagnosed independently. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - Field-Level Security, field accessibility, profiles, permission sets, and separation of field security from record sharing.

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.

Public Read-Only is the correct Lead OWD because it balances duplicate prevention with ownership-based editing. Users can see existing Lead records across the organization, which helps them identify whether a prospect already exists before creating another Lead, but they cannot edit another user ' s Lead merely because they can view it. A Private OWD would protect ownership more strictly but would undermine the duplicate-reduction objective because users might not be able to discover Leads owned elsewhere. Public Read/Write/Transfer would go too far in the opposite direction by allowing broader modification or reassignment than the requirement permits. The organization can complement the OWD with Duplicate Rules and Matching Rules for stronger prevention and warning behavior, but the OWD still establishes the right record-visibility baseline. Study Guide reference: Access to Records - Lead OWD, Public Read-Only, record ownership, duplicate prevention, and least-privilege access. 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.

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 field is unavailable because an encrypted field cannot be used directly as the criterion in a criteria-based sharing rule. This is a platform limitation arising from the security properties of encrypted data, not a consequence of the architect ' s personal Field-Level Security. Granting the administrator more visibility to the field therefore would not make the field eligible for sharing-rule criteria. The design implication is important: encryption can affect downstream functionality such as filtering, searching, deterministic comparisons, reporting, and sharing-rule logic. If UC needs sharing behavior related to the sensitive Social Security Number, the architect should avoid duplicating the plaintext value merely to bypass the restriction. A safer design is to use a non-sensitive classification, segment, status, or derived security indicator that expresses the business condition without exposing the protected identifier. The encryption decision and the sharing design must therefore be considered together rather than independently. Study Guide reference: Implications of Security Model Choice - Shield Platform Encryption limitations, criteria-based sharing, sensitive-data architecture, and security design trade-offs.