Collection Sort is designed to reorder a collection and optionally reduce the number of records retained after sorting. Salesforce documents that the Collection Sort element can sort a record collection by a selected field in ascending or descending order and can specify the maximum number of items to keep afterward. The flow should therefore sort the Opportunity collection by Amount in descending order and retain only five records. A Collection Filter selects records based on Boolean-style criteria, but it does not identify the top N records based on ranking. A Decision controls execution paths rather than restructuring a collection. Transform maps data between structures but is not intended to rank and limit records. Collection Sort directly implements both requirements—highest Amount first and only five records retained.

================

Record type availability determines which record types a user can select when creating records. Salesforce allows record types to be assigned through profiles, permission sets, and permission set groups. Therefore, if the support team ' s profile currently provides access to Bronze, removing Bronze from that profile prevents users from selecting that record type, assuming it is not granted through another permission set. Organization-wide defaults and sharing rules regulate access to records after they exist; they do not control which record types a user can select during creation. A permission set group containing Platinum and Diamond could grant additional access but does not inherently revoke Bronze access already provided by the profile. The direct solution described by the options is therefore to remove the Bronze record type assignment from the support team ' s profile.

================

The correct answer is C. Data Export Service.

Salesforce Data Export Service is the native tool used to export backup data from a Salesforce org. It allows admins to create export files of Salesforce data and schedule exports. Salesforce documentation describes Data Export as the feature for exporting backup data from Salesforce.

Important exam note: the question says “daily backup,” but standard Salesforce Data Export scheduling is commonly weekly or monthly depending on edition and settings. Among the listed options, Data Export Service is still the correct Platform App Builder answer.

A is incorrect because refreshing a Full Copy sandbox is not a backup strategy.

B is incorrect because packages move metadata, not org data backup.

D is incorrect because “Support expert” is not the Salesforce backup/export tool.

===========

The correct answer is A. Page structure will automatically adapt to the device being used to view the record page.

When choosing a Lightning record page template, the app builder should consider how the template displays across supported devices. Salesforce Lightning pages are designed for Lightning Experience and the Salesforce mobile app, and Salesforce documentation states that the chosen template controls how the page displays across devices.

B is incorrect because users do not need “View All Data” just to view a Lightning record page; normal object and record access applies.

C is incorrect because Salesforce supports switching Lightning page templates, subject to template-switching considerations.

D is incorrect because the app builder does not create a separate template for every device type.

===========

The requirement specifies that a new vendor must accept terms on Agreements before an Opportunity can be closed. Salesforce Approval Processes are the declarative solution for enforcing such business rules. An approval process can:

Require users (vendors) to accept or approve records (Agreements).

Prevent Opportunities from moving to a closed stage until approval is completed.

Send email notifications automatically to approvers.

Salesforce documentation confirms that approval processes are used to enforce conditions on record lifecycle and ensure required steps are completed before record status changes. (Salesforce Help)

A. Email Alert cannot enforce record progression.

B. Dynamic Action only controls field-level UI visibility, not enforcement.

D. Validation Rule could prevent saving a record, but it cannot require explicit approval from a specific user group.

===========

The correct answer is A. Build a global action to create Contacts.

Sales reps need a fast mobile-friendly way to create new Contact records and complete additional details later. A global quick action is the best fit because it lets users create records quickly without needing to navigate deeply into the app. Salesforce documentation states that global actions allow users to create or update records without leaving the page they are on. Salesforce also documents that Create a Record global actions let admins choose the object to create, such as Contact.

Salesforce mobile uses quick actions in the action bar/action menu, making them suitable for fast record creation on mobile.

B. Path is used for guided stages, not quick contact creation. C. Mobile menu customization improves navigation but does not simplify the create process enough. D. Compact layout controls key field display, not fast record creation.

===========

Dynamic Related List - Single provides the advanced declarative customization required in this scenario. Salesforce documents that this component allows an app builder to select and reorder displayed columns, define the record sort order, filter related records, determine how many records appear, and show or hide list actions. These capabilities go beyond the standard Related Lists and Related List - Single components, which are more dependent on traditional page-layout configuration. Related List Quick Links provides compact navigation to related lists rather than detailed control of list behavior. Because the requirement specifically combines configurable sorting with action visibility, Dynamic Related List - Single is the precise Salesforce component designed for the use case. It can be configured directly through Lightning App Builder on a supported record page.

The best option is a managed package from AppExchange.

Managed packages are designed for distributed apps where the provider can deliver upgrades. Salesforce documentation states that upgrades are supported for managed packages only. This reduces manual maintenance compared with unmanaged packages or custom open-source development, where updates typically require more manual replacement, deployment, or rework.

Why not the others? Unmanaged packages and open-source custom development can be useful, but they do not provide the same upgrade path and vendor-managed maintenance model as a managed AppExchange package.

===========

The correct answers are A. Create a custom-based sharing rule and B. Update the organization-wide defaults.

Here, “custom-based” is most likely referring to a criteria-based sharing rule. UC wants to move from public sharing to a more restrictive model, so the app builder must first update the Organization-Wide Defaults for Accounts. Salesforce OWDs define the default access users have to records they do not own.

Then, to continue giving the Sales team access to all Account records with the Sales record type, the app builder should create a criteria-based sharing rule based on record criteria, such as Record Type. Salesforce criteria-based sharing rules share records based on field values.

C is incorrect because profiles control object permissions, not record-level sharing by record type.

D is incorrect because owner-based sharing rules share records based on record owner, not record type.

===========

The correct answer is A because the requirement is to keep one specific field, the Comment field, private from users outside HR. Salesforce field-level security is the correct security layer for controlling whether users can view or edit a field. Salesforce documentation states that field-level security restricts user access to fields and overrides page-layout visibility.

A page layout alone is not enough because page layouts control UI presentation, not full field security. Salesforce also notes that to ensure users cannot access a field, field permissions should be used because other settings do not provide the same field-level protection.

Why others are incorrect:

B and D are wrong because sharing rules and Apex sharing control record access, not individual field access.

C is wrong because removing a field from a page layout only hides it from that layout; it does not securely prevent access through reports, API, related lists, or other interfaces.

===========