Free Salesforce Certified Platform Sharing and Visibility Architect Plat-Arch-205 Exam Questions

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

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.

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

A sharing rule can extend record-level access only after the user has the fundamental object permission required to use the object. The affected users have no Read permission on Account, so membership in a public group and a sharing rule that exposes inactive Accounts cannot make those records visible. Salesforce evaluates security in layers: the license and object permissions establish whether a user can use an object at all; Field-Level Security controls individual fields; and record-level mechanisms such as OWD, role hierarchy, sharing rules, teams, and manual sharing determine which records are available. A page layout does not grant record or object access, and the position of the Account owner in the role hierarchy is irrelevant when the user's profile prevents Account access entirely. The administrator must first grant appropriate Account Read permission through the profile or a permission set, then allow the sharing rule to determine which Accounts the user can reach. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - object CRUD, profiles, permission sets, interaction between object permission and record sharing, and layered security evaluation.

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 branch requirement combines vertical management access with geographic isolation. The role hierarchy should model the branch reporting structure so branch managers inherit the records available to branch staff, while sharing rules provide controlled exceptions or horizontal access where the hierarchy alone does not express the complete requirement. This is preferable to using Account Teams record by record because the need is systematic across an entire geographic branch, not ad hoc collaboration on selected Accounts. The organization-wide default should remain restrictive enough to prevent cross-branch visibility, but among the supplied choices the combination of Role Hierarchy and sharing rules is the architecture that models both management and regional sharing requirements. The security model should be tested for users in neighboring branches to confirm that no unintended access is introduced. Study Guide reference: Access to Records - Role Hierarchy, geographic access models, sharing rules, Private baseline, branch management, and least-privilege record visibility.

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

The architect must extend the Shield Platform Encryption policy to include the additional supported Account fields and also address the data that already exists. Enabling encryption for a field establishes the policy for the field, but historical values that were stored before the change must be brought into the encrypted state through the platform's data synchronization or re-encryption process. That is why simply waiting for an activation notification is not sufficient to guarantee that every existing value has been encrypted. Classic Encryption is also not a substitute for the Shield Platform Encryption architecture that the organization already uses. The secure implementation treats encryption as a lifecycle concern: select supported fields, activate the policy, ensure key material and tenant-secret management are correct, synchronize existing data, and validate the resulting encryption state. This preserves a consistent enterprise encryption model instead of mixing encryption technologies. Study Guide reference: Access to Other Data - Shield Platform Encryption, encryption policies, key management, existing-data synchronization, field encryption, and data-at-rest protection.

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

A public group is the scalable audience mechanism for list views that should be visible only to a defined set of users. UC can create groups that represent the relevant geography or specialist population and share each list view with the appropriate group instead of trying to maintain visibility user by user. This becomes especially important when there are dozens of list views and frequent personnel changes: administrators update group membership rather than modifying many view definitions. A queue is intended for supported record ownership and workload distribution, not for controlling list-view visibility. Direct sharing to arbitrary individual users is also not the standard list-view model; a public group provides the reusable abstraction when the target audience does not correspond to a single role. The architect must also distinguish visibility of the list-view definition from visibility of the underlying Opportunity records. Sharing a list view does not grant record access; users still see only records permitted by their object permissions, OWD, hierarchy, sharing rules, teams, and other record-level mechanisms. Study Guide reference: Access to Other Data - list-view sharing, public groups, scalable audience management, and separation of view visibility from record access.

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

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.

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

Account Teams are designed to model collaboration around an Account while allowing different access levels to the Account and its related Opportunities and Cases. UC can give the sales associate Read access to the Account, Read access to related Cases, and no general Opportunity access through the team configuration. If the associate later needs access to a particular Opportunity, that record can be opened separately through an Opportunity Team or another appropriate sharing mechanism. Introducing separate Case Teams or sharing rules would duplicate functionality that the Account Team already provides for this collaboration model. The design also preserves the Private OWD, because access is granted only to the users explicitly added to the team. Object permissions still apply independently, so the sales associate must have the required object-level Read permission before the team access can be effective. Study Guide reference: Access to Records - Account Teams, related Opportunity and Case access, team roles, Private OWD, and least-privilege collaboration.

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

A report saved in the user's Private Reports folder is private to that user for ordinary reporting access. The private reports area is not treated like a public folder that can be shared with arbitrary colleagues, and View All Data is not a general bypass that lets another user open and run someone else's private report. This distinction matters because report and dashboard assets have their own folder-security model that is separate from access to the underlying Case records. If the support representative wants other users to consume the report, it should be moved or saved into a report folder that is explicitly shared with the appropriate users, roles, groups, or territories at the required access level. The report owner's ability to see the Cases does not automatically make the report definition available to other people, and broad data permissions should not be substituted for proper folder sharing. Study Guide reference: Access to Other Data - private reports, report folders, enhanced folder sharing, analytics permissions, and separation of report-asset access from record access.

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

Large changes to roles, ownership, OWD, and sharing rules can force Salesforce to recalculate very large numbers of sharing rows. In an organization with a complex hierarchy spanning many regions and countries, that recalculation can become a major operational event. Parallel sharing recalculation is the relevant capability because Salesforce can process eligible portions of the sharing recalculation workload concurrently instead of treating the entire job as one serial operation. Divisions are primarily a data-partitioning and reporting feature; they do not optimize access recalculation. Skinny tables are database-query performance structures and likewise do not address the sharing model. The architect should also recognize that Account sharing changes can cascade into related Contacts, Opportunities, and Cases through implicit sharing relationships, increasing the scale of the work. Major hierarchy and ownership reorganizations therefore require planned maintenance, monitoring of background sharing jobs, and a design that limits unnecessary complexity in the role and group model. Study Guide reference: Implications of Security Model Choice - enterprise-scale sharing, hierarchy changes, ownership realignment, parallel recalculation, and sharing performance.