Free Salesforce Platform-App-Builder Practice Exam with Questions & Answers

Inspection__c must be the detail object and Building__c the master. Salesforce master-detail relationships create strong dependency between parent and child records: when a master record is deleted, its related detail records are cascade-deleted. Detail records also inherit record access from the master through the Controlled by Parent sharing model. Salesforce additionally specifies that the master-detail relationship field is created on the detail object. Therefore, the relationship field belongs on Inspection__c and references Building__c . A lookup relationship would leave Inspection records independently owned and would not provide the required cascade-delete and inherited-sharing behavior. Option B reverses the relationship direction and would incorrectly make Building the detail. Thus, D satisfies both lifecycle dependency and security inheritance requirements with the standard declarative Salesforce data model.

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

The correct solution is to configure validation rules with help text/error messaging.

Validation rules are the right tool because they evaluate record data before save and stop the save when the record does not meet the defined conditions. They can enforce that a Case status is not changed back to an earlier value by using formula logic such as PRIORVALUE() and picklist checks. They can also require certain fields only when specific Case criteria are met by checking whether those fields are blank under those conditions.

Why the other options are wrong:

Dependent picklists control valid picklist values, but they do not enforce status progression or conditional required fields across all save paths. Approval processes are not the best fit for real-time save validation. Page layout required fields are UI-level requirements and are not flexible enough for criteria-based enforcement.

The correct answer is C.

Universal Containers wants to accept clean data and verify that important fields are entered. The best solution is a validation rule, because validation rules verify that data entered by users meets defined standards before the record can be saved. This is stronger than making a field required only on a page layout, because validation rules can enforce requirements based on conditions such as record type.

A is weaker because page-layout required fields apply mainly to that UI layout and do not provide the same conditional data-quality enforcement. B is reactive cleanup after bad data exists. D can calculate or display a value, but it does not enforce user data entry by itself.

===========

Use a Component visibility filter. The issue is not object access or field access. The Contact Lightning record page is shared, but one component should be hidden for users with the Marketing profile. Salesforce Lightning App Builder supports visibility filters on Lightning page components, so the app builder can conditionally show or hide that component based on user/profile criteria.

Why not the others? AppExchange is unrelated. Detail page layouts control field layout, not visibility of a Lightning page component. Field-level security controls field access, not whether a large component appears on a Lightning record page.

===========

The correct answer is B. Add the standard Chatter feed component.

To show Chatter on a custom object Lightning record page, the app builder should use the standard Chatter Feed / Chatter component in Lightning App Builder. Salesforce documentation describes adding Chatter components such as Chatter Feed, Chatter Publisher, and Chatter to Lightning record pages, usually after feed tracking is enabled for the object.

A is incorrect because a related list component does not display the Chatter feed.

C and D are incorrect because a custom component or AppExchange component is not required for standard Chatter feed functionality.

===========

Existing data will be truncated to the first 255 characters.

Salesforce documentation on changing custom field types states that when a Long Text Area field is converted to Email, Phone, Text, Text Area, or URL, the record data is truncated to the first 255 characters. Since the target is a standard Text Area with a 255-character limit, longer Manager Notes values would not remain intact.

Why not the others? Salesforce does not preserve values beyond the new limit in this conversion. The data is not completely lost, but anything after the first 255 characters is removed.

The correct answer is A. Add the field to the custom report type field layout.

The report already exists: Position with or without Applicants Report. The issue is not that reporting is disabled for the object; the issue is that the new Applicant field is not available as a column in that custom report type. For custom report types, fields available to report builders are controlled by the custom report type field layout. Salesforce’s documentation for adding fields to a custom report type directs admins to open the report type and use Edit Layout to add the missing fields.

B is incorrect because field-level security can hide a field from a user, but the troubleshooting step for a field missing from a custom report type column list is to add it to the custom report type layout.

C is incorrect because the report type already exists and is being used.

D is incorrect because the field data type was already assigned when the field was created.

===========

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. Record Detail.

The Record Detail component on a Lightning Record Page displays the fields and sections from the object’s assigned page layout. After using Lightning Object Creator to create the object, fields, and data, the app builder must add the Record Detail component if users need to see the fields from the page layout on the Lightning Record Page. Salesforce documentation states that the Record Detail component displays fields and sections from the page layout associated with the object.

Why the other options are incorrect:

Highlights Panel shows key record actions and compact-layout information.

Recommendations displays recommendation records.

Path shows guided stage/status progression, not all page-layout fields.

===========

The correct answer is B. Data is unable to be deployed with change sets.

Change sets deploy metadata/configuration, not business data. Salesforce documentation states that change sets can contain setup modifications, but they cannot be used to upload a list of records such as contacts.

So the report itself can be deployed, but the underlying records needed for the report results are not deployed through the change set. If the Partial Copy sandbox does not contain matching sample data, the report returns no data.

Why others are incorrect:

Data is not deployed just because it is added to a change set.

Reports do not have to be manually recreated if they are deployed properly.

“Salesforce OK” is not a deployment requirement.

===========