Plat-Arch-205 Salesforce Certified Platform Sharing and Visibility Architect Free Practice Exam Questions (2026 Updated)

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.

View All Users is the narrowly scoped system permission intended for users who must see every User record regardless of the User object ' s sharing restrictions. That makes it appropriate for an identity and access audit because the team can review user configuration without receiving broad visibility to unrelated business data. View All Data is far more powerful: it bypasses record-level restrictions across the organization and would violate least privilege when the requirement is limited to User setup. The User object also has specialized visibility and sharing semantics, so simply thinking in terms of a generic object-level Read permission does not address the need to bypass restrictive User sharing. The preferred architecture is to grant View All Users through a dedicated permission set assigned only to the identity and access auditors, then remove it when no longer required. Study Guide reference: Access to Other Data - User record sharing, View All Users, identity administration, system permissions, and least privilege.

Read/Write Opportunity Team access allows the team member to edit the Opportunity record, assuming the user also has the necessary object- and field-level permissions. Updating a normal Opportunity field such as Stage therefore falls within the access granted by the team membership. Ownership transfer is a separate privilege and is not automatically granted merely because a user can edit the record. Likewise, being a member of the Opportunity Team does not necessarily give the user authority to add or remove other team members; team administration is controlled by ownership and applicable administrative permissions. This distinction reflects Salesforce ' s layered security model: Opportunity Team membership supplies record access, while object permissions and ownership-related privileges govern what operations the user can perform. The owner always has the broadest control over the Opportunity and can manage collaboration more extensively than an ordinary team member. Study Guide reference: Access to Records - Opportunity Teams, Read/Write access, ownership, team administration, and collaborative sales security.

Partner Community is the appropriate external license model because the distributors participate in a B2B sales process and require Opportunity visibility. Partner-oriented licenses support the external role hierarchy and the sales-object collaboration model needed for channel users such as distributors and resellers. Customer Community is primarily aimed at high-volume customer self-service and does not provide the same Opportunity-oriented partner model. Customer Community Plus adds more advanced sharing than basic Customer Community, but it is not the primary licensing model for external channel sales collaboration. At the scale described, the architect must also design the partner role hierarchy and external sharing model carefully so that one distributor cannot see another distributor ' s records and so that role/group proliferation does not create unnecessary sharing complexity. The license defines the ceiling of what the external user can do; UC must still configure object permissions and record-level sharing to expose only the Opportunities relevant to each distributor. Study Guide reference: Access to Records - Experience Cloud licensing, Partner Community, Opportunity access, partner roles, external sales collaboration, and scalable partner sharing.

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.

The durable design is to anchor the feedback record to the driver for hierarchy purposes, remove the driver ' s object-level Read permission, and allow managers above the driver to inherit record access through the role hierarchy. Ownership by the driver means that when the driver moves to a different manager or branch in the hierarchy, the access path can follow the updated hierarchy instead of remaining tied to a specific former manager. Removing Read permission prevents the driver from opening the Performance Feedback object even though the driver is used as the ownership anchor. Managers are stated to have Read permission, so hierarchy-derived record access can be effective for them. Transferring ownership to the current manager would make the design brittle when management changes, and an additional ownership-based sharing rule is unnecessary when the hierarchy already expresses the upward-access relationship. Study Guide reference: Access to Records - role hierarchy, record ownership, custom-object hierarchy access, object permissions, Private OWD, and management realignment.

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.

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.

External organization-wide defaults are designed for this exact separation of internal and external access. UC can keep the internal default for Delivery at the level required by employees while setting Default External Access to Private for authenticated external users. That creates a restrictive baseline for distributors without reducing internal visibility. Sharing rules are additive: they can open access beyond the organization-wide default, but they cannot take away access already granted by a public OWD. For that reason, neither an owner-based nor a criteria-based rule can be used to make external access more restrictive. After the external OWD is Private, UC can selectively grant the required records through the appropriate Experience Cloud mechanism, such as sharing sets, partner roles, sharing rules, or other supported sharing constructs depending on the relationship model. This follows the least-privilege design principle used throughout Salesforce security architecture: establish the most restrictive baseline that satisfies the broad population, then add narrowly scoped exceptions. Study Guide reference: Access to Records - organization-wide defaults, external OWDs, Experience Cloud record access, sharing rules, and least-privilege sharing.

