Free Practice Questions for Salesforce Platform-App-Builder Exam

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 correct answer is D. Apex unit test failures.

The option text says “Apps unit test failures,” but the intended Salesforce answer is Apex unit test failures. When a package containing Apex is installed or deployed to production, Salesforce runs Apex tests. If the required tests fail, the package installation can fail. Salesforce documentation states that package installation involving Apex runs unit tests, and production deployments with Apex require tests to pass.

A, B, and C are not the best answers because the package already installed successfully in a Full Copy sandbox matching production. The most certification-relevant production failure reason is Apex test failure.

===========

The correct answer is A. Existing reports created under the Sun__c with Planet__c report type made by Salesforce will be unusable, but not deleted.

When a relationship is changed from master-detail to lookup, the available standard report types can change. Salesforce documentation notes that converting a lookup relationship to master-detail or vice versa can make existing custom reports unusable because of differences in available standard report types.

B is incorrect because roll-up summary fields are not automatically deleted from reports as part of the conversion. In fact, Salesforce states that a master-detail relationship cannot be converted to lookup while roll-up summary fields exist on the master object.

C is incorrect because roll-up summary fields do not remain and simply stop updating.

D is incorrect because the reports are not deleted; they become unusable.

===========

The correct answer is C. A Galaxy__c with Star__c report type will be automatically created.

When a master-detail relationship is created between a parent custom object and a child custom object, Salesforce can automatically generate a standard report type for the parent object with the child object, such as Galaxy__c with Star__c, assuming reporting is enabled for the objects. Salesforce documentation confirms that standard report types are created in certain object relationship scenarios, including lookup and master-detail relationships.

Why the other options are incorrect:

A is incorrect because the report type is based on the parent with child, not the child object with the parent merely as a field.

B is incorrect because a custom report type is not required for this basic master-detail reporting scenario.

D is incorrect because the report type is not created as Star__c with lookup fields from Galaxy__c.

===========

The correct answer is B. Cross-object formula.

Opportunity has a standard relationship to Account, so an app builder can create a formula field on Opportunity that references the parent Account field. Salesforce defines a cross-object formula as a formula that spans related objects and references fields on those related objects.

Because Account_Region__c is a picklist on Account, the Opportunity formula would commonly be a text formula like:

TEXT(Account.Account_Region__c)

Field history tracking only tracks changes, a lookup field would create a relationship rather than display the Account field value, and field-level security controls visibility but does not copy or display the parent field on Opportunity.

===========

The correct answer is C.

The app builder needs to display only the first five digits from the parent Account’s ZIP+4 custom text field. Salesforce’s LEFT() function returns a specified number of characters from the beginning of a text string, so the correct formula is:

LEFT(Account.Zip_Code__c, 5)

Salesforce formula documentation confirms that LEFT returns characters from the beginning of a text string.

BEGINS() checks whether text starts with specific characters. LPAD() pads text to a specified length. TEXT() converts certain data types to text, but it does not extract the first five characters.

===========

The correct answer is C. Salesforce Schema Builder can create fields, including relationship fields, formula fields, and normal fields, and it also helps visualize existing object relationships. However, a field created in Schema Builder is not automatically added to the object’s page layout. Salesforce documentation states that after using Schema Builder, the field must be added through the Page Layout Editor.

Why others are incorrect:

A is incorrect because Schema Builder can create formula fields.

B is incorrect because Schema Builder can create relationship fields.

D is incorrect because Schema Builder is specifically used to view and understand object relationships.

===========

The correct answers are C. Unique and D. External ID.

The legacy ID should be stored in a custom field marked as an External ID because Salesforce uses External ID fields to identify records from an outside system and to support update/upsert operations during future data loads. The field should also be marked Unique so each legacy system ID maps to only one Salesforce Account record and avoids duplicate-match problems during upsert. Salesforce documentation defines External ID fields as fields that contain record identifiers from outside Salesforce and can be used to update or upsert records.

A. Required is not necessary for the upsert-matching requirement.

B. Encrypted/Text encrypted is not appropriate because encrypted fields are not used for this legacy-ID matching purpose.

===========

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.

===========

The correct answer is C. Research and evaluate data enrichment products on the AppExchange to automate data entry.

The sales manager wants reps to spend less time manually entering business-card information while maintaining data quality. Salesforce AppExchange is the correct place to evaluate packaged solutions that extend Salesforce functionality. Trailhead describes AppExchange as a place to find solutions for business needs, and AppExchange contains business-card scanning apps that can create or match Salesforce Leads, Contacts, and Accounts with reduced manual entry.

A does not automate data entry.

B is not the best fit because Flow cannot read business cards by itself.

D is incorrect because formula fields calculate values from existing data; they do not capture business-card information.

===========