Free Salesforce Platform Administrator Practice Test Questions
Topic: Automation
148 questionsUpdated 17-Nov-20268 topics
TopicAutomation
Question 1Choose 1
A Platform Administrator at Universal Containers has a screen flow that helps users create new leads. When Lead Source is " Search Engine " , the administrator needs to require the user to choose a specific search engine from a picklist. If Lead Source is not " Search Engine " , this picklist should be hidden. What is the most efficient way for the administrator to complete this requirement?
Correct answer:
C. Create a picklist for Specific Search Engine, and set conditional visibility so that it is only shown when Lead Source is " Search Engine " .
Explanation:
In Salesforce Flows, the most efficient way to conditionally display a field on a screen is to use native conditional visibility on the screen component itself. This declarative feature shows or hides a field instantly based on another field's value without requiring extra assignment elements, filters, or validation rules.
Correct Option: C
Conditional visibility is a built-in property on screen components (e.g., picklist, input field).
Configure it with a simple rule: Show field only when {!LeadSource} = "Search Engine".
No additional elements, variables, or complex logic required.
This is the most efficient, low-code, and maintainable approach.
Incorrect Option: A
Conditional filter applies to choices within a picklist or lookup, not to showing/hiding an entire field.
It filters available options, not the visibility of the field itself.
Incorrect interpretation of Flow filtering capabilities.
Incorrect Option: B
Assignment elements can set variables but cannot conditionally show/hide a field on a screen at runtime.
You would need multiple screens or screen versions, which is inefficient and duplicate work.
Overly complex for simple conditional visibility.
Incorrect Option: D
Validation rules prevent saving invalid data but do not hide fields on a screen.
The user would still see the picklist and be confused, then receive an error upon submission.
Validation rules fire after input, not before; they do not control visibility during data entry.
Reference:
Salesforce Help Article: Add Conditional Visibility to Screen Components in Flow – Use the "Conditional Visibility" option on any screen component to show or hide it based on a formula or resource comparison. This is the most efficient method for hiding fields conditionally without extra elements.
Question 2Choose 1
The Cloud Kicks CFO requires any opportunity over $100,000 to be automatically sent to them, so they can sign off on the record before the deal closes. Which feature should a Platform Administrator use to fulfill this requirement?
Correct answer:
D. Flow Approvals
Explanation:
Salesforce provides a declarative Approval Process feature that automates record submission, routing, and approval decisions. When integrated with Flow (specifically Flows that launch approval processes), this is referred to as Flow Approvals. It allows automatic submission of opportunities over $100,000 to the CFO without requiring users to click a button manually.
Correct Option: D
Flow Approvals (Approval Processes launched via Flow) enable fully automated submission based on criteria (e.g., Amount > $100,000).
The Flow can run on record creation or update, check the amount, and submit for approval automatically.
No user button click required—meets "automatically sent" requirement.
Declarative, no code needed.
Incorrect Option: A
Submit for Approval button requires a user to manually click it on each eligible opportunity.
The requirement states "automatically sent," so a manual button does not fulfill it.
Can be part of a solution but is not the primary automatic feature.
Incorrect Option: B
Einstein Next Best Action recommends actions to users based on insights but does not automatically submit records for approval.
It is prescriptive, not automated submission.
Overkill and incorrect tool for approval routing.
Incorrect Option: C
Apex Triggers can execute approval submission code, but this is code-based and not the most efficient declarative solution.
Flow Approvals are preferred for low-code maintainability.
Triggers require developer resources and testing.
Reference:
Salesforce Help Article: Automate Approvals with Flows – Use Flow to automatically submit records for approval when criteria are met (e.g., Opportunity Amount > $100,000). This eliminates manual button clicks and fulfills automatic submission requirements declaratively.
Question 3Choose 1
Universal Containers requires that when an opportunity is closed won, all other open opportunities on the same account must be rendered as Closed Lost. Which automation solution should a Platform Administrator use to implement this request?
Correct answer:
A. Flow Builder
Explanation:
Flow Builder is the recommended declarative automation tool for complex, multi-record update logic triggered by a record change. In this scenario, when a single Opportunity is updated to Closed Won, Flow can query all other open Opportunities on the same Account and update them to Closed Lost—all in one automated process without code.
Correct Option: A
Flow Builder can be triggered on Opportunity update (Record-Triggered Flow).
Flow queries related Opportunities on the same Account where Stage ≠ Closed Won/Lost.
Updates those records to Closed Lost in a single transaction.
Fully declarative, maintainable, and meets the cross-object update requirement.
Incorrect Option: B
Outbound Message sends data to an external endpoint but does not perform internal record updates.
It is used for integrations, not for updating child records in Salesforce.
Cannot query or mass-update opportunities.
Incorrect Option: C
Flow Orchestration manages multi-step, cross-user processes with wait steps and human tasks.
It is overkill and inappropriate for a simple synchronous update of sibling records.
Designed for business process orchestration (e.g., onboarding), not bulk field updates.
Incorrect Option: D
Quick Action creates or updates a single record from a related list or object.
Cannot query multiple records or perform conditional updates across a related set.
A Quick Action would only affect the current opportunity, not all open ones on the Account.
Reference:
Salesforce Help Article: Best Use Cases for Flow Builder – Use Record-Triggered Flows to perform cross-object updates, mass updates on related records, and complex business logic. Flow Orchestration, Outbound Messages, and Quick Actions serve different purposes and are not suited for this scenario.
Question 4Choose 1
Which action should a Platform Administrator configure to reverse a submitted approval request and unlock the associated record when setting up an approval process? 99
Correct answer:
B. Recall Actions
Explanation:
In Salesforce Approval Processes, the Recall action is specifically designed to reverse a submitted approval request and unlock the associated record. When a user with appropriate permissions recalls an approval request, the process is cancelled, the record is unlocked, and any locked fields become editable again.
Correct Option: B
Recall Actions are executed when a submitted approval request is recalled (cancelled) before final decision.
The recall action reverses the submission, unlocks the record, and can trigger specified field updates or email alerts.
This is the correct action type for reversing a submitted request and unlocking the record.
Available only when "Allow Recall" is enabled in the approval process.
Incorrect Option: A
Final Rejection Actions execute when an approval request is rejected, not recalled.
These occur at the end of the process, not as a reversal of a submitted request.
Does not unlock the record if it was locked upon submission.
Incorrect Option: C
Final Approval Actions execute when an approval request is approved, not recalled.
These actions finalize the approval, not reverse it.
The record remains locked if the approval process is configured to lock on approval.
Incorrect Option: D
Initial Submission Actions execute when the approval request is first submitted, not when it is recalled.
These actions lock the record and notify approvers.
They are the opposite of reversal.
Reference:
Salesforce Help Article: Recall Approval Requests – When you recall an approval request, any Recall Actions configured in the approval process are executed. These actions can unlock the record, update fields, and send notifications. Final Approval, Final Rejection, and Initial Submission actions serve different phases of the approval lifecycle.
Question 5Choose 1
A Platform Administrator needs to configure an approval process for the sales team when opportunities that meet particular conditions are closed. How should the administrator make sure the right records are included in the process?
Correct answer:
A. Add Specific Entry Criteria.
Explanation:
In Salesforce Approval Processes, Entry Criteria are the conditions that determine which records are eligible to enter the approval process when submitted. By adding specific entry criteria (e.g., Amount > $10,000 AND Stage = Closed Won), the administrator ensures only records meeting the sales team's conditions will trigger the approval workflow.
Correct Option: A
Specific Entry Criteria are configured in the approval process definition.
Records must meet all criteria to be submitted for approval.
Examples: Amount > 50,000, Region = "EMEA", Discount_Percentage < 30.
This is the standard, declarative way to filter records into an approval process.
Incorrect Option: B
Dynamic Forms control field visibility and layout on record pages, not approval process eligibility.
A button's visibility can be controlled by criteria, but that does not prevent non-eligible records from being submitted via other methods (e.g., API, list view).
Entry criteria inside the approval process are more secure and reliable.
Incorrect Option: C
A screen flow can guide users through submission, but it does not replace entry criteria inside the approval process itself.
Without entry criteria, any record submitted—even misrouted ones—would enter the approval process.
Entry criteria provide a system-level filter.
Incorrect Option: D
A validation rule prevents saving records that don't meet conditions, but it does not control which records enter an approval process.
Approval processes have their own entry criteria independent of validation rules.
Validation rules are for data quality, not approval eligibility.
Reference:
Salesforce Help Article: Define Approval Process Entry Criteria – Entry criteria determine which records are eligible for an approval process. Use specific criteria to filter records based on field values, ensuring only the right records enter the process when submitted.
That's the last free question in Automation
You've seen the free 25% of this topic (5 of 22 questions). Get complete access for every question, explanation and the timed exam simulator.
Our timed 2026 Salesforce Platform Administrator practice test mirrors the format, number of questions and time limit of the official exam.
The #1 challenge isn't just knowing the material, it's managing the clock. The simulation builds your speed and stamina, so you walk in knowing exactly what to expect.