Salesforce Platform-App-Builder - Salesforce Certified Platform App Builder (Plat-Admn-202)

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.

===========

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.

A roll-up summary field requires a master-detail relationship. Since Galaxy__c and Star__c currently have a lookup relationship, the app builder cannot create a standard roll-up summary field to count related Star__c records. The lookup must be converted to master-detail first, with Galaxy__c as the master and Star__c as the detail. Salesforce Trailhead confirms that roll-up summary fields display values on the master record based on directly related detail records in a master-detail relationship.

===========

A custom link or button that passes the current Account ID into a report filter provides direct access to a report showing only records associated with the Account being viewed. Salesforce ' s official documentation specifically describes creating an Account custom link that opens a report and automatically filters the results by the current Account ' s record ID. This precisely satisfies the requirement for Account owners to access the relevant Asset report from the Account record page. A dashboard filter requires dashboard-level filtering and does not inherently pass the current record context. Scheduled Reports deliver reports at scheduled times, while a Custom Report Type merely defines the objects and fields available for reporting.

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

The correct answers are A. Remove the delete button from the Delivery page layout and C. Remove the Delete permission from the Shipper profile.

The real security control is C because object permissions define whether users can create, read, edit, or delete records for an object. To prevent shipping users from deleting Delivery__c records, the app builder must remove the Delete object permission from the Shipper profile.

A is also a valid supporting UI step because Salesforce page layouts can control whether standard/custom buttons are displayed. Removing the Delete button reduces the visible delete option on the record page. However, this alone is not complete security because hiding a button does not fully remove the underlying permission.

Why others are incorrect:

B is incorrect because a regular permission set grants additional access; it does not remove profile access.

D is incorrect because OWD controls record-level sharing, not object-level Delete permission.

===========

To optimize Salesforce Mobile experience:

B. Minimize formula fields and lookup fields improves page load performance on mobile devices.

C. Put key fields in the compact layout ensures important information is visible immediately.

E. Use Global Actions simplifies creating or updating records from mobile quickly.

Salesforce documentation on mobile best practices recommends limiting complex fields, prioritizing compact layouts, and using quick actions for essential functionality. (Salesforce Help)

A is incorrect because default values improve speed and reduce user errors, not eliminate them.

D is unnecessary; Lightning layouts are responsive and do not require separate OS-specific layouts.

===========

In-App Guidance is Salesforce ' s native capability for contextual onboarding, feature adoption, prompts, and guided walkthroughs directly inside Lightning Experience. Salesforce documents that administrators can create prompts and walkthroughs, determine the target audience, and specify where and when that guidance appears. Targeted prompts can highlight a specific page element, while walkthroughs connect multiple prompts into a step-by-step guided experience. This aligns directly with Universal Containers ' goals of increasing adoption and guiding users through a newly launched application. A Screen Flow is appropriate when collecting information or executing an interactive business process, but it is not the dedicated adoption feature. Dynamic Actions control which actions appear, while Dynamic Forms controls field and section presentation. Neither provides structured onboarding walkthroughs.

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

The correct answer is B. Apex unit test failures.

When installing a package that contains Apex in a production org, Salesforce runs Apex tests as part of the installation/deployment validation. Salesforce documentation states that package installs or upgrades can fail when Apex test requirements are not met.

Even though the unmanaged package was tested in a Full Copy sandbox, production installation can still fail if Apex tests fail during production validation.

Why others are incorrect:

A, C, and D are not the best answer because the package already installed successfully in a Full Copy sandbox that matched production. The most certification-relevant reason for production failure is Apex unit test failure.

===========

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.

===========