Free Practice Questions for Salesforce Platform-App-Builder Exam

Flow Builder supports debugging a flow as another user, allowing an administrator to execute the flow under that user ' s profile, permission sets, object permissions, and field-level security. This is exactly what is needed to reproduce a permission-context failure. Salesforce documents the Run flow as another user option under Flow Builder ' s Debug functionality. However, Salesforce also specifies an important current-platform restriction: debugging as another user is supported only in a sandbox/non-production environment . Therefore, the intended solution is C, with the production flow first available in an appropriate sandbox for safe testing. Options A and D require involvement from the sales rep, while B analyzes an existing failure rather than actually reproducing it in the user ' s security context.

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

The Repeater component is specifically designed to collect and modify multiple instances of the same type of information within a Screen Flow. Salesforce supports using a record collection as the Repeater ' s data source, allowing existing records to be prepopulated. At runtime, users can modify those items and, when configured, add or remove additional instances. That directly matches the requirement to display existing Order Line Items while permitting users to add new line items within the same interactive screen. A Data Table is primarily intended to display and select records rather than provide this repeated add/edit data-entry pattern. Section only organizes screen components, while Slider captures a numeric value. Salesforce ' s current Repeater functionality explicitly supports prepopulated records together with user additions and modifications.

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

The correct answer is A. Schema Builder.

Schema Builder lets an app builder quickly create and view custom objects, fields, and relationships from one visual interface. Salesforce Trailhead states that Schema Builder is used to visualize and edit the data model, including objects, fields, and relationships.

Lightning Object Creator is mainly used to create objects and fields from a spreadsheet. Manage Field Permissions controls access, not object creation. Developer Console is not the recommended point-and-click tool for this requirement.

===========

The correct answer is D. Approval process.

The requirement is to automate travel request form submission and enforce an internal approval policy. Salesforce approval processes are specifically designed to automate how records are submitted, reviewed, approved, rejected, recalled, and acted upon. Salesforce Trailhead explains that an approval process defines the criteria a record must meet before submission, the approval steps, approvers, and the actions taken when the record is approved or rejected.

This exact scenario also aligns with Salesforce’s travel approval training example, where a Travel Approval object uses an approval process to route travel requests to the employee’s manager and, when needed, to another approver.

A is incorrect because assignment rules route leads or cases, not approval requests.

B is incorrect because validation rules prevent invalid saves but do not manage approval routing.

C is incorrect because Apex is unnecessary when a standard declarative approval process fits the requirement.

===========

The requirement specifies that a new vendor must accept terms on Agreements before an Opportunity can be closed. Salesforce Approval Processes are the declarative solution for enforcing such business rules. An approval process can:

Require users (vendors) to accept or approve records (Agreements).

Prevent Opportunities from moving to a closed stage until approval is completed.

Send email notifications automatically to approvers.

Salesforce documentation confirms that approval processes are used to enforce conditions on record lifecycle and ensure required steps are completed before record status changes. (Salesforce Help)

A. Email Alert cannot enforce record progression.

B. Dynamic Action only controls field-level UI visibility, not enforcement.

D. Validation Rule could prevent saving a record, but it cannot require explicit approval from a specific user group.

===========

The correct answer is B. Universal Containers has internal Account OWD set to Public Read/Write, which lets internal users broadly access Account records. However, Experience Cloud / customer community users can have a separate external sharing model. Salesforce documentation explains that External Organization-Wide Defaults provide separate default access for external authenticated users so companies can better secure data for community users.

Setting the Account external OWD to Private prevents customer community users from seeing all company Account records by default.

Why others are incorrect:

A record types do not control record visibility.

C an owner-based sharing rule would grant more access, not restrict default access.

D permission sets grant object/field permissions; they do not replace OWD record-sharing control.

===========

The correct formula is:

IF(

NOT(ISBLANK(Nickname__c)),

Nickname__c,

FirstName

)

Salesforce recommends ISBLANK() to check whether a field has no value, including text fields. Since Nickname__c is optional, the formula first checks whether it is not blank. If it has a value, Salesforce uses the nickname. If it is blank, Salesforce uses FirstName .

A is incorrect because BLANKVALUE() is not used this way inside NOT() .

B is incorrect because the logic is reversed and ISNULL() is not preferred for text fields.

D is incorrect because TEXT() is not needed for a text field and does not perform a blank check.

===========

The correct answers are B. Upload the lead list using the Import Wizard and select a Matching Type to prevent duplicate lead creation and D. Utilize a Lead Matching Rule and corresponding Duplicate Rule to block newly created duplicate leads.

For 400 leads, the Data Import Wizard is appropriate because Salesforce supports importing leads and other common objects with the wizard, and it can handle up to 50,000 records.

Salesforce documentation for lead imports states that choosing a matching type sets criteria for avoiding duplicate leads when using the Data Import Wizard.

Duplicate Management also uses matching rules and duplicate rules to identify and control duplicates. Salesforce states that duplicate rules can block users from creating duplicate records, including lead duplicates.

Why others are incorrect:

A is incorrect because Data Loader’s update operation updates existing records and normally requires record IDs or proper matching/upsert configuration; it is not the best duplicate-prevention answer here.

C is not the correct Salesforce setup wording. The correct tools are Lead Matching Rules and Duplicate Rules.

===========

The five permissions common to the entire department should be bundled into a permission set group. Salesforce defines permission set groups as a mechanism for combining multiple permission sets around a job persona or role, simplifying assignment and ongoing maintenance. Users assigned to the group receive the combined permissions from its component permission sets. Higher-level staff can then receive the same permission set group plus additional individual permission sets that represent their extra responsibilities. This avoids repeatedly assigning the same five permission sets one-by-one and supports least-privilege access. Data Import Wizard is not the standard administration mechanism for permission-set assignments, and Data Loader is unnecessary for the described configuration. The Manage Assignments approach with a permission set group plus individual exceptions provides the cleanest scalable permissions model.

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

The correct answers are A. Dynamic Actions and C. Approval Process.

An Approval Process is required because sales managers must provide formal sign off when an Opportunity discount meets the defined criteria. Salesforce approval processes define the criteria a record must meet, the steps required for approval, and who must approve it.

Dynamic Actions are also needed because Universal Containers wants the sign-off action available quickly from the Opportunity record page. Dynamic Actions let app builders control which actions appear on Lightning record pages based on conditions.

Why others are incorrect:

Schema Builder is for data model design, not approval/sign-off UI behavior.

Validation Rule can block invalid data, but it does not provide manager approval or sign-off.

===========