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

Path is designed to give users a visual representation of a record ' s progression through a process based on a picklist field such as Status or Stage. Salesforce describes Path as an at-a-glance indicator that shows where a record currently sits in a process and where it is progressing next. For delivery tracking, the app builder can configure delivery statuses as Path stages and place the Path component on the Lightning record page. Related Lists display associated records rather than process progression. Details displays record fields, while Related Record exposes information from another related record. Because the stated requirement is specifically for a visual representation of delivery status, Path is the native declarative component that directly satisfies the requirement.

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

The correct answers are A. Assign app to profiles and B. Build a Custom Tab for the app.

Your option A appears corrupted as “Asking new options,” but the known Salesforce wording for this question is Assign app to profiles.

To make a custom Lightning app available to internal users, users must have access to the app through profile/app assignment. Salesforce documentation explains that assigned app settings specify which apps users can select from the Lightning Platform app menu.

A Custom Tab is also needed when exposing the custom app/component as something users can access from the Salesforce UI. Salesforce documentation states that custom tabs can appear in the app navigation bar and App Launcher.

Adding the app to a Visualforce page is not required, and uploading it to Static Resources is not how Lightning apps are made available to users.

===========

A Text field configured as External ID and Unique satisfies both requirements. Existing Invoice Numbers can be migrated directly from the external system without changing their values, while the Unique attribute prevents duplicate Invoice Numbers from being stored later. Salesforce defines an External ID as a field containing an identifier from a system outside Salesforce and supports Text fields as External IDs. Salesforce also states that marking the field Unique prevents duplicate values and makes it suitable for record matching and future data operations. An Auto Number field would generate Salesforce-controlled values and therefore would not preserve externally assigned Invoice Numbers. Maintaining separate legacy and Salesforce numbering fields is unnecessary when one field can preserve the external identifier and enforce uniqueness. Salesforce

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

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.

===========