Practice Free Plat-Admn-201 Exam Online Questions
Question #1
Cloud Kicks wants to ensure that every client has support based on the level of service that has been agreed on in the sales cycle. There are tiers to this support model, Gold, Silver, and Bronze.
What should a Platform Administrator create to ensure that this is part of every client’s account once they become a client?
- A . A flow to assign Entitlements
- B . Routing Configuration for each client
- C . Email to Case for each service level
- D . Case Assignment Rules for each client
Correct Answer: A
A
Explanation:
To manage different levels of support service (Gold, Silver, Bronze), Salesforce uses the Entitlement Management feature. An "Entitlement" defines the specific type of support a customer is eligible for. To "ensure that this is part of every client’s account" automatically, a Platform Administrator should use Flow Builder. A record-triggered flow can be set to run whenever an Account is updated to "Customer" status or when a specific "Service Level" field is populated. The flow can then automatically create or link an Entitlement record to that Account. This ensures that when a new case is opened, the support agent immediately sees the SLA (Service Level Agreement) associated with that customer. Routing Configurations (Option B) and Assignment Rules (Option D) handle who gets the case, but they do not define the level of service. Email-to-Case (Option C) is an intake method, not a service-level tracking tool.
A
Explanation:
To manage different levels of support service (Gold, Silver, Bronze), Salesforce uses the Entitlement Management feature. An "Entitlement" defines the specific type of support a customer is eligible for. To "ensure that this is part of every client’s account" automatically, a Platform Administrator should use Flow Builder. A record-triggered flow can be set to run whenever an Account is updated to "Customer" status or when a specific "Service Level" field is populated. The flow can then automatically create or link an Entitlement record to that Account. This ensures that when a new case is opened, the support agent immediately sees the SLA (Service Level Agreement) associated with that customer. Routing Configurations (Option B) and Assignment Rules (Option D) handle who gets the case, but they do not define the level of service. Email-to-Case (Option C) is an intake method, not a service-level tracking tool.
Question #2
A Platform Administrator assigned a custom profile based on the Minimum Access named Salesforce profile to a group of new users and assigned them several existing permission sets. However, when the users log in, they do not see the Lightning interface.
Which action should the administrator take to give the users access to the Lightning interface?
- A . Enable the Enhanced Interface for User Access Policies.
- B . Add Lightning component to a layout.
- C . Create a page in Lightning App Builder with the org as default.
- D . Assign a permission to enable Lightning Experience User.
Correct Answer: D
D
Explanation:
The "Minimum Access – Salesforce" profile is a very restrictive standard profile designed to provide no access by default, adhering to the principle of least privilege. One of the specific permissions that is not included in this profile is the Lightning Experience User permission. Without this system permission, users will be defaulted to the Salesforce Classic interface (or potentially blocked from any UI if no other access is granted). To resolve this, the Platform Administrator should either edit the custom profile or, preferably, create a Permission Set that includes the "Lightning Experience User" checkbox and assign it to the affected users. This "unlocks" the modern Lightning interface for them.
Options B and C relate to the design of specific pages, but they are irrelevant if the user isn’t even allowed to enter the Lightning environment.
Option A refers to a different feature set entirely and does not address basic UI access.
D
Explanation:
The "Minimum Access – Salesforce" profile is a very restrictive standard profile designed to provide no access by default, adhering to the principle of least privilege. One of the specific permissions that is not included in this profile is the Lightning Experience User permission. Without this system permission, users will be defaulted to the Salesforce Classic interface (or potentially blocked from any UI if no other access is granted). To resolve this, the Platform Administrator should either edit the custom profile or, preferably, create a Permission Set that includes the "Lightning Experience User" checkbox and assign it to the affected users. This "unlocks" the modern Lightning interface for them.
Options B and C relate to the design of specific pages, but they are irrelevant if the user isn’t even allowed to enter the Lightning environment.
Option A refers to a different feature set entirely and does not address basic UI access.
Question #3
What is an Agentforce use case in a sales organization?
- A . Generating cold calls
- B . Automating all marketing content
- C . Providing basic web bot chats
- D . Automating Lead Qualification
Correct Answer: D
D
Explanation:
Agentforce is designed to handle sophisticated, multi-step business processes that traditionally require human intervention. In a sales organization, a primary use case is Automating Lead Qualification. Unlike basic web bots (Option C) that follow a rigid, pre-defined script, an Agentforce agent can engage in natural language conversations with prospects. It can ask relevant discovery questions, handle objections, and determine if a lead meets the company’s "Qualified" criteria based on the information provided. Once qualified, the agent can autonomously update the Salesforce record or even book a meeting for a human sales representative. While AI can assist with content, "automating all marketing content" (Option B) is overly broad and typically handled by specialized marketing tools. Generating cold calls (Option A) involves voice technology and legal complexities that are not the core focus of the Agentforce platform’s digital agent capabilities. Lead qualification represents a high-value, repeatable process that perfectly leverages the agent’s ability to reason and interact with Salesforce data.
D
Explanation:
Agentforce is designed to handle sophisticated, multi-step business processes that traditionally require human intervention. In a sales organization, a primary use case is Automating Lead Qualification. Unlike basic web bots (Option C) that follow a rigid, pre-defined script, an Agentforce agent can engage in natural language conversations with prospects. It can ask relevant discovery questions, handle objections, and determine if a lead meets the company’s "Qualified" criteria based on the information provided. Once qualified, the agent can autonomously update the Salesforce record or even book a meeting for a human sales representative. While AI can assist with content, "automating all marketing content" (Option B) is overly broad and typically handled by specialized marketing tools. Generating cold calls (Option A) involves voice technology and legal complexities that are not the core focus of the Agentforce platform’s digital agent capabilities. Lead qualification represents a high-value, repeatable process that perfectly leverages the agent’s ability to reason and interact with Salesforce data.
Question #4
DreamHouse Realty (DHR) wants a templated process with a mortgage calculator that generates leads for loans. DHR needs to complete the project within 30 days and has maxed out its budget for the year.
Which AppExchange item should help a Platform Administrator meet the request?4
- A . Bolt Solutions5
- B . Lightning Community6
- C . Lightning Data7
- D . Flow Solutions8
Correct Answer: D9
D9
Explanation:
10
When a business needs a specific11, complex functional tool (like a mortgage calculator) on a tight timeline and zero budget, Flow Solutions on the AppExchange are the best resource. Many Flow Solutions are provided for free by Salesforce Labs or other partners. These are pre-built, "installable" flows that an administrator can download and customize. Because they are built using standard Flow Builder logic, they can be easily integrated into a website or Experience Cloud site to capture user
input and generate Lead records automatically. Bolt Solutions (Option A) are full industry templates that often require more setup and licensing. Lightning Data (Option C) is for data enrichment, not functional calculators. Flow Solutions empower administrators to deliver complex automation and specialized UI components quickly and cost-effectively.
D9
Explanation:
10
When a business needs a specific11, complex functional tool (like a mortgage calculator) on a tight timeline and zero budget, Flow Solutions on the AppExchange are the best resource. Many Flow Solutions are provided for free by Salesforce Labs or other partners. These are pre-built, "installable" flows that an administrator can download and customize. Because they are built using standard Flow Builder logic, they can be easily integrated into a website or Experience Cloud site to capture user
input and generate Lead records automatically. Bolt Solutions (Option A) are full industry templates that often require more setup and licensing. Lightning Data (Option C) is for data enrichment, not functional calculators. Flow Solutions empower administrators to deliver complex automation and specialized UI components quickly and cost-effectively.
Question #5
The VP of sales at AW Computing would like sales reps to check in with their top account every Monday. The VP would like a dashboard component to show the status of the check-ins.
What should a Platform Administrator configure to remind the reps to contact their top account?
- A . Create a time-based workflow task.
- B . Enable the creation of recurring tasks.
- C . Add the email action to the page layout.
- D . Use a process email alert on the account.
Correct Answer: B
B
Explanation:
To ensure a consistent, weekly "check-in" occurs, the Platform Administrator should enable the creation of recurring tasks. This feature allows a sales rep to create a single task (e.g., "Monday Check-in") and set a recurring frequency of "Weekly" on "Mondays." Salesforce then automatically generates the next task in the series once the current one is completed. This is the most effective way to provide reps with a constant reminder in their task list. Additionally, because these are standard Task records, the administrator can easily build a report and a dashboard component to track the completion status of these check-ins for the VP. Time-based workflow (Option A) is typically for one-off alerts based on a date field, not for a permanent weekly habit. Email actions (Option C) and alerts (Option D) notify users but do not create the trackable task record required for the dashboard component.
B
Explanation:
To ensure a consistent, weekly "check-in" occurs, the Platform Administrator should enable the creation of recurring tasks. This feature allows a sales rep to create a single task (e.g., "Monday Check-in") and set a recurring frequency of "Weekly" on "Mondays." Salesforce then automatically generates the next task in the series once the current one is completed. This is the most effective way to provide reps with a constant reminder in their task list. Additionally, because these are standard Task records, the administrator can easily build a report and a dashboard component to track the completion status of these check-ins for the VP. Time-based workflow (Option A) is typically for one-off alerts based on a date field, not for a permanent weekly habit. Email actions (Option C) and alerts (Option D) notify users but do not create the trackable task record required for the dashboard component.
Question #6
A Platform Administrator at Cloud Kicks has a flow in production that is supposed to create new records. However, no new records are being created.
What is causing the issue?
- A . The flow is inactive.
- B . The flow URL is deactivated.
- C . The flow is Read Only.
- D . The flow trigger is missing.
Correct Answer: A
A
Explanation:
In Salesforce, a flow must be Active for it to execute in a production environment. When an administrator builds or updates a flow, it is saved as a new version. Even if the logic is perfect and passes all debug tests, the flow will not run for end-users unless the administrator explicitly clicks the "Activate" button. If a flow is intended to create records but nothing is happening, the first troubleshooting step is always to verify the status in the Flow Builder or the Flows list in Setup. A flow version that is simply "Saved" but not "Active" will remain dormant.
Option D is unlikely because the Flow Builder usually prevents saving a record-triggered flow without a trigger defined.
Option C ("Read Only") is not a state that would prevent a flow from running.
Option B ("Flow URL") only applies to specific types of screen flows launched via custom links, whereas the question implies a general failure of the automation to execute.
A
Explanation:
In Salesforce, a flow must be Active for it to execute in a production environment. When an administrator builds or updates a flow, it is saved as a new version. Even if the logic is perfect and passes all debug tests, the flow will not run for end-users unless the administrator explicitly clicks the "Activate" button. If a flow is intended to create records but nothing is happening, the first troubleshooting step is always to verify the status in the Flow Builder or the Flows list in Setup. A flow version that is simply "Saved" but not "Active" will remain dormant.
Option D is unlikely because the Flow Builder usually prevents saving a record-triggered flow without a trigger defined.
Option C ("Read Only") is not a state that would prevent a flow from running.
Option B ("Flow URL") only applies to specific types of screen flows launched via custom links, whereas the question implies a general failure of the automation to execute.
Question #7
A Platform Administrator at Universal Containers is asked to restrict login access for users to specific hours and specific IP addresses to help minimize the risk of bad actors getting into the org.
Which setting should the administrator update to accomplish this?
- A . Company Settings
- B . The user’s role
- C . The user’s profile
- D . Custom permission sets
Correct Answer: C
C
Explanation:
In Salesforce, security restrictions like Login Hours and Login IP Ranges are managed at the Profile level. When these are configured on a profile, they are strictly enforced; if a user attempts to log in outside of the allowed hours or from an unauthorized IP address, the system will deny access entirely. This is one of the most robust ways to secure an organization against unauthorized access. Company Settings (Option A) can set "Trusted IP Ranges" for the whole org, but these only bypass multi-factor authentication; they do not restrict login. Roles (Option B) control record visibility, not system access. While Permission Sets (Option D) can grant many permissions, Login Hours and IP Ranges remain a core profile-level security setting.
C
Explanation:
In Salesforce, security restrictions like Login Hours and Login IP Ranges are managed at the Profile level. When these are configured on a profile, they are strictly enforced; if a user attempts to log in outside of the allowed hours or from an unauthorized IP address, the system will deny access entirely. This is one of the most robust ways to secure an organization against unauthorized access. Company Settings (Option A) can set "Trusted IP Ranges" for the whole org, but these only bypass multi-factor authentication; they do not restrict login. Roles (Option B) control record visibility, not system access. While Permission Sets (Option D) can grant many permissions, Login Hours and IP Ranges remain a core profile-level security setting.
Question #8
A Platform Administrator wants to limit the kinds of reports their users can create.
Which tool should the administrator use?
- A . Hide Report Types
- B . Report Folder Sharing
- C . Standard Report Types
- D . Joined Report
Correct Answer: A
A
Explanation:
When users click the "New Report" button, they are presented with a list of Report Types, which act as templates determining which objects and fields are available for the report. Often, an org has many standard report types that are irrelevant or confusing to the average user. To "limit the kinds of reports" and simplify the user experience, a Platform Administrator can use the Select Report Types to Hide feature in the Report and Dashboard Settings. By hiding unnecessary or redundant report types, the admin ensures that users only see the specific templates that align with company reporting standards. This reduces the risk of users creating inaccurate reports using the wrong data models. Report Folder Sharing (Option B) controls who can view or edit existing reports, but it does not restrict the creation of new ones from specific templates. While creating Custom Report Types is a way to define what data is available, the specific act of "limiting" the visible list is handled by the "Hide" functionality.
A
Explanation:
When users click the "New Report" button, they are presented with a list of Report Types, which act as templates determining which objects and fields are available for the report. Often, an org has many standard report types that are irrelevant or confusing to the average user. To "limit the kinds of reports" and simplify the user experience, a Platform Administrator can use the Select Report Types to Hide feature in the Report and Dashboard Settings. By hiding unnecessary or redundant report types, the admin ensures that users only see the specific templates that align with company reporting standards. This reduces the risk of users creating inaccurate reports using the wrong data models. Report Folder Sharing (Option B) controls who can view or edit existing reports, but it does not restrict the creation of new ones from specific templates. While creating Custom Report Types is a way to define what data is available, the specific act of "limiting" the visible list is handled by the "Hide" functionality.
Question #9
A Platform Administrator at Cloud Kicks has set up a junior administrator as a delegated administrator in Salesforce.
What should the Platform Administrator consider regarding delegated administrators?
- A . Delegated administrators can unlock users but cannot reset passwords.
- B . Delegated administrators can update field-level security on standard objects.
- C . Delegated administrators cannot modify permission sets.
- D . Delegated administrators cannot assign users to profiles.
Correct Answer: C
C
Explanation:
Delegated Administration is a powerful feature that allows a System Administrator to pass off specific administrative tasks to non-admin users without granting them the full "Modify All Data" permission. However, there are strict security boundaries to what a delegated admin can do. One of the most critical limitations is that delegated administrators cannot modify permission sets. They are primarily intended to manage users within specific roles, reset passwords, and manage specific custom objects. While they can assign users to certain profiles that have been explicitly allowed in the Delegated Administration group configuration, they are not permitted to manage the broader security architecture of the org, such as Permission Sets or Field-Level Security (Option B). This ensures that while junior staff can handle day-to-day user maintenance (like unlocking users, contrary to Option A), they cannot inadvertently elevate their own permissions or those of others through permission set manipulation.
C
Explanation:
Delegated Administration is a powerful feature that allows a System Administrator to pass off specific administrative tasks to non-admin users without granting them the full "Modify All Data" permission. However, there are strict security boundaries to what a delegated admin can do. One of the most critical limitations is that delegated administrators cannot modify permission sets. They are primarily intended to manage users within specific roles, reset passwords, and manage specific custom objects. While they can assign users to certain profiles that have been explicitly allowed in the Delegated Administration group configuration, they are not permitted to manage the broader security architecture of the org, such as Permission Sets or Field-Level Security (Option B). This ensures that while junior staff can handle day-to-day user maintenance (like unlocking users, contrary to Option A), they cannot inadvertently elevate their own permissions or those of others through permission set manipulation.
Question #10
A sales rep at Ursa Major Solar has launched a series of networking events. They are hosting one event per month and want to be able to report on Campaign ROI by month and series.
How should a Platform Administrator set up the Campaign to simplify reporting?
- A . Create individual Campaigns that all have the same name.
- B . Configure Campaign Member Statuses to record which event Members attended.
- C . Use Campaign Hierarchy where the monthly events roll up to a parent Campaign.
- D . Add different record types for the monthly event types.
Correct Answer: C
C
Explanation:
To organize related marketing initiatives and simplify reporting, Salesforce utilizes Campaign Hierarchies. A hierarchy allows an administrator to link multiple campaigns together using the "Parent Campaign" field. In this scenario, the admin should create a "Parent" campaign to represent the entire networking series and then create individual "Child" campaigns for each monthly event. This structure provides two major benefits: it allows the sales rep to see the specific performance (ROI, members, responses) of a single monthly event, and it uses "Hierarchy Total" fields to automatically roll up all those metrics to the parent level. This provides a holistic view of the entire series’ success without requiring complex manual calculations. Using the same name for campaigns (Option A) leads to data confusion, and while member statuses (Option B) are useful, they do not provide the structural "series vs. month" reporting required here. Campaign Hierarchy is the standard architectural approach for multi-touch or recurring marketing efforts.
C
Explanation:
To organize related marketing initiatives and simplify reporting, Salesforce utilizes Campaign Hierarchies. A hierarchy allows an administrator to link multiple campaigns together using the "Parent Campaign" field. In this scenario, the admin should create a "Parent" campaign to represent the entire networking series and then create individual "Child" campaigns for each monthly event. This structure provides two major benefits: it allows the sales rep to see the specific performance (ROI, members, responses) of a single monthly event, and it uses "Hierarchy Total" fields to automatically roll up all those metrics to the parent level. This provides a holistic view of the entire series’ success without requiring complex manual calculations. Using the same name for campaigns (Option A) leads to data confusion, and while member statuses (Option B) are useful, they do not provide the structural "series vs. month" reporting required here. Campaign Hierarchy is the standard architectural approach for multi-touch or recurring marketing efforts.