Plat-Arch-205 Sample Questions Answers

The relevant Experience Cloud capability is Super User access, which gives selected external users broader visibility to records belonging to other users associated with the same external account. For Customer Community Plus, the modern terminology commonly used is Portal Super User; the answer choice uses the broader or legacy Partner Super User wording, but it represents the same architectural concept being tested. Delegated external-user administration focuses on managing external users rather than granting broad same-account Case visibility, and a generic community-administration permission is not the record-sharing mechanism required. Super User access should be assigned only to carefully selected agents because it materially expands what they can see within the distributor account. The organization ' s external OWD can remain restrictive between distributors while the elevated user receives the intended same-account visibility. Study Guide reference: Access to Records - Customer Community Plus, Super User access, same-account Case visibility, external-user administration, and Experience Cloud least privilege.

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.

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.

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.

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 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.

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.

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.

Field-Level Security is the appropriate control because the requirement concerns whether a user may see a sensitive field anywhere in Salesforce, not merely whether the field appears on one page layout. If the VIP Flag is hidden through FLS for non-authorized users, Salesforce can suppress that field across record pages, reports, list views, search results, APIs, and other interfaces according to the user ' s effective permissions. Removing the field from a page layout is only a presentation change and is not a reliable security boundary; a user who retains FLS could still reach the value through another surface. Record types likewise select business processes and page layouts but do not provide authoritative field confidentiality. The architect should therefore grant field visibility only to the Private Banking population, preferably through the organization ' s chosen profile/permission-set strategy, and keep the field hidden from everyone else. This follows the principle that sensitive information must be protected at the data-access layer rather than by cosmetic UI configuration. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - Field-Level Security, page layouts, record types, profiles, permission sets, and protection of sensitive fields.

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.

The decisive requirement is that temporary deal access must expire automatically at a known future date. Salesforce sharing mechanisms such as manual or Apex-created shares can grant the temporary access, but a standard share entry does not carry an automatic expiration date. A Scheduled Apex job can therefore implement the lifecycle requirement by running after the specified fiscal-year date and removing only the temporary shares that were created for this collaboration program. Apex sharing by itself describes how access could be granted but not how it expires, while a sharing rule is population-based and is poorly suited to temporary per-deal collaboration with individual expiration. A production design should mark the temporary grants in a reliable way so the scheduled process removes only those shares and leaves ownership, hierarchy, teams, and unrelated sharing intact. Study Guide reference: Access to Records - temporary record sharing, Apex/manual shares, scheduled revocation, share lifecycle, and least-privilege collaboration.

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 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.

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.

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.

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 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 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.

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.

The requirement is a many-to-many external relationship: one part-time agent can work for several distributor Accounts. Contacts to Multiple Accounts can model those relationships through Account Contact Relationships, and a Sharing Set can use the related-account relationship to grant the Experience Cloud user access to the appropriate distributor Accounts. This is substantially more scalable than maintaining Apex share rows or manual sharing rules every time an agent begins or stops working for a distributor. The user ' s access follows the underlying relationship data instead of a separate custom sharing-maintenance process. Customer Community Plus supports the richer external sharing architecture needed for this scenario. The architect should ensure the Sharing Set mapping uses the eligible Account/Contact relationship field and grants only the required access level. Study Guide reference: Access to Records - Sharing Sets, Contacts to Multiple Accounts, Account Contact Relationships, Customer Community Plus, and scalable external 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.

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.

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.