Free Practice Questions for Salesforce Platform-App-Builder Exam

The correct answer is D. Choose an unmanaged package from AppExchange that closely meets the requirements of the project and allows programmatic development.

The requirement has two key parts: the app builder has very little time, and the solution must be fully customizable. Salesforce documentation describes unmanaged packages as suitable for one-time drops of applications that require customization after installation. That fits this scenario better than building everything from scratch.

C is incorrect because managed packages are better for distributed, upgradeable AppExchange apps, but they can restrict subscriber changes to packaged components. The question specifically says the solution still needs full customization, which points to an unmanaged package.

The correct answer is C. Internal profiles.

When an app builder creates a custom field using Schema Builder, Salesforce sets field-level security for custom fields to visible and editable for internal profiles by default.

That is why B. All profiles is not the best answer. Salesforce’s documented default is specifically internal profiles, not every possible profile type.

===========

The correct answer is C. A Galaxy__c with Star__c report type will be automatically created.

When a master-detail relationship is created between a parent custom object and a child custom object, Salesforce can automatically generate a standard report type for the parent object with the child object, such as Galaxy__c with Star__c, assuming reporting is enabled for the objects. Salesforce documentation confirms that standard report types are created in certain object relationship scenarios, including lookup and master-detail relationships.

Why the other options are incorrect:

A is incorrect because the report type is based on the parent with child, not the child object with the parent merely as a field.

B is incorrect because a custom report type is not required for this basic master-detail reporting scenario.

D is incorrect because the report type is not created as Star__c with lookup fields from Galaxy__c.

===========

Use a Record-Triggered Flow optimized for Actions and Related Records.

Submitting a record for approval is an action in Flow. Salesforce provides a Submit for Approval action, and after-save record-triggered flows are used when the automation needs to perform actions or work with related records after Salesforce saves the triggering record.

Option A is wrong because Fast Field Updates is the before-save path, mainly for updating fields on the triggering record. It is not the right optimization for submitting an approval request. Option B still requires a custom button and manual user action. Option C is unrelated because this requirement is based on an Opportunity record change, not a platform event.

===========

The correct answer is B. Use an AppExchange solution.

UC has a time-sensitive need and the developers are delayed for several months. AppExchange is the best recommendation because it provides ready-to-install apps, components, and solutions that can extend Salesforce without building everything from scratch. Salesforce describes AppExchange as the marketplace for ready-to-install solutions, including apps, components, and experts.

A and C still require building the solution internally. D. Bolt solution is more specific to prebuilt Experience Cloud/community templates and is not the best answer for a general custom component requirement. Salesforce describes Bolt Solutions as combinations of Lightning apps, business process flows, and Experience Builder templates/pages.

===========

The correct answer is A. Web-to-Case is the Salesforce feature designed to let visitors submit case information from a public-facing website. Salesforce documentation states that Web-to-Case is set up by enabling the feature, creating and customizing a web form, and adding that form to a website.

Why others are incorrect:

B. Outbound message sends data out of Salesforce; it does not create cases from a website.

C. Screen flow could require extra site/guest-user setup and is not the standard feature for this requirement.

D. Email-to-case creates cases from inbound email, not directly from a public web form.

The correct answer is D.

Validation rules are the right declarative tool to enforce data compliance before a record is saved. They can prevent a Case from moving backward to an earlier Status and can require specific fields when Case criteria are met. Salesforce formula functions such as ISCHANGED() compare whether a field value changed, and validation rules can use formula logic to stop invalid saves.

Why others are incorrect:

Approval Process is for routing records for approval.

Dependent picklists control picklist value availability, not status regression.

Case Flow can automate case processes, but validation rules are the best tool for enforcing save-time compliance.

===========

Collection Sort is designed to reorder a collection and optionally reduce the number of records retained after sorting. Salesforce documents that the Collection Sort element can sort a record collection by a selected field in ascending or descending order and can specify the maximum number of items to keep afterward. The flow should therefore sort the Opportunity collection by Amount in descending order and retain only five records. A Collection Filter selects records based on Boolean-style criteria, but it does not identify the top N records based on ranking. A Decision controls execution paths rather than restructuring a collection. Transform maps data between structures but is not intended to rank and limit records. Collection Sort directly implements both requirements—highest Amount first and only five records retained.

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

Salesforce requires installation records to be directly associated with Opportunities, and sales reps need visibility of all installations tied to their Opportunities. A Master-Detail relationship is the correct solution because:

The Installation object (detail) inherits sharing and security from the Opportunity (master), ensuring sales reps see only their related installations.

Enables roll-up summaries on Opportunity if needed.

Salesforce documentation confirms that Master-Detail relationships provide parent-controlled ownership and access, making them ideal for enforcing related record visibility. (Salesforce Help)

B. Hierarchical is only available for User object.

C. Many-to-Many requires a junction object; not needed here.

D. Lookup allows optional, independent access; would not automatically enforce visibility.

===========

The correct answers are A. Create an object-specific action on Account and D. Create predefined values for most of the fields.

For this requirement, sales reps need to create a custom Feedback record related to an Account with minimal clicks on mobile. An object-specific quick action is the best solution because it runs in the context of a specific Account record and can create a related child record automatically. Salesforce Trailhead states that object-specific actions let users create records with automatic relationships to other records and provide a streamlined mobile and desktop experience.

Predefined field values reduce manual typing and save mobile users time. Salesforce mobile customization guidance explains that quick actions can include predefined fields, and Trailhead specifically shows predefined values being used to prepopulate fields on action layouts.

B. Create a feedback object as a parent of Account is incorrect because the Feedback record should be related to each Account, normally as a child record or lookup-related record. C. Create a global action on Account is incorrect because global actions create records without record context; Salesforce explains that global actions create records with no relationship to other records, while object-specific actions work in the context of a particular object.

===========