Free Practice Questions for Salesforce Platform-App-Builder Exam

The requirement specifies detailed descriptions that can include pictures and links. Salesforce Rich Text Area fields support:

Multiple lines of text

Inline images

Hyperlinks

Formatting (bold, italic, lists)

Salesforce documentation confirms that Rich Text Area fields are the standard choice when storing formatted content on a record. (Salesforce Help)

D. Long Text Area supports only plain text, not images or links.

C. URL is for a single web address only.

B. Lightning Web Component is for custom UI elements, not a field type.

===========

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 D. Patch.

In application lifecycle management, patch releases are used for bug fixes and simple, low-impact changes. Salesforce packaging documentation also describes patch versions as minor upgrades used for fixing bugs or errors.

Major releases are for large changes or significant new functionality. Minor releases are usually for limited-impact enhancements. Roll is not the correct ALM release category here.

===========

The lookup field is created on the custom object Box and points to Account. That makes Account the parent-side object and Box the related child object. Salesforce automatically creates a standard relationship report type in the format Parent Object with Child Object, so the report type is Accounts with Boxes. Salesforce Help confirms that standard report types can be generated automatically when reportable custom objects have lookup relationships.

Why others are incorrect:

A. Boxes with Accounts starts from the child object perspective.

C and D include “with or without,” which is normally configured through custom report type relationship options, not the automatically created standard relationship report type.

===========

The correct answers are A. Create a child record, C. Update a related record, and D. Send an email alert.

Process Builder was designed to automate repetitive business actions. Salesforce documentation describes Process Builder as a tool for automating tasks, emails, and record updates.

Process Builder can improve productivity by performing actions such as:

Create a child record — Process Builder can create a record when criteria are met.

Update a related record — Process Builder can update the record that started the process or related records.

Send an email alert — Salesforce documentation specifically states that a process can send an email by using an email alert.

B is incorrect because “Start an additional message” is not a standard Process Builder productivity capability.

E is incorrect because Process Builder does not delete related records as a standard declarative action.

===========

The correct answer is B.

Salesforce supports roll-up summary fields for summarizing related records, including scenarios involving Account and related Opportunity values. However, Salesforce documentation states that if Advanced Currency Management is enabled, currency roll-up summary fields are invalid when they are on Accounts and summarize Opportunity values.

Because the VP wants to aggregate Opportunity Amount values on Account, the app builder cannot create that roll-up summary field if Advanced Currency Management is enabled.

Why not others:

A is not the stated Salesforce limitation.

C is wrong because roll-up summary fields are available on Account in supported scenarios.

D is wrong because currency fields can be used in roll-up summaries generally; the issue is specifically Advanced Currency Management with Account-to-Opportunity currency rollups.

The correct answers are B. Apex and C. AppExchange.

Cloud Kicks needs to count related Case records on Account based on open and closed status. Standard roll-up summary fields work only in supported roll-up relationships, mainly master-detail relationships. Salesforce documentation states that lookup relationships do not support roll-up summary fields.

Because Cases are related to Accounts through a lookup-style relationship, native roll-up summary fields are not the best available option in this answer set. The app builder can meet the requirement by using:

Apex — Apex triggers can run before or after record changes such as insert, update, or delete, allowing custom logic to recalculate the open and closed Case counts on the Account.

AppExchange — AppExchange roll-up tools, such as lookup roll-up packages, can summarize records across lookup relationships without building custom code.

Why others are incorrect:

Validation Rule prevents invalid data entry; it does not calculate related record counts.

Approval Process routes records for approval; it does not summarize Case counts.

===========

A managed package is designed for distributable Salesforce solutions whose components can be maintained and upgraded by the package provider. Salesforce states that managed packages provide fully upgradeable application resources, and AgentExchange guidance distinguishes them from unmanaged packages by specifically noting that providers can automatically upgrade managed solutions. This makes a managed package appropriate when Universal Containers wants a complete preconfigured application while minimizing ongoing manual maintenance. An unmanaged package provides editable components but does not have the same provider-managed upgrade mechanism; receiving a newer unmanaged version generally requires replacement or reinstallation. A change set transfers metadata between related Salesforce orgs and is not an AgentExchange distribution package. A data kit is not the package type used to deliver an upgradeable Salesforce application.

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

The correct answers are B. External ID and C. Unique.

The legacy ID field should be marked as External ID because Salesforce can use an external ID field to match records during import, integration, and upsert operations. Salesforce documentation confirms that external IDs can be used to create or update records through upsert.

The field should also be marked Unique so Salesforce prevents duplicate legacy ID values. Salesforce custom field attribute documentation states that the Unique option prevents duplicate field values.

Why others are incorrect:

A is incorrect because encrypted text is not the right choice for a matching legacy ID used in upserts.

D is not the best answer because making the field required does not enable upsert matching or prevent duplicate external IDs.

===========