Salesforce Updated Platform-App-Builder Exam Questions and Answers by kathleen

The lookup field is created on the custom object Box and points to Account. That makes Account the parent-side object and Box the related child object. Salesforce automatically creates a standard relationship report type in the format Parent Object with Child Object, so the report type is Accounts with Boxes. Salesforce Help confirms that standard report types can be generated automatically when reportable custom objects have lookup relationships.

Why others are incorrect:

A. Boxes with Accounts starts from the child object perspective.

C and D include “with or without,” which is normally configured through custom report type relationship options, not the automatically created standard relationship report type.

===========

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.

===========

The verified exam answer is D. Add the Path component to the Lightning record page.

Salesforce Path is designed to guide users through stages of a business process. For each step, such as each Opportunity Stage, an app builder can highlight key fields and add guidance for success. Salesforce documentation states that when creating a Path, the app builder can select key fields for each step and enter success guidance.

This fits the requirement because users need to know which fields should be completed at each Opportunity stage.

Important nuance: Path guides users, but it does not hard-enforce stage-based required fields by itself. Salesforce notes that page layouts cannot require different fields in different Path steps; strict enforcement requires validation rules based on the stage/path step.

===========

Salesforce requires installation records to be directly associated with Opportunities, and sales reps need visibility of all installations tied to their Opportunities. A Master-Detail relationship is the correct solution because:

The Installation object (detail) inherits sharing and security from the Opportunity (master), ensuring sales reps see only their related installations.

Enables roll-up summaries on Opportunity if needed.

Salesforce documentation confirms that Master-Detail relationships provide parent-controlled ownership and access, making them ideal for enforcing related record visibility. (Salesforce Help)

B. Hierarchical is only available for User object.

C. Many-to-Many requires a junction object; not needed here.

D. Lookup allows optional, independent access; would not automatically enforce visibility.

===========