Free Practice Questions for Salesforce Platform-App-Builder Exam

The correct answer is A because the rule must fire only when Sales Organization = Canada and Pricing Tier is blank.

ISPICKVAL() checks whether a picklist equals a specific text value, and TEXT() converts a picklist value into text so ISBLANK() can evaluate whether it is empty. Salesforce documents ISPICKVAL() for comparing picklist values and TEXT() for converting picklist values in formulas.

Why others are incorrect:

B has invalid formula structure.

C uses incorrect picklist blank logic.

D uses OR , which would require Pricing Tier even when Sales Organization is not Canada.

===========

The correct answers are C. Email Alert, D. Task, and E. Outbound Message.

In a standard Salesforce approval process, available approval action types include Email Alerts, Tasks, Field Updates, and Outbound Messages. Since Field Update is not listed in the answer choices, the three valid action types from the options are Email Alert, Task, and Outbound Message. Salesforce documentation identifies approval-process actions around task, email alert, field update, and outbound message automation.

A. Invocable Flow is incorrect because it is not a standard approval-process action type in this exam context.

B. Decision Element is incorrect because Decision is a Flow element, not an approval-process action.

===========

The correct answer is A. Quick Action on the Account object.

Universal Containers wants users to create Opportunity records related to an Account, with many Opportunity fields automatically populated from the Account and some fields entered by the user. The best solution is an object-specific Quick Action on Account that creates an Opportunity. Object-specific actions run in the context of the parent record, and predefined field values can automatically populate fields to make record creation faster and more consistent.

C is incorrect because a Quick Action on Opportunity would not naturally start from the Account context. B and D are incorrect because assignment rules are not used for creating related Opportunities or prepopulating fields.

===========

The correct answers are B. Flow Builder and D. Escalation rules.

Escalation rules are the most direct Salesforce Service feature for this requirement. They are designed to automate case escalation when cases are not resolved or not acted on within a defined time period. Salesforce documentation explains that escalation rule entries can use business hours, and escalation actions can send notification emails when the case escalates.

Flow Builder can also be used because record-triggered flows support scheduled paths, allowing automation to run after a defined time from a triggering record event. A flow can check whether the Case is still in New status and then send a notification. For strict business-hour calculation, the app builder must design the flow carefully around the correct time source/business-hour logic.

A is incorrect because validation rules only prevent invalid data from being saved; they do not wait four business hours and send notifications.

C is incorrect for the Platform App Builder context because Scheduled Apex is a programmatic approach, while declarative automation tools are available and preferred for this requirement.

===========

The correct answer is A. Highlights panel.

In Lightning Experience, record actions such as New Task appear in the Highlights Panel area of the Lightning record page. Salesforce documentation explains that the actions in the highlights panel come from the object’s page layout, specifically the Salesforce Mobile and Lightning Experience Actions section, unless dynamic actions are enabled.

Since the custom action was already added to the Mobile & Lightning Actions section on the page layouts, the app builder must add the Highlights Panel component to display those actions on the Lightning record page.

Activities shows activity timeline/composer-related functionality, but it is not where page-layout actions are generally displayed. Related Lists and Related Record do not display the main action bar.

===========

A criteria-based sharing rule can identify Project records according to the Department field and share matching records with the appropriate public group. Salesforce documents that criteria-based sharing rules determine which records are shared based on field values and can grant access to public groups. Administrators can therefore maintain departmental public-group membership as employees change roles. When an employee leaves one department, removing that user from its public group removes the sharing path to those departmental Projects after sharing recalculation. Permission sets and profiles control object and field permissions but are not targets for criteria-based record-sharing rules. Account Teams apply specifically to Account collaboration and are unrelated to a custom Project object. With Project OWD set to Private, public groups plus criteria-based sharing provide the required controlled departmental visibility.

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

The correct answer is A. Add the field to the custom report type field layout.

The report already exists: Position with or without Applicants Report. The issue is not that reporting is disabled for the object; the issue is that the new Applicant field is not available as a column in that custom report type. For custom report types, fields available to report builders are controlled by the custom report type field layout. Salesforce’s documentation for adding fields to a custom report type directs admins to open the report type and use Edit Layout to add the missing fields.

B is incorrect because field-level security can hide a field from a user, but the troubleshooting step for a field missing from a custom report type column list is to add it to the custom report type layout.

C is incorrect because the report type already exists and is being used.

D is incorrect because the field data type was already assigned when the field was created.

===========

The correct answer is B. Edit a record page using Lightning App Builder > Drag the component onto the page.

A custom Lightning component installed from AppExchange is configured on a Lightning record page through Lightning App Builder. Salesforce documentation states that Lightning App Builder supports custom Lightning components, including Aura and Lightning web components, and record pages are edited as Lightning pages.

The Page Layout editor is used for fields, buttons, related lists, and layout behavior, not for placing Lightning components on a Lightning record page. App Manager manages apps and utility bars, but the page canvas configuration is done in Lightning App Builder.

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 correct answers are B. Cross-object field updates between Training and Student records are not supported and C. On Training record, the Student Lookup field can be made optional.

This question is about creating a Student lookup field on the Training object. A lookup relationship is a looser relationship than master-detail. Salesforce documentation explains that lookup relationships do not support roll-up summary fields, unlike master-detail relationships.

Because this is a lookup relationship, the Student lookup field on Training can be optional unless the app builder marks it required. Cross-object field updates are also not supported in this lookup relationship scenario; Salesforce documents that cross-object field updates work for master-detail relationship scenarios, not normal lookup relationships.

A is incorrect because roll-up summary fields require a master-detail relationship.

D is incorrect because deleting Student records is controlled by object permissions and relationship delete behavior, not simply by access from the Training record.

===========