Free Practice Questions for Salesforce Platform-App-Builder Exam

The correct answers are C. Custom object, D. Apex class, and E. Custom field.

Change sets are used to move metadata between related Salesforce environments, such as sandbox and production. Salesforce documentation confirms that change sets can migrate components such as custom objects, custom fields, and Apex classes. Salesforce also notes that custom fields can be migrated individually in a change set.

A. Web-to-lead is not one of the common metadata components normally selected as an item in this exam context. B. Standard fields are standard Salesforce metadata and are not moved like custom fields in change sets.

===========

Permission Sets are the appropriate mechanism for granting additional object and field access to users who perform a particular function without changing their base profiles. The app builder can create a permission set for hiring managers that grants the required access to JobApplication__c and Read access to the sensitive salary fields through field-level security. Salesforce specifically recommends permission sets and permission set groups rather than profiles for extending field permissions. Sharing Rules and organization-wide defaults govern record-level access; they do not make fields visible when field-level security hides them. Page Layouts control which fields are placed in the interface but cannot override field-level security. Because salary information represents restricted field-level data that only a designated functional group should see, Permission Sets provide the precise least-privilege solution.

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

The correct answers are C. Currency, D. Date, and E. Percent.

Salesforce roll-up summary fields support different field types depending on the summary operation. For SUM, Salesforce supports number, currency, and percent fields. For MIN and MAX, Salesforce supports number, currency, percent, date, and date/time fields. Therefore, from the options given, Currency, Date, and Percent are valid field types for roll-up summary calculations.

Checkbox is not a supported field type for roll-up summary aggregation. Time is not the intended supported option in this exam context.

This question is testing the classic Salesforce Process Builder automation best practice , not a generic Flow-only rule. Salesforce’s official process design guidance states that an org should have only one record-change process per object . The reason is simple: every time a record is created or updated, Salesforce evaluates the record-change processes for that object. If an object has multiple record-change processes, the automation becomes harder to predict, harder to troubleshoot, and more likely to hit governor limits. Salesforce specifically explains that consolidating automation into one record-change process gives admins a single view of all criteria and actions for that object, reduces duplicated automation overhead, and allows the app builder to control the order of criteria evaluation.

A is not the best exam answer here. In modern Flow architecture, “one Flow per object” is often discussed as a design pattern, but it is not the exact best-practice wording being tested by this Platform App Builder-style question. Salesforce Flow design is more nuanced today because record-triggered flows can vary by trigger timing and event. B is wrong because validation rules should be separated by validation requirement, not forced into one rule per object. C is wrong because invocable processes are reusable modular processes, not the main record-change automation container.

The correct answer is B. Field-level security.

Only users with the Outer Planets profile need to see the Jupiter field. Salesforce field-level security, also called field permissions, controls whether users can view or edit individual fields on an object. This is the proper way to restrict a field by profile or permission set.

Sharing rules control record-level access, not field visibility. Filtered views affect list views, not field security. Classic encryption protects sensitive data but is not the correct feature for profile-based field visibility.

===========

The correct answer is B. Clone the change set and re-deploy.

After a change set has been uploaded, Salesforce does not allow its contents to be changed. Salesforce documentation states that after upload, the change set contents cannot be changed; to redeploy the same set of components, the app builder should clone the change set, and the cloned change set includes the latest changes to its components from the source org.

A is incorrect because renaming does not update uploaded components. C is unnecessary. D is incorrect because an uploaded change set cannot simply be updated and redeployed.

The formula must evaluate true when:

Stage = Negotiation/Review

Close Date < 1 week from today

Salesforce formula functions used:

ISPICKVAL() for picklist equality checks

AND() to combine multiple conditions

CloseDate < TODAY() + 7 to check the Close Date is within one week

Correct formula:

AND(

ISPICKVAL(StageName, " Negotiation/Review " ),

CloseDate < TODAY() + 7

)

Options A, C, D use invalid syntax (missing quotation marks, incorrect function structure).

Salesforce Help confirms correct syntax for picklist comparison and date arithmetic in formula fields. (Salesforce Help)

This formula evaluates true only when both conditions are simultaneously met.

===========

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. Create a new text field and import the formula field values in it.

The existing Specialty__c field is a formula field, so users cannot manually edit it. Formula fields calculate their value automatically from other fields. Since Cloud Kicks now wants Opportunity Specialty__c values to be different from the related Account value, the app builder should create a new editable field, such as a Text field, and then load the existing calculated formula values into that new field for existing Opportunity records.

This preserves historical Opportunity values while allowing sales reps to enter or update Specialty values going forward. Salesforce documentation explains that roll-up/formula-style calculated values are system-derived, while changing custom field types has limitations and requires care when data must be preserved.

A and B are incorrect because a formula field cannot simply become an editable text field while safely preserving all existing calculated values.

C is incomplete because creating a new text field without importing the existing formula values does not preserve the current values on existing Opportunities.

===========

The correct answer is B. Cross-object formula.

Opportunity has a standard relationship to Account, so an app builder can create a formula field on Opportunity that references the parent Account field. Salesforce defines a cross-object formula as a formula that spans related objects and references fields on those related objects.

Because Account_Region__c is a picklist on Account, the Opportunity formula would commonly be a text formula like:

TEXT(Account.Account_Region__c)

Field history tracking only tracks changes, a lookup field would create a relationship rather than display the Account field value, and field-level security controls visibility but does not copy or display the parent field on Opportunity.

===========