Salesforce Plat-Arch-205 Dumps

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.

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.

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.

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.

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.

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.

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

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.

A file uploaded to Files Home is private by default until it is explicitly shared. Current Salesforce behavior allows the file owner and users with the powerful View All Data permission to access such private files. The ordinary role hierarchy does not automatically expose a private Salesforce File merely because another user is the owner ' s manager. Files have their own visibility and sharing model and should be evaluated separately from standard business-object sharing. View All Data is a very broad administrative permission and should not be granted merely to solve a file-sharing requirement; this question describes its effect, not a least-privilege recommendation. When collaboration is needed, the appropriate design is to share the file through the supported Salesforce Files mechanisms with the intended people, records, groups, or libraries. Study Guide reference: Access to Other Data - Salesforce Files, Files Home, private files, View All Data, file-sharing semantics, and least privilege.

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

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

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.

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.

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.

Dynamic Forms is the most maintainable solution for an object with hundreds of fields and several distinct business processes. It allows the Lightning record page to be decomposed into individual fields and field sections, then uses visibility rules to show only the information relevant to the current Work Order or Case type. Record Type can be used as the controlling condition so one governed Lightning page supports multiple process variants without multiplying page layouts or introducing custom LWC code. A custom override with metadata would create unnecessary development and maintenance overhead for behavior the platform can provide declaratively. Separate page layouts per type can work, but with hundreds of fields they become harder to govern and often duplicate large portions of configuration. Dynamic Forms is therefore the declarative-first architecture. The architect must still enforce sensitive-data restrictions through Field-Level Security because conditional page visibility is not an authorization control. Study Guide reference: Implications of Security Model Choice - Dynamic Forms, Record Types, field sections, component visibility, large-field-count page design, and UI visibility versus FLS.

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.

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.

Super User access is designed for selected external partner managers who need visibility across records associated with other users at the same partner account. Granting that elevated access to the individual partner manager is more scalable than creating and maintaining separate ownership-based sharing rules for every distributor. The requirement is deliberately limited to certain managers, so the organization can keep the external sharing model private between distributors while giving designated managers broader visibility within their own distributor organization. Sharing Sets are best suited to deterministic Account/Contact relationship mappings and do not replace the manager-level elevation represented by the Super User model. Because Super User access is powerful, it should be assigned only to users who genuinely need it and should be reviewed as part of the external-access governance process. Study Guide reference: Access to Records - Partner Community, Super User access, partner manager visibility, same-account external sharing, distributor isolation, and scalable Experience Cloud access.

When a sharing rule grants Opportunity access to members of a public group, the effective audience can also include managers above those group members through the role hierarchy. Salesforce can propagate access upward according to the group ' s Grant Access Using Hierarchies behavior and the object ' s normal hierarchy semantics. That is why the sales engineers in the public group and their managers can have access to the shared Opportunities. The reverse is not true: subordinates of a manager do not inherit records merely because the manager or another subordinate has access, and peer users in comparable roles do not automatically receive one another ' s shared records. Architects must account for this upward propagation when designing public groups for sensitive records because the effective audience may be broader than the explicit list of group members. Study Guide reference: Access to Records - Public Groups, sharing rules, Grant Access Using Hierarchies, upward access inheritance, and Private Opportunity OWD.

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.

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.

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.

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.