Free Practice Questions for Salesforce Platform-App-Builder Exam

Global actions are designed to be available broadly, not only from one object’s record page. Salesforce Trailhead states that global actions can be placed anywhere actions are supported and can let users send email without leaving the page they are on.

This fits the requirement because users need a Send New Email action available from Leads, Contacts, and Accounts in the Salesforce mobile app.

Why others are incorrect:

A is incorrect because a global action layout does not automatically clone the default page layout.

B is incorrect because the Lightning Component Library is not the reason to use global actions.

C is incorrect because global actions are not record-specific; object-specific actions are record-specific.

===========

The primary object of a custom report type is a fundamental design choice and cannot be changed after the report type is saved. Salesforce explicitly states in both the Enhanced and Legacy Custom Report Type Builder documentation that after saving a custom report type, the selected primary object cannot be changed. The primary object determines the base set of records represented by the report type and controls how additional related objects can subsequently be included. Consequently, the app builder must choose the Job Application object deliberately before saving the report type. Deployment does not permanently prevent a custom report type from being deleted, and the other options do not describe the core configuration limitation being tested. Therefore, B is the documented Platform App Builder consideration.

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

The correct sandbox type is Partial Copy.

A Partial Copy sandbox is built for testing with a subset of production data. Salesforce lists Partial Copy sandboxes with 5 GB data storage and a 5-day refresh interval, which supports the requirement to refresh it every weekend.

Why the other options are wrong:

Developer and Developer Pro sandboxes are mainly for development and do not copy a production data subset in the same way. A Full sandbox can copy all production data, but its refresh interval is longer and it is unnecessary for a subset under 5 GB.

===========

The correct answers are A. There are already two master-detail relationships on the Invoice Line Item and C. Invoice Line Item records exist without having the Invoice lookup field populated.

Salesforce allows a lookup relationship to be converted to a master-detail relationship only when the lookup field has a value on all existing records. Therefore, if any Invoice_Line_Item__c records do not have the Invoice lookup populated, Salesforce prevents the conversion.

Salesforce also limits each custom object to up to two master-detail relationships. If Invoice Line Item already has two master-detail relationships, it cannot have another master-detail relationship added or converted.

B is incorrect because custom objects can be on the detail side of master-detail relationships. D is incorrect because a roll-up summary field on Invoice is not the reason this lookup-to-master-detail conversion would be blocked.

===========

The correct answer is B. Validation Rule.

DreamHouse Realty wants to prevent an Opportunity from entering the Qualified stage unless Expected_Close_Date__c is populated. A validation rule is the correct tool because Salesforce validation rules check whether record data meets specified criteria before the user can save the record.

A validation rule could check:

Stage = Qualified

AND

Expected_Close_Date__c is blank

If both are true, Salesforce blocks the save and displays an error message.

A. Page Layout can make a field visible or required on a layout, but it cannot conditionally require the field only when Stage equals Qualified.

C. Activity History is unrelated.

D. Record Type controls business processes and layouts but does not enforce this condition by itself.

===========

The correct answers are A. Remove the delete button from the Delivery page layout and C. Remove the Delete permission from the Shipper profile.

The real security control is C because object permissions define whether users can create, read, edit, or delete records for an object. To prevent shipping users from deleting Delivery__c records, the app builder must remove the Delete object permission from the Shipper profile.

A is also a valid supporting UI step because Salesforce page layouts can control whether standard/custom buttons are displayed. Removing the Delete button reduces the visible delete option on the record page. However, this alone is not complete security because hiding a button does not fully remove the underlying permission.

Why others are incorrect:

B is incorrect because a regular permission set grants additional access; it does not remove profile access.

D is incorrect because OWD controls record-level sharing, not object-level Delete permission.

===========

The actions described require an after-save record-triggered flow because the automation must create additional Salesforce records and invoke a notification action after the triggering Case is saved. Salesforce explains that after-save flows handle actions dependent on a successfully saved record, including creating records, updating related records, sending emails, and other actions. The Send Custom Notification core action is also directly available in Flow Builder. A before-save flow is optimized for changing or validating fields on the triggering record and does not support this full set of post-save operations. A Screen Flow would unnecessarily require user interaction, while a platform event-triggered flow requires a platform event rather than a Case record change. Therefore, Actions and Related Records after save is the appropriate architecture.

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

The correct answers are A. Processes that update record owners do not transfer child records and C. Processes will fail on records owned by inactive users.

When Process Builder updates a record owner, Salesforce does not automatically transfer associated child records such as related Contacts or other child records. Salesforce documentation says processes that update owners do not automatically transfer associated items, so separate update actions are required for each related record type.

Also, Salesforce documentation states that processes can’t update records owned by inactive users. If records are still owned by inactive users, automation that tries to update them can fail.

B is not the correct consideration here.

D is not the best answer because the issue described is about ownership-based access to Accounts and Contacts, not simply whether a process version is active.

===========

The correct answer is A. Path.

Sales managers want reps to see recommendations, sales strategies, and key fields at each step of the Opportunity sales process. Salesforce Path is designed for exactly this. Path can highlight key fields and provide customized Guidance for Success for each stage of a process.

For Opportunities, Path can show reps which fields matter at each sales stage and provide stage-specific guidance such as qualification tips, sales strategy, or next-step recommendations.

C. Approval Process is for record approval routing.

D. Global Action is for creating or updating records quickly, not guiding users through sales stages.

B is not the correct Salesforce feature for this requirement.

===========

Queues are represented through Salesforce Group records, and their stable programmatic identifier is the DeveloperName , or API name. A flow that determines a regional queue dynamically can first calculate the appropriate queue API name in a text or formula resource and then use Get Records against the Group object, filtering DeveloperName to that value and Type to Queue. Salesforce ' s current Flow guidance provides this exact architecture for dynamically resolving queues rather than hard-coding IDs. Hard-coded user or queue IDs are brittle across environments and conflict with the dynamic-routing requirement. An asynchronous path changes execution timing but does not resolve the assignee. A custom Task text field likewise does not establish an actual queue assignment. Therefore, the formula-resource plus Get Records pattern is the correct declarative solution.

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