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 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 requirement is an authorization requirement, not merely a page-design preference. Removing the Work Order Edit object permission from the Sales Representative permission model prevents those users from updating Work Orders regardless of which UI, API, automation entry point, or page layout they use. Page layouts can make fields appear read-only, but they are presentation controls and should not be relied on as the security boundary. A sharing rule is also the wrong tool because sharing rules add record-level access; they do not reduce the CRUD capabilities a user already has. In a modern Salesforce permission architecture, the organization should remove Edit from the relevant profile or baseline permission set and verify that no other assigned permission set or permission set group grants it back, because permissions are additive. The page can still be configured to present an appropriate read-only experience, but enforcement belongs at the object-permission layer. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - object CRUD, profiles, permission sets, page-layout limitations, and least-privilege authorization.

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.

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.