Free Practice Questions for Salesforce Platform-App-Builder Exam

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

The legacy ID should be marked as an External ID because Salesforce can use an external ID field to match records during import, integration, and upsert operations. Salesforce REST API documentation states that records can be inserted or updated using a specified external ID field.

The field should also be marked Unique so that the legacy system ID identifies one Salesforce Account record only. Salesforce documentation explains that an external ID can represent an ID from another external system, and uniqueness helps prevent duplicate matching values.

B is incorrect because encrypted text is not appropriate for a matching/upsert key.

C is incorrect because Required only forces a value; it does not make the field usable for upsert matching or prevent duplicate legacy IDs.

===========

The correct answer is D.

Validation rules are the right declarative tool to enforce data compliance before a record is saved. They can prevent a Case from moving backward to an earlier Status and can require specific fields when Case criteria are met. Salesforce formula functions such as ISCHANGED() compare whether a field value changed, and validation rules can use formula logic to stop invalid saves.

Why others are incorrect:

Approval Process is for routing records for approval.

Dependent picklists control picklist value availability, not status regression.

Case Flow can automate case processes, but validation rules are the best tool for enforcing save-time compliance.

===========

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 answer is B. Unable to reference the child records.

Formula fields can reference fields on related parent records through cross-object formulas. For example, a formula field on Contact can reference Account fields because Account is the parent of Contact. Salesforce Trailhead shows this pattern by inserting Contact | Account | Account Number in a formula on Contact.

However, the reverse direction is not supported in a normal formula field. An Account formula cannot directly reference values from multiple related Contact child records. Since Contacts are child records of Account, the Contact relationship does not appear in the Account formula editor.

A is incorrect because the issue described is about relationship direction, not the number of formula fields.

C is incorrect because Contact and Account do not need a master-detail relationship for this limitation to apply.

D is incorrect because Salesforce formula character limits are separate from this parent-to-child reference limitation. Salesforce documents formula character limits separately.

===========

An indirect lookup relationship is used when an external object must relate to a standard or custom Salesforce object and the external data does not contain Salesforce record IDs. Salesforce requires the parent Salesforce object to contain a custom field marked External ID and Unique . Values from the external object ' s indirect lookup field are matched against this external ID field to establish the relationship. Salesforce specifically states that indirect lookups link a child external object to a parent standard or custom object using a custom unique External ID field. TEXT(Id) does not create such a relationship key, and CASESAFEID() merely converts Salesforce IDs to their 18-character representation. A normal Salesforce Record ID is used for standard lookup relationships, not indirect lookups.

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

omprehensive and Detailed Explanation with all Platform App Builder documents: =

The correct answer is C. Validation Rule.

DreamHouse Realty needs to prevent an Opportunity from entering the Qualified stage unless Expected_Close_Date__c is populated. A validation rule is the correct feature because validation rules check whether record data meets defined requirements before the record can be saved. Salesforce also provides examples of validation rules used to control Opportunity stage changes.

Example formula:

AND(

ISPICKVAL(StageName, " Qualified " ),

ISBLANK(Expected_Close_Date__c)

)

A is incorrect because record types do not enforce this conditional requirement by themselves.

B is incorrect because page layouts cannot reliably enforce conditional required fields by stage.

D is incorrect because Activity History does not validate data entry.

===========

The correct answers are C. Use Data Loader to update leads using the CSV file and D. Select Insert Null Values in Settings.

Universal Containers wants to delete values from fields on 5,000 Lead records. The correct method is to use Data Loader Update with the record IDs in the CSV file, leave the target field cells blank, and enable Insert Null Values so Data Loader treats the blank CSV values as null updates. Salesforce Help explains that to change field values to blank/null with Data Loader, export IDs and fields, clear the values in the CSV, select Insert Null Values, and run an update.

Why others are incorrect:

A is unrelated because record type selection does not delete field values.

B is not the best choice because the Import Wizard is not the proper tool for mass clearing field values using null updates.

The correct answer is A. Two Master-detail relationships on a new custom object.

This is a classic many-to-many relationship requirement: one Contact can relate to many Solar Projects, and one Solar Project can relate to many Contacts. Salesforce recommends using a junction object for many-to-many relationships. A junction object is a custom object with two master-detail relationships.

The new custom junction object would sit between Contact and Solar Project, with one master-detail relationship to Contact and one master-detail relationship to Solar Project.

C could technically connect records using lookups, but the standard Salesforce data-modeling answer for a true many-to-many relationship is a junction object with two master-detail relationships.

===========

The correct answer is C. Flow.

This requirement needs automation that can do multiple things: update the To Be Installed checkbox when a Lift is sold, then notify an external system the next day using an outbound message. Salesforce states that Flow Builder is the optimal tool for triggered automation because it combines workflow and process automation capabilities in one point-and-click tool. Record-triggered flows can run when records are created, updated, or deleted, and can update records, send notifications, initiate processes, and maintain data consistency.

The “next day” timing points to a scheduled path in a record-triggered flow. Salesforce explains that scheduled paths delay automation for minutes, hours, days, or months after the triggering record change. Salesforce also documents outbound messages as a Flow Builder core action for record-triggered flows, used to send a SOAP message to a designated endpoint.

Approval Process is for approvals, Validation Rule only prevents invalid data, and Assignment Rule is for assigning records such as leads or cases. None of those tools can meet the full requirement.

The correct answer is C. Submit the record for approval from an automated process.

The issue is not the approval process itself. The issue is that sales reps forget to manually submit the Opportunity. Salesforce supports submitting records for approval from automation, including Flow’s Submit for Approval action. Salesforce also documents using an after-save record-triggered flow to automatically submit records into an approval process.

A does not solve the problem because changing approval entry criteria does not automatically submit the record. B only reminds the manager and does not run the approval process. D is unrelated to automatic submission.

===========