Free Practice Questions for Salesforce Platform-App-Builder Exam

The correct answer is C. Use Dynamic Forms to display the Years of Previous Experience field if Previous Experience is checked.

This is a conditional field-visibility requirement. Salesforce Dynamic Forms lets app builders manage fields and sections directly in Lightning App Builder and use visibility rules to show users only the fields they need, when they need them.

So the app builder can place the Years of Previous Experience field on the Dynamic Forms-enabled record page and set visibility so it displays only when Previous Experience = True.

A is unnecessary and overcomplicated.

B is incorrect because field dependencies apply to picklists, not checkbox-to-number visibility.

D is incorrect because Visualforce is unnecessary when Dynamic Forms provides a declarative solution.

===========

A schedule-triggered flow is appropriate when Salesforce must periodically identify records approaching a date and perform an automated action. Salesforce documents schedule-triggered flows as automation that runs at a specified time and frequency for batches of records. A daily scheduled flow can use Get Records to identify Contracts whose End Date is five days away, obtain the related Account information, and invoke Send Email for the Account owner. Salesforce provides the same architectural pattern for expiration reminders, where a daily schedule-triggered flow checks records and sends notifications a specified number of days before expiration. Screen Flow requires user interaction, while an autolaunched flow does not independently provide the required recurring schedule.

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

The correct answer is B. Quick action.

Sales reps need to create Opportunity records directly from an Account, with several fields prepopulated. This is an object-specific Quick Action use case. Salesforce states that object-specific actions let users create or update records in the context of a particular object. Salesforce also supports predefined field values for quick actions, which can prepopulate fields and make record creation faster.

Default action is not the correct feature name for this requirement. Custom button and custom link are older navigation-style tools and are not the best Lightning/mobile-friendly option for creating related records with predefined values.

===========

The intended answer is D , because the validation must check two error conditions before allowing the Opportunity to be saved as Closed Won :

Scheduled_Ship_Date__c is blank.

Scheduled_Ship_Date__c is more than 14 days after CloseDate .

Salesforce validation rules fire when the formula evaluates to True . Salesforce’s formula documentation confirms that ISPICKVAL(picklist_field, text_literal) is the correct syntax for comparing a picklist field such as StageName . Salesforce validation examples also show date arithmetic such as subtracting one date from another to check whether a date exceeds a required range.

The option text appears corrupted, but the correct exam concept is a validation rule that blocks Closed Won if the Scheduled Ship Date is blank or more than 14 days after the Close Date.

===========

The correct answer is D. Rich text area.

The requirement says users need to write detailed descriptions that can include pictures and links. Salesforce Rich Text Area fields are designed for formatted text and support images and hyperlinks.

Long text area supports longer plain text but not rich formatting with images. URL stores a single web address. Multi-select picklist stores selected values, not detailed formatted descriptions.

===========

The correct answer is A. The requirement is to combine four custom text fields into one formula field and display the result on two lines.

The formula works as follows:

Street__c displays the street on the first line.

BR() inserts a line break. Salesforce documents the BR formula function as inserting a line break in a text string.

City__c & " , " & Planet__c & " " & Galaxy__c displays the remaining location information on the second line. The & operator connects two or more strings in Salesforce formulas.

Why others are incorrect:

Options using field names without __c are not correct for custom fields. Options using __r are relationship references, not direct custom field references. Options without BR() do not satisfy the two-line requirement.

===========

A Template-Triggered Prompt Flow is specifically designed to provide dynamically retrieved Salesforce data and additional logic to Prompt Builder templates. Salesforce states that these flows perform logic and actions that generate output text merged into the associated prompt template. The app builder can retrieve the Contact ' s related Order records, construct appropriate prompt instructions, and pass that grounded context back to the Field Generation prompt template. Salesforce also documents the Add Prompt Instructions element as available specifically in template-triggered prompt flows. A record-triggered flow responds to database changes, while a schedule-triggered flow runs at predefined intervals. A generic autolaunched flow does not provide the dedicated Prompt Builder integration required by the scenario. Therefore, A is the correct flow type for grounding this prompt template.

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

The correct answer is C. A delegated approver is the recommended Salesforce feature when the assigned approver is unavailable, such as during vacation. Salesforce documentation confirms that users can identify a delegate in approval settings, and delegated approvers can approve or reject approval requests.

This ensures the closed-won Opportunity can still be reviewed before the leaderboard is updated, even though the owner’s manager is away.

Why others are incorrect:

A is not the best recommended setup because relying on an assistant to reassign requests is manual and reactive.

B is incorrect because forwarding approval requests is not the standard solution for planned approver absence.

D is incorrect because assignment rules do not assign delegated approvers for approval processes.

===========

The correct solution is to add a Rich Text component to the Case Lightning record page and then use component visibility so it only appears when the related Account’s support level is Platinum.

Salesforce Lightning App Builder supports visibility rules that show or hide components based on field criteria. Salesforce documentation confirms that visibility filters on record pages rely on field data associated with the page’s object, and related lookup fields can be used in visibility-rule considerations.

This is the best declarative solution because the requirement is only to display a text notification. A custom Lightning Web Component or cloned Lightning page is unnecessary.

Why others are incorrect:

A is incorrect because assigning a Case page to “platinum accounts” is not the correct assignment model.

C and D are incorrect because custom Lightning Web Components add unnecessary development effort for a simple text notification.

===========

The correct answer is A.

When custom tabs are deployed through change sets without profile settings or permission sets, the deployed custom tabs are hidden by default for all users. Salesforce Help states that deployed custom tabs are hidden by default unless the change set also includes profiles that set the tab visibility.

Tab visibility is controlled through profile or permission set tab settings such as Default On, Default Off, and Tab Hidden.

Why others are incorrect:

B and C are incorrect because the tabs are not automatically default off or default on for all users.

D is incorrect because the custom tabs are deployed; they are just not visible until access is configured.

===========