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

Because Invoice is the detail side of a master-detail relationship to Account, its record-level access is controlled by the master. In Salesforce this is effectively a Controlled by Parent model: users can reach the detail record only to the extent that they can reach the associated master record, assuming they also have the necessary object permission on the detail object. The AR users have no access to the relevant Accounts, so they cannot discover or open the dependent Invoice records in list views, reports, or Global Search. Creating a sharing rule directly on the master-detail child does not solve the underlying access problem because the child does not maintain an independent sharing model in the same way as an independently owned record. The required access must therefore be established at the Account level; once the relevant Accounts are shared to AR, the dependent Invoice records become available according to the parent relationship. Study Guide reference: Access to Records - master-detail relationships, Controlled by Parent, OWD, inherited record access, and sharing at the master record.

This is an ownership data skew problem. Salesforce sharing performance degrades when a single user or queue owns an excessively large number of records of the same object because ownership is deeply involved in sharing calculations, role changes, group membership evaluation, transfers, and other access operations. A common design guideline is to avoid concentrating more than roughly ten thousand records of one object under a single owner when possible. Here, each donations representative owns more than fifty thousand donor Accounts, well beyond that threshold, and the organization has more than twenty million members overall. The problem is therefore structural, not simply a one-time recalculation event or an incorrect permission assignment. The architect should distribute ownership more evenly and, where concentration cannot be avoided, keep heavily skewed owners out of unnecessary roles and groups to reduce sharing complexity. Study Guide reference: Implications of Security Model Choice - ownership data skew, enterprise-scale sharing, Account ownership, role/group participation, and sharing 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.

Among the supplied choices, cloning the Sales Rep profile is the only option that can both grant the pilot functionality and remove legacy functionality for only the selected users. Salesforce permissions are additive: a normal permission set can grant more access, but it cannot negate an existing permission already supplied by the user ' s profile or another permission set. Option B would revoke legacy access from the shared Sales Rep profile and therefore affect the entire sales population, not just the pilot. Option C can add access to the new application, but a standalone permission set cannot hide functionality that the users already receive elsewhere. In a modern design, permission set groups with muting can provide a more composable persona model, but that architecture is not one of the available choices. For the stated options, the separate profile gives the pilot population an independently controlled baseline. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - profiles, permission sets, additive permissions, pilot access strategies, and permission-set-group concepts.

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.

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 security defect is field-level write authorization, not record-level sharing. Apex can execute with elevated behavior, so code that performs DML must explicitly respect whether the running user is allowed to update the fields being changed. The Schema Describe check represented by isUpdateable() verifies field update permission before DML and directly addresses the Read-Only Field-Level Security condition in the scenario. By contrast, the with sharing keyword controls record visibility through the sharing model; it does not itself enforce object CRUD or Field-Level Security. Moving the same logic into another with sharing class therefore would not stop a field from being updated when the user lacks field edit permission. In modern Salesforce development, user-mode database operations and Security.stripInaccessible() can provide broader and often simpler enforcement of CRUD and FLS, but the explicit isUpdateable() check remains technically valid for the option set given. The architectural rule is to evaluate object permissions, field permissions, and record sharing as separate layers. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - CRUD, Field-Level Security, secure Apex, Schema Describe checks, and user-mode operations.

Partner users do participate in an external role hierarchy, but the hierarchy available under a partner account is limited. Salesforce supports a maximum of three partner role levels, commonly represented as Partner User, Partner Manager, and Partner Executive. The affiliate ' s requested structure contains four external management layers, so it cannot be represented one-for-one using four separate partner roles. This matters because the business wants vertical visibility: sales representatives should remain isolated from peers, while higher levels should inherit access to opportunities owned by users beneath them. The partner role hierarchy can support that pattern only within its available depth. The architect must therefore collapse or redesign one organizational level, supplement the hierarchy with another sharing mechanism, or determine whether every management title actually requires a distinct Salesforce role. In large Experience Cloud implementations, minimizing external role proliferation is also important because every partner account can add groups and sharing complexity. Study Guide reference: Access to Records - Experience Cloud, partner roles, external role hierarchy, role-depth limits, partner record visibility, and external sharing scalability.

The requirement is limited to one object and requires universal visibility without edit access, so the least-privilege solution is a permission set that grants View All Records for Opportunity. View All Records bypasses record-sharing restrictions for that object only. View All Data is much broader because it bypasses sharing across essentially all objects, which would conflict with UC ' s privacy principle and expose more information than the reporting team needs. A permission set is preferable to changing a broad profile when only a few users require the elevation because it can be assigned and removed independently. View All Records does not itself grant edit permission; object CRUD and Field-Level Security still control what users can change and which fields they can access. This preserves the rest of the security model while ensuring the reporting team can see every Opportunity. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - View All Records, View All Data, permission sets, sharing overrides, and least privilege.

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.

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.

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.

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.

Deferred Sharing Calculation is intended for major administrative changes that would otherwise cause Salesforce to repeatedly recalculate sharing while the organization is still in an intermediate state. During a large role hierarchy restructuring and mass Account ownership realignment, each individual change can affect group membership and record access. With deferred calculation enabled, administrators can suspend automatic calculation while they perform the planned restructuring and then explicitly resume and recalculate after the final model is in place. This reduces repeated work and can materially improve the operational stability of a very large reorganization. The capability must be governed carefully because access changes made while calculation is suspended are not reflected until the recalculation is completed. Skinny tables solve a different database-performance problem, and Divisions partition data but do not prevent repeated sharing recalculations. Study Guide reference: Implications of Security Model Choice - Deferred Sharing Calculation, large organizational changes, role and ownership maintenance, sharing recalculation, and operational governance.

A Public Group is the standard reusable container for users who need common record access but do not share a natural position in the role hierarchy. Public groups can include individual users, roles, roles with subordinates, and other groups, then be referenced by sharing rules or manual sharing. The role hierarchy is intended for vertical access based on organizational responsibility, so forcing unrelated users into one role would distort the security model. Sharing Sets serve a different purpose: they are relationship-based Experience Cloud mechanisms that map an external user ' s Account or Contact relationship to target records. For unrelated internal users, the architect should create a public group and then use that group as the recipient in the appropriate sharing mechanism. This centralizes membership management and lets the record-sharing rule remain stable even as individual users change. Study Guide reference: Access to Records - Public Groups, sharing-rule recipients, cross-functional access, role hierarchy, and scalable record-sharing design.

View All Records is an object-specific sharing override. Granting View All on Case lets the service representative see every Case regardless of the Case OWD, but it does not automatically grant the same access to Account or other related standard objects. Each object still requires its own object permission and record-access path. This is an important distinction from normal implicit sharing: Salesforce does not treat a broad View All grant on the child object as though the user had individually received each child record through ownership or a normal share, so the expected parent access must be evaluated separately. If Contact is Controlled by Parent, Contact visibility depends on the user ' s access to the parent Account. The architect must therefore design Account access explicitly rather than assuming that universal Case visibility cascades through the customer data model. Study Guide reference: Access to Records - View All Records, object-specific sharing overrides, Account/Case relationships, Controlled by Parent, and Private OWD.

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.

The custom Apex layer is responsible for enforcing Salesforce security; the Lightning component does not automatically make server-side data access safe. The valid runtime control among the choices is the Apex security mechanism that checks or enforces the user ' s access before data is returned or changed. Field-Level Security must be respected for sensitive values such as Shipment Amount, and the record-sharing model must also be enforced so a Private OWD is not bypassed. Schema Describe checks such as isAccessible(), isCreateable(), and isUpdateable() can be used for explicit field and object permission checks. Current secure-Apex patterns also include user-mode database operations and Security.stripInaccessible(), which can enforce or sanitize CRUD/FLS more comprehensively. Record visibility is a separate layer and should be preserved with the appropriate sharing context. System.runAs() is a testing facility, not a production authorization mechanism, and isShareable is not a valid Apex security keyword. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - secure Apex, CRUD/FLS, record-sharing enforcement, user-mode operations, and Lightning/Apex security boundaries.

Dynamic Forms is the declarative solution for adapting record presentation without replacing the standard Salesforce page with custom Visualforce or Lightning code. It allows administrators to place fields and field sections individually on a Lightning record page and apply visibility rules based on record context or supported device conditions. That is a better fit for form-factor and alignment problems than maintaining custom view-action overrides that detect devices and route users to different layouts. The declarative approach reduces code ownership, regression risk, testing effort, and long-term maintenance while preserving the standard Salesforce record experience. Where the requirement is driven by record type, the same mechanism can show different field sections for different business processes. The architect must still remember that Dynamic Forms controls presentation rather than security: fields that are hidden by component visibility can still be available through reports, list views, APIs, or other interfaces if Field-Level Security grants access. Sensitive information therefore still requires proper FLS. Study Guide reference: Implications of Security Model Choice - Dynamic Forms, Lightning App Builder, component visibility, record types, device form factors, maintainability, and UI visibility versus security.

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.

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.

A PDF stored in a private library is intended to remain private to the file owner until it is deliberately shared or published through another supported context. Salesforce Files does not automatically use the ordinary business-record role hierarchy to expose a private file to managers above the owner. The private-library boundary therefore differs from standard object sharing, where role hierarchy can provide upward access. If collaboration is required, the user should share the file with the appropriate people, group, record, or library rather than relying on hierarchy inheritance. This question tests the fact that file visibility has its own security model and should be evaluated separately from record-level OWD and role hierarchy. The organization should also avoid granting broad system permissions merely to solve an individual file-sharing requirement. Study Guide reference: Access to Other Data - Salesforce Files, private libraries, file ownership, file-sharing contexts, and distinction between file security and record security.