Private is the correct organization-wide default because at least one population must be prevented from seeing a subset of Account records. Salesforce sharing is additive: once an OWD grants broad access, sharing rules cannot be used to take that access away for a particular group. Starting with Private creates the restrictive baseline needed to keep Prospect Accounts hidden from Service users. UC can then grant Read access to all Accounts for the sales population, let ownership give sales users edit access to their own Accounts, and use the role hierarchy so sales managers inherit the appropriate access to records owned by their team. Service users can receive Read access only to the non-Prospect Accounts through an appropriately designed sharing rule. Public Read/Write or Public Read/Transfer would establish an access baseline that is already broader than the requirements allow and therefore could not be corrected through ordinary sharing rules. Study Guide reference: Access to Records - OWD design, Private baseline, additive sharing, role hierarchy, criteria-based sharing, and least privilege.

Granular Locking is the platform capability associated with reducing group-membership lock contention during large changes to roles, groups, territories, and related sharing structures. A major role hierarchy realignment can cause many concurrent operations to update group membership and sharing tables. Without sufficiently granular locking, unrelated changes can be serialized behind broad locks, increasing the probability of contention and long-running maintenance operations. Granular locking narrows the scope of locks so unrelated hierarchy branches and group structures can be processed more independently where the relationships allow it. Divisions serve a different purpose: they partition data for organizational and reporting needs but do not solve group-membership locking during hierarchy maintenance. Skinny tables are database-performance optimizations and are unrelated to access recalculation. For enterprise-scale realignments, architects should also plan maintenance windows carefully and avoid overlapping major sharing, territory, role, and user-provisioning operations. Study Guide reference: Implications of Security Model Choice - enterprise-scale sharing, role hierarchy maintenance, group-membership locking, granular locking, and access-model performance.

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.

Salesforce Content Deliveries are designed to distribute files externally through generated links and include an option to require a password before the recipient can access the content. That directly satisfies the CISO ' s requirement without adding a third-party product or building an Experience Cloud site solely for file delivery. A content delivery can provide a controlled external URL while the password is communicated separately to the customer. Administrators can also establish organization-level policies for content-delivery password behavior so the security requirement is applied consistently. An Experience Cloud site would introduce identity, licensing, and site-management overhead that is unnecessary when the business simply needs to send a protected file link. The architect should still consider the sensitivity of the content, expiration requirements, and broader information-governance policy when deciding whether content delivery is appropriate for a particular file. Study Guide reference: Access to Other Data - Salesforce Files, Content Deliveries, external file access, password protection, and secure content distribution.

The reporting permissions represented by the answer are Manage Reports in Public Folders and Edit My Reports. Under Salesforce ' s enhanced folder-sharing model, Manage Reports in Public Folders is a broad reporting permission that includes the ability to create and manage public report content and encompasses several lower-level reporting capabilities. The question is testing the permission combination required to create, organize, and share report-folder content with other coaches rather than merely run reports. Architects should still apply least privilege: if a user needs management rights only to one specific folder, granting Manager access to that folder can be safer than assigning an organization-wide reporting management permission. The key distinction is that report-folder permissions govern analytics assets, while access to the underlying business records remains controlled by the normal object, field, and record-security model. Study Guide reference: Access to Other Data - report-folder permissions, enhanced folder sharing, Manage Reports in Public Folders, Edit My Reports, and least-privilege analytics administration.

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.

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.

The valid runtime mechanism among the choices is declaring the Apex class with sharing so Salesforce evaluates record-level sharing when the class queries Shipment records. Because the Shipment OWD is Private, Apex that ignores sharing can expose records outside the user ' s intended visibility. The sensitive Shipment Amount introduces a second security layer: with sharing does not enforce object CRUD or Field-Level Security. The implementation must separately enforce field access, for example with user-mode operations, Security.stripInaccessible(), or valid Schema Describe checks. System.runAs() is useful for tests but does not secure production execution, and isShareable is not a valid Apex sharing keyword. The correct architecture therefore combines record-sharing enforcement with explicit CRUD/FLS enforcement instead of assuming one mechanism protects every layer. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - with sharing, Apex execution context, CRUD/FLS, user-mode operations, and secure Lightning/Apex architecture. 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.

A Default Account Team is designed for sales representatives who repeatedly collaborate with the same internal specialists on customer Accounts. The representative can define recurring team members such as legal, engineering, or finance and specify the access each team member receives to the Account and, where applicable, related Opportunities and Cases. The default team can then be applied automatically to new or transferred Accounts or added to existing Accounts, eliminating the repetitive manual-sharing work described in the scenario. A criteria-based sharing rule is better suited to record access determined by stable record attributes and a fixed audience; it does not model a recurring collaboration team tied to a particular salesperson. View All Data would be dramatically overprivileged because it bypasses record-level controls across the organization. Default Account Teams therefore improve productivity while preserving least privilege and making the collaboration relationship explicit. Study Guide reference: Access to Records - Default Account Teams, team roles, related-record access, collaboration, and least-privilege sharing.

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.