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

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.

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.

For custom objects, a dedicated Apex Sharing Reason should be used when programmatic shares must survive a change of record owner. Apex-managed shares that use a custom sharing reason are designed to represent access granted by business logic independently of ownership. A share created with RowCause Manual is different: manual shares can be removed when ownership changes, so they are not reliable for persistent application-managed access. The with sharing keyword also does not control the persistence of share-table rows; it controls whether Apex respects the current record-sharing model when executing queries and DML. A custom sharing reason has an additional operational advantage because it gives the application a stable way to identify, update, or remove only the shares created for that business process. Study Guide reference: Access to Records - Apex-managed sharing, Apex Sharing Reasons, RowCause, ownership changes, and custom-object share lifecycle. 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 Presenters junction object expresses a dynamic user-to-record relationship: each Presentation has a different set of users who must be able to edit it, and that set can change over time. Apex-managed sharing is appropriate because a trigger on the junction object can create a share when a presenter is added and remove that access when the relationship is deleted or changed. The Presentation object ' s OWD can remain Private while only the users represented by the junction records receive the necessary Edit access. A permission set cannot grant access to one specific Presentation record; it supplies object, field, or system permissions and must be combined with a record-level sharing mechanism. Standard Sales Team functionality also does not apply to an arbitrary Presentation custom object. For a robust custom-object design, the implementation should use a dedicated Apex Sharing Reason so the programmatic shares are easy to distinguish and manage throughout the record lifecycle. Study Guide reference: Access to Records - Apex-managed sharing, junction objects, dynamic user-to-record relationships, custom sharing reasons, and Private OWD.

Shipment is a custom object, so Salesforce allows the administrator to control whether access automatically rolls upward through the role hierarchy. If Grant Access Using Hierarchies is disabled, a correctly configured manager role does not by itself provide access to Shipment records owned by subordinate users. With a Private OWD, this produces exactly the symptom described: managers cannot see their team ' s records even though the hierarchy is otherwise correct. Re-enabling Grant Access Using Hierarchies restores the normal upward inheritance pattern for the custom object, assuming managers also have the required object-level permissions. An ownership-based sharing rule is not required merely to reproduce ordinary manager-to-subordinate access, and there is no separate generic switch called ' Role Hierarchy implicit sharing ' that replaces this custom-object setting. Study Guide reference: Access to Records - custom-object OWD, Grant Access Using Hierarchies, role hierarchy, inherited access, and Private 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.

External organization-wide defaults are designed for this exact separation of internal and external access. UC can keep the internal default for ServiceFeedback at the level required by employees while setting Default External Access to Private for authenticated external users. That creates a restrictive baseline for partner users 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.

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.

System.runAs() is used in Apex tests to execute a block of code in the context of a specified user so that user-dependent record-sharing behavior can be verified. It is particularly useful when the application relies on a Private OWD, role hierarchy, manual or managed shares, or classes declared with sharing. A well-designed test creates representative users, runs the relevant code under those users, and confirms that authorized users can retrieve the intended records while unauthorized users cannot. The key distinction is that runAs() is not itself a production security mechanism and does not replace explicit enforcement of CRUD or Field-Level Security. Object permissions, field permissions, and record sharing remain separate layers that the implementation must enforce appropriately. This question therefore focuses on the sharing aspect of user context rather than on field-level authorization. Study Guide reference: Access to Records - Apex sharing tests, System.runAs(), user context, record visibility, and secure testing of sharing behavior.

Salesforce provides parent implicit sharing for several standard Account relationships. When a user has access to an Opportunity, Case, or Contact, Salesforce can grant Read Only access to the related parent Account so the user can understand the business context of the child record. In this scenario, the sales representative owns the Opportunities, so the representative has direct access to those records and receives implicit Read access to the parent Account even though the Account OWD is Private. That implicit access does not grant Account edit rights. Create/Edit permission on Opportunity determines what the user can do to Opportunity records; it does not translate into Create or Edit access on Account. Object permissions and record access must still be evaluated independently. This behavior is native to standard relationships and should not be confused with a manually created sharing rule. The important exam distinction is that child-record access can produce limited parent visibility, but the inherited access is Read Only unless another mechanism grants more. Study Guide reference: Access to Records - implicit sharing, parent implicit access, Account/Opportunity security, record ownership, and OWD interaction.

The Partner Community role hierarchy naturally models the relationship between service agents and their dealer manager. Agents can occupy a lower partner role and the dealer manager a higher role within the same partner account, allowing record visibility to roll upward while users at the same lower level remain isolated from one another under a Private sharing model. This is more efficient than creating a separate sharing rule for every dealer-manager relationship because the management structure itself already expresses who should inherit access. A sharing group is associated with other Experience Cloud access patterns and does not replace the partner role hierarchy for this requirement. The architect should ensure that the partner roles are correctly assigned and that the underlying Case object permissions support the access the manager needs. Study Guide reference: Access to Records - Partner Community roles, external role hierarchy, Private Case sharing, manager access, and scalable Experience Cloud design.

A criteria-based sharing rule combined with a public group precisely matches the requirement. The records are selected by a business characteristic - whether an Opportunity is high value - while the recipients are a cross-functional set of auditors who do not belong to one common role. The public group provides a stable audience that can be maintained independently, and the criteria-based rule automatically exposes only the Opportunities that meet the defined condition. Placing the auditors at the top of the role hierarchy would grant much broader access and distort the hierarchy ' s organizational purpose. Default Opportunity Teams are tied to deal collaboration and individual owners, so they are not an appropriate enterprise audit mechanism. Starting from a Private OWD and opening only the qualifying records to the auditor group preserves least privilege. Study Guide reference: Access to Records - criteria-based sharing, public groups, Private OWD, cross-functional audit access, and least privilege.

A Sharing Set is designed for Experience Cloud users whose record access can be derived from the Account or Contact relationship associated with their external user. In this scenario, all users at a distributor share the distributor-account context, and Delivery records can be related to the customers assigned to that distributor. A Sharing Set can map the external user ' s Account or Contact relationship to the corresponding relationship on the target object and grant the required Read Only or Read/Write access when the values match. This scales much better than creating separate public groups and sharing rules for hundreds of distributors. It also keeps the access relationship data-driven, so membership changes follow the user ' s account relationship instead of requiring manual maintenance of sharing artifacts. The architect must ensure that the selected external license supports the required object and sharing-set configuration and that the target relationship is eligible for the mapping. Study Guide reference: Access to Records - Experience Cloud sharing, Sharing Sets, account/contact access mappings, distributor isolation, and scalable external record access.

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.

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.

Because the Account page layout did not change, the next control to inspect is Field-Level Security and effective field accessibility. Salesforce can hide a field from a user even when that field remains present on the assigned page layout. The Field Accessibility view in Object Manager provides a consolidated way to determine whether a field is visible, read-only, or hidden for the relevant profile and configuration. This is a better diagnostic than logging in and checking several records because the symptom is field-level, not record-specific. A Who Sees What analysis focuses on record visibility and therefore does not explain why one field disappeared while the user can still open the Account. The administrator should verify the affected field ' s FLS for the user ' s profile and any relevant permission-set assignments, then confirm that the page layout and record type do not impose additional presentation restrictions. Field-Level Security is the enforceable security boundary; page layout placement alone is not. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - Field-Level Security, field accessibility, profiles, permission sets, and page layouts.

Price Books have specialized organization-wide access levels. Use is the appropriate level when sales agents must not only view products and pricing but also select the Price Book and add its products to Opportunities. View Only supports inspection and reporting but does not represent the same ability to transact with the Price Book during the sales process. Salesforce therefore distinguishes Use, View Only, and No Access so organizations can separate catalog visibility from sales usability. If UC later needs to restrict specialized Price Books, it can establish a more restrictive baseline and explicitly share those Price Books with selected users, roles, or groups at the Use level. The Price Book security model must also be combined with normal Product, Opportunity, and object permissions because each layer controls a different part of the process. Study Guide reference: Access to Other Data - Price Book security, Use access, View Only, product pricing, and Opportunity product access.

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.

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.

Site User Visibility controls whether authenticated Experience Cloud users can discover other users who participate in the same site. Turning the setting off therefore affects searching for and seeing other external site users. The setting is part of the broader User-object sharing model, which is distinct from sharing business records such as Accounts, Cases, and Opportunities. It does not primarily control whether a user can edit the user ' s own profile, and it should not be interpreted as a general switch for internal-user search. Experience Cloud architects must treat user visibility as its own privacy problem because exposing the User directory can reveal names and other profile information even when business data is correctly isolated. The organization should therefore combine the User object ' s OWD and site/portal visibility settings with any required user-sharing rules according to the collaboration experience it intends to provide. Study Guide reference: Access to Other Data - User sharing, Site User Visibility, Experience Cloud user discovery, external-user privacy, and User-object access controls.

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.

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.

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.