Authentic Salesforce Certification Exam Plat-Arch-205 Questions Answers

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.

The enforceable control is the Order Delete object permission. Removing the Delete button from a page layout removes only one user-interface path and does not guarantee that the user cannot delete through another supported interface or API. Likewise, making a page layout read-only controls presentation and field editing but does not revoke the underlying delete capability. UC should remove Delete permission for Order from the affected profiles and permission sets and verify that no permission set group or elevated permission grants it back, because Salesforce permissions are additive. The organization should also review powerful overrides such as Modify All Records or Modify All Data for users who are subject to the legal-retention requirement. If the business needs a formal legal hold, additional retention, backup, audit, and governance controls may be appropriate, but within the supplied choices the correct authorization layer is object CRUD. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - object CRUD, Delete permission, permission aggregation, page-layout limitations, and least privilege.

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.