Free Practice Questions for Salesforce Platform-App-Builder Exam

The correct answer is C. Flow.

The requirement is to automatically delete rejected Quote records. Salesforce Flow is the correct declarative automation tool because Flow can identify records and delete them using the Delete Records element.

Why not the others:

Approval Process routes records for approval. Einstein Next Best Action recommends actions. Validation Rule prevents bad saves. None of those tools is designed to delete rejected child records automatically.

===========

The correct answers are C. Text field and D. Number field.

Salesforce allows custom Text, Number, Email, and Auto Number fields to be marked as External ID fields. Since the available choices include Text and Number, those are the two valid answers.

Why others are incorrect:

A. Phone field cannot be marked as an External ID.

B. URL field cannot be marked as an External ID.

===========

Feed Tracking is the correct feature because Salesforce can automatically generate feed updates when a tracked field changes on a record. Salesforce Help explains that feed tracking detects changes to tracked record fields and posts updates to the feed. It can also be configured for custom objects.

For this scenario, the app builder would track the travel request approval/status field. When the request becomes Approved, Salesforce posts that tracked change automatically on the record feed.

Why others are incorrect:

Auto-response rule sends automatic email responses, mainly for Lead/Case scenarios.

Approval process manages record approval routing, but the feature that creates automatic feed posts for field changes is Feed Tracking.

Feed quick action is manual, not automatic.

===========

The correct place to verify whether a change set can be deployed is Inbound Change Sets in the target org, normally Production.

Salesforce guidance says that after uploading a change set from the source sandbox, the app builder goes to Setup → Inbound Change Sets, opens the change set awaiting deployment, and clicks Validate. Validation checks whether the deployment succeeds or fails before committing the changes.

A. Deployment Settings is mainly used to authorize deployment connections and allow inbound changes from another org. C. Deployment Status is used to monitor deployment progress/results, not to initiate validation of an inbound change set.

\

The correct answer is B. Use field-level security on page layouts with record types to restrict editing fields.

The requirement changes after the Opportunity is closed. The best configuration is to use record types with assigned page layouts so the closed Opportunity layout can make most fields read-only while allowing the Sales Operations team to edit the two post-close fields. Salesforce page layouts can control which fields are visible, read-only, or required, and page layouts can be assigned by profile and record type.

A is incomplete because it does not account for different behavior after close. C is incorrect because field sets are not used for page-layout field editability. D is too broad because it would make fields read-only for the Sales profile regardless of Opportunity stage.

Executing Get Records inside a Loop generates another SOQL query for every iteration. In bulk processing, that pattern can quickly exceed Salesforce ' s per-transaction SOQL governor limit. Salesforce explicitly documents that a Flow retrieving records from inside a Loop can consume one SOQL query per iteration and fail after exceeding the transaction limit. The correct bulkification pattern is to retrieve the needed records once outside the Loop, store them in a collection, and then iterate over the already-retrieved data. Changing from after-save to before-save does not eliminate repeated queries. A Fault Path can handle an error but does not prevent the governor limit from being reached. Replacing the Loop with Assignment is not appropriate when multiple items still require iteration. Moving Get Records outside the Loop resolves the root architectural problem. Salesforce

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

When deploying from sandbox to production using Change Sets, the following are critical considerations:

A. Transactions will revert if the deployment errors – Salesforce applies deployments as a single transaction; any failure rolls back the deployment to maintain org integrity.

D. Change sets do not include all components and may require manual configuration – Certain components, such as record data or some metadata, may need manual setup or additional deployment steps.

Salesforce documentation emphasizes that change sets cannot deploy everything and must be carefully reviewed before validation. (Salesforce Help)

B. Users being logged out is not required; deployments can occur while users are logged in.

C. Salesforce Connect does not automatically link environments; it is unrelated to change sets.

===========

Current Salesforce documentation makes C the correct answer. Salesforce Help states that to enforce validation rules during Lead conversion, the Require Validation for Converted Leads setting must be enabled under Lead Settings. If it is disabled, validation automation that would otherwise protect the resulting Account, Contact, or Opportunity can be bypassed during conversion. Therefore, missing information on Accounts created through Lead conversion indicates that this Lead setting has not been enabled.

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

Grouping is the correct reporting capability because the requirement is to compare Case counts across two categorical dimensions: Status and Priority. Salesforce reports support grouping records by rows and columns. The app builder can group Cases by Status and then by Priority, or configure a matrix-style report using one field for row grouping and another for column grouping. The resulting subtotals and grand totals make the comparison immediately visible. Filters determine which records are included but do not organize the resulting records into comparison categories. Bucket columns are useful for creating temporary categories without adding Salesforce fields, but Status and Priority already provide the required categories. A custom report type controls which related objects and fields are available, not how existing Case records are grouped.

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

The correct answer is C. Developer sandbox.

For small, individual projects where teams need separate environments before moving work into a larger shared testing sandbox, a Developer sandbox should be considered first. It is intended for development and testing of configuration changes in an isolated environment and is the lowest-cost sandbox option compared with Developer Pro, Partial, and Full sandboxes. Salesforce describes sandbox types for different testing and development needs, with Developer and Developer Pro sandboxes copying configuration/metadata rather than full production data.

Developer Pro provides more storage, but the question emphasizes small projects and keeping costs down. Partial and Full sandboxes are better for broader testing with data, but they are not the first choice for many small isolated development efforts.

===========