Practice Free Plat-Admn-201 Exam Online Questions
Question #31
A Platform Administrator is building an agent to nurture leads.
How does Agentforce SDR help?
- A . Generate a dynamic call script and talking points for the human sales reps to use.
- B . Autonomously negotiate pricing with the lead and close the final deal.
- C . Analyze the performance of human sales reps and provide coaching tips.
- D . Answer the lead’s questions with responses that are grounded in company data.
Correct Answer: D
D
Explanation:
Agentforce SDR (Sales Development Representative) is an AI agent designed to autonomously engage with prospects to nurture leads and accelerate the sales pipeline. A core functionality of this agent is its ability to interact with potential customers by answering their specific questions about products or services. Crucially, these responses are grounded in company data, meaning the agent retrieves relevant information from the Salesforce Knowledge base, product catalogs, or other internal resources to provide accurate, brand-aligned answers. This ensures that the agent provides high-quality, trustworthy information without the "hallucinations" common in non-grounded AI. While the agent helps in lead qualification and nurturing, its primary value in an ecommerce or sales support context is providing immediate, context-aware assistance. It is not intended to replace humans in complex price negotiations (Option B) or serve purely as a coaching tool (Option C), but rather to act as a front-line digital worker that scales the sales team’s reach by handling information-seeking queries autonomously.
D
Explanation:
Agentforce SDR (Sales Development Representative) is an AI agent designed to autonomously engage with prospects to nurture leads and accelerate the sales pipeline. A core functionality of this agent is its ability to interact with potential customers by answering their specific questions about products or services. Crucially, these responses are grounded in company data, meaning the agent retrieves relevant information from the Salesforce Knowledge base, product catalogs, or other internal resources to provide accurate, brand-aligned answers. This ensures that the agent provides high-quality, trustworthy information without the "hallucinations" common in non-grounded AI. While the agent helps in lead qualification and nurturing, its primary value in an ecommerce or sales support context is providing immediate, context-aware assistance. It is not intended to replace humans in complex price negotiations (Option B) or serve purely as a coaching tool (Option C), but rather to act as a front-line digital worker that scales the sales team’s reach by handling information-seeking queries autonomously.
Question #32
A Platform Administrator needs to create a new prompt template to automatically summarize customer cases for a sales team. The administrator wants to dynamically populate the response with data from the case record.
What should the administrator use to display real Salesforce data in an agent response from a prompt template?
- A . Flow
- B . Picklists
- C . Agent Instructions
- D . Merge Fields
Correct Answer: D
D
Explanation:
When building prompt templates within the Prompt Builder, the most direct way to inject specific record data into the AI’s instructions is through Merge Fields. Much like an email template or a mail merge, merge fields allow the administrator to reference specific fields from the object in context― in this case, the Case object.
For example, an administrator might use {!$Input:Case.Subject} or {!$Input:Case.Description} within the prompt template. When the agent runs, it replaces these placeholders with the actual data from the specific case record being viewed. This ensures that the AI has the "grounding" information it needs to generate an accurate and relevant summary. While Flows (Option A) can be used for more complex data retrieval, Merge Fields are the standard, low-code tool for simple record-to-prompt data population. Agent Instructions (Option C) provide the "how-to" logic for the AI but do not themselves represent the dynamic data points from the Salesforce database.
D
Explanation:
When building prompt templates within the Prompt Builder, the most direct way to inject specific record data into the AI’s instructions is through Merge Fields. Much like an email template or a mail merge, merge fields allow the administrator to reference specific fields from the object in context― in this case, the Case object.
For example, an administrator might use {!$Input:Case.Subject} or {!$Input:Case.Description} within the prompt template. When the agent runs, it replaces these placeholders with the actual data from the specific case record being viewed. This ensures that the AI has the "grounding" information it needs to generate an accurate and relevant summary. While Flows (Option A) can be used for more complex data retrieval, Merge Fields are the standard, low-code tool for simple record-to-prompt data population. Agent Instructions (Option C) provide the "how-to" logic for the AI but do not themselves represent the dynamic data points from the Salesforce database.
Question #33
Northern Trail Outfitters has the Case object set to private. The support manager raised a concern that reps have a broader view of data than expected and can see all cases on their group’s dashboards.
What is causing reps to have inappropriate access to data on dashboards?
- A . Dashboard Filters
- B . Public Dashboards
- C . Dashboard’s running user
- D . Dashboard Subscriptions
Correct Answer: C
C
Explanation:
In Salesforce, a dashboard’s running user determines which data is displayed to anyone viewing the dashboard. If a dashboard is configured with a "Static" running user (e.g., a Support Manager who has "View All" permissions), every user who views that dashboard will see the manager’s level of data, regardless of their own personal sharing permissions. This bypasses the Organization-Wide Default (OWD) of "Private" for the Case object. When the support manager observes that reps can see all cases on a group dashboard, it is almost certainly because the dashboard is "running" as a user with high-level access. To correct this and ensure users only see data they are entitled to, the Platform Administrator should convert it into a Dynamic Dashboard. A dynamic dashboard is set to "Run as the logged-in user," meaning the data reflected in the components will automatically filter based on the individual viewer’s specific sharing rules and record ownership. This ensures that the dashboard remains a useful tool for the team while strictly adhering to the company’s data privacy and security requirements.
C
Explanation:
In Salesforce, a dashboard’s running user determines which data is displayed to anyone viewing the dashboard. If a dashboard is configured with a "Static" running user (e.g., a Support Manager who has "View All" permissions), every user who views that dashboard will see the manager’s level of data, regardless of their own personal sharing permissions. This bypasses the Organization-Wide Default (OWD) of "Private" for the Case object. When the support manager observes that reps can see all cases on a group dashboard, it is almost certainly because the dashboard is "running" as a user with high-level access. To correct this and ensure users only see data they are entitled to, the Platform Administrator should convert it into a Dynamic Dashboard. A dynamic dashboard is set to "Run as the logged-in user," meaning the data reflected in the components will automatically filter based on the individual viewer’s specific sharing rules and record ownership. This ensures that the dashboard remains a useful tool for the team while strictly adhering to the company’s data privacy and security requirements.
Question #34
Cloud Kicks uses the standard Account Type field to indicate different account tiers. Users find this confusing, so management has asked that the field be changed to read "Tier" on the page layouts.
How should a Platform Administrator implement this change?
- A . Edit the Type field and change the name.
- B . Use Rename Tabs and Labels.
- C . Build a custom field called Tier and delete Type.
- D . Create a global picklist value set.
Correct Answer: B
B
Explanation:
To change the display name of a standard field (like "Account Type") globally across the entire organization, the correct tool is Rename Tabs and Labels in the Setup menu. This tool allows an administrator to modify the singular and plural labels for standard objects and the field labels for their standard fields. By renaming "Type" to "Tier," the change will be reflected on page layouts, in report column headers, and in list views. This is the preferred method because it preserves the underlying data and logic associated with the standard field.
Option A is incorrect because standard field names cannot be edited in the "Fields and Relationships" menu.
Option C is a destructive and complex process that would require data migration and could break existing reports or integrations.
Option D does not address the label of the field itself.
B
Explanation:
To change the display name of a standard field (like "Account Type") globally across the entire organization, the correct tool is Rename Tabs and Labels in the Setup menu. This tool allows an administrator to modify the singular and plural labels for standard objects and the field labels for their standard fields. By renaming "Type" to "Tier," the change will be reflected on page layouts, in report column headers, and in list views. This is the preferred method because it preserves the underlying data and logic associated with the standard field.
Option A is incorrect because standard field names cannot be edited in the "Fields and Relationships" menu.
Option C is a destructive and complex process that would require data migration and could break existing reports or integrations.
Option D does not address the label of the field itself.
Question #35
Northern Trail Outfitters uses a custom Invoice object to collect customer payment information from an external billing system. The Billing System field needs to be filled in on every Invoice record.
How should a Platform Administrator ensure this requirement?
- A . Create a flow to update the field.
- B . Require the field on the record type.
- C . Define an approval process for the field.
- D . Make the field universally required.
Correct Answer: D
D
Explanation:
To ensure that a field is populated on every single record, regardless of how it is created (manually, via API, or through an integration), the best method is to make the field universally required at the field definition level. When a field is marked as "Required" in the Object Manager, the Salesforce database will reject any attempt to save a record if that field is empty. While requiring a field on a Page Layout or Record Type (Option B) provides a good user experience for manual entry, it does not prevent records from being created without that data via the API or background processes25. Using a flow (Option A) to update the field is reactive rather than preventative26. Universal requirement is the most robust way to maintain data integrity for critical fields like "Billing System" that are essential for reporting and external system alignment.
D
Explanation:
To ensure that a field is populated on every single record, regardless of how it is created (manually, via API, or through an integration), the best method is to make the field universally required at the field definition level. When a field is marked as "Required" in the Object Manager, the Salesforce database will reject any attempt to save a record if that field is empty. While requiring a field on a Page Layout or Record Type (Option B) provides a good user experience for manual entry, it does not prevent records from being created without that data via the API or background processes25. Using a flow (Option A) to update the field is reactive rather than preventative26. Universal requirement is the most robust way to maintain data integrity for critical fields like "Billing System" that are essential for reporting and external system alignment.
Question #36
In an approval process, what happens when a queue is selected as the approver?
- A . The queue requires unanimous approval from all of its members before the record is approved.
- B . Any member of the queue can approve or reject the record and the queue is treated as a single entity.
- C . Only the queue owner is notified about the approval request, not its members.
- D . The queue can only be used for objects that do not support individual user approvals.
Correct Answer: B
B
Explanation:
Salesforce allows Queues to be designated as assigned approvers in an approval process. When a record is submitted for approval and routed to a queue, an email notification is sent to all queue members (depending on queue settings). The core behavior is that any member of the queue can "claim" the request and either approve or reject it. Once one member takes action, the step is considered complete, and the queue is treated as a single decision-making entity. Unanimous approval (Option A) is a specific setting for multiple individual assigned approvers, but it does not apply to queues in this way.
Option C is incorrect because the purpose of a queue is to notify all members to ensure a timely response. Queues are supported for most standard and all custom objects (negating Option D).
B
Explanation:
Salesforce allows Queues to be designated as assigned approvers in an approval process. When a record is submitted for approval and routed to a queue, an email notification is sent to all queue members (depending on queue settings). The core behavior is that any member of the queue can "claim" the request and either approve or reject it. Once one member takes action, the step is considered complete, and the queue is treated as a single decision-making entity. Unanimous approval (Option A) is a specific setting for multiple individual assigned approvers, but it does not apply to queues in this way.
Option C is incorrect because the purpose of a queue is to notify all members to ensure a timely response. Queues are supported for most standard and all custom objects (negating Option D).
Question #37
A sales team is having difficulty understanding which stage their opportunity is in and what the company sales process requires of them in that stage.
Which feature should a Platform Administrator implement to help the sales team quickly determine where they are in the sales process and what is required of them?
- A . Reports & Dashboards
- B . Opportunity Sales Path
- C . Big Deal Alerts
- D . List Views
Correct Answer: B
B
Explanation:
The Opportunity Sales Path (or simply Path) is a visual representation of the stages in a sales process. It is the best tool for this requirement because it not only shows the current stage prominently at the top of the record but also allows administrators to define Key Fields and Guidance for Success for every stage. This guidance can include specific steps, tips, and links to company resources that explain exactly what a rep needs to do to move the deal to the next phase. Reports (Option A), List Views (Option D), and Big Deal Alerts (Option C) provide data and notifications but do not offer the contextual, stage-by-stage guidance that the Path provides.
B
Explanation:
The Opportunity Sales Path (or simply Path) is a visual representation of the stages in a sales process. It is the best tool for this requirement because it not only shows the current stage prominently at the top of the record but also allows administrators to define Key Fields and Guidance for Success for every stage. This guidance can include specific steps, tips, and links to company resources that explain exactly what a rep needs to do to move the deal to the next phase. Reports (Option A), List Views (Option D), and Big Deal Alerts (Option C) provide data and notifications but do not offer the contextual, stage-by-stage guidance that the Path provides.
Question #38
Which two actions should a Platform Administrator perform with Case escalation rules?
- A . Send email notifications.
- B . Change the Case Priority.
- C . Reopen the Case.
- D . Reassign the Case.
Correct Answer: A, D
A, D
Explanation:
Case Escalation Rules are used in Service Cloud to ensure that cases are handled within specific timeframes, helping organizations meet their Service Level Agreements (SLAs)23232323232323. When a case meets the criteria defined in an escalation rule and remains unresolved for a specified period, the system can perform two primary automated actions:
Reassign the Case: The rule can automatically transfer ownership of the case to another user or a specific queue (e.g., a "Tier 2 Support" queue) to ensure it gets specialized attention242424242424242424.
Send Email Notifications: The system can send alerts to the new owner, the current owner, or up to five additional email addresses to notify management that a case has escalated.
While administrators often use other tools like Flow Builder to change the "Case Priority" (Option B) or "Reopen" a case (Option C), these are not standard features within the Escalation Rule interface26. Escalation rules focus specifically on the routing and notification aspects of case management to prevent tickets from "sitting" too long without a response.
A, D
Explanation:
Case Escalation Rules are used in Service Cloud to ensure that cases are handled within specific timeframes, helping organizations meet their Service Level Agreements (SLAs)23232323232323. When a case meets the criteria defined in an escalation rule and remains unresolved for a specified period, the system can perform two primary automated actions:
Reassign the Case: The rule can automatically transfer ownership of the case to another user or a specific queue (e.g., a "Tier 2 Support" queue) to ensure it gets specialized attention242424242424242424.
Send Email Notifications: The system can send alerts to the new owner, the current owner, or up to five additional email addresses to notify management that a case has escalated.
While administrators often use other tools like Flow Builder to change the "Case Priority" (Option B) or "Reopen" a case (Option C), these are not standard features within the Escalation Rule interface26. Escalation rules focus specifically on the routing and notification aspects of case management to prevent tickets from "sitting" too long without a response.
Question #39
Senior leadership wants to be notified of any opportunities over $250,000 with more than a 75% probability of closing.
Which feature should a Platform Administrator set up to facilitate this?
- A . Guidance for Success
- B . Big Deal Alerts
- C . Reports and Dashboards
- D . Similar Opportunities
Correct Answer: B
B
Explanation:
Big Deal Alerts are a specialized, "out-of-the-box" notification feature specifically for the Opportunity object. This tool allows a Platform Administrator to define a threshold based on "Amount" and "Probability." When an opportunity is created or updated and meets these thresholds (in this case, >$250k and >75%), Salesforce automatically sends an email notification to a specified user or a list of stakeholders. This is the most efficient way to meet the requirement because it is a native feature designed exactly for high-value deal visibility. While Reports and Dashboards (Option C) can display this data, they are "pull" mechanisms that require leadership to actively check them, whereas a Big Deal Alert is a "push" mechanism that ensures immediate awareness. Guidance for Success (Option A) provides tips within a sales path, and Similar Opportunities (Option D) helps reps find related deals, but neither is designed for automated leadership notifications.
B
Explanation:
Big Deal Alerts are a specialized, "out-of-the-box" notification feature specifically for the Opportunity object. This tool allows a Platform Administrator to define a threshold based on "Amount" and "Probability." When an opportunity is created or updated and meets these thresholds (in this case, >$250k and >75%), Salesforce automatically sends an email notification to a specified user or a list of stakeholders. This is the most efficient way to meet the requirement because it is a native feature designed exactly for high-value deal visibility. While Reports and Dashboards (Option C) can display this data, they are "pull" mechanisms that require leadership to actively check them, whereas a Big Deal Alert is a "push" mechanism that ensures immediate awareness. Guidance for Success (Option A) provides tips within a sales path, and Similar Opportunities (Option D) helps reps find related deals, but neither is designed for automated leadership notifications.
Question #40
The sales director at Cloud Kicks wants to be able to predict upcoming revenue in the next several fiscal quarters so they can set goals and benchmark how reps are performing.
Which two features should a Platform Administrator configure?
- A . Sales Quotes
- B . Forecasting
- C . Opportunity List View
- D . Opportunity Stages
Correct Answer: B, D
B, D
Explanation:
To "predict upcoming revenue" and "benchmark performance," Salesforce provides the Collaborative Forecasting feature.
Forecasting (Option B): This tool allows managers to see their pipeline summarized by time period (quarters) and category. It provides a real-time view of what the team expects to close.
Opportunity Stages (Option D): Forecasting relies directly on the Opportunity Stage. Each stage is mapped to a "Forecast Category" (e.g., Pipeline, Best Case, Commit, Closed). By accurately defining these stages and their associated probabilities, the Platform Administrator ensures that the forecast reflects a realistic revenue prediction.
Sales Quotes (Option A) are for generating customer-facing documents. List Views (Option C) are for managing individual records but do not provide the multi-quarter aggregation and benchmarking capabilities required by the sales director.
B, D
Explanation:
To "predict upcoming revenue" and "benchmark performance," Salesforce provides the Collaborative Forecasting feature.
Forecasting (Option B): This tool allows managers to see their pipeline summarized by time period (quarters) and category. It provides a real-time view of what the team expects to close.
Opportunity Stages (Option D): Forecasting relies directly on the Opportunity Stage. Each stage is mapped to a "Forecast Category" (e.g., Pipeline, Best Case, Commit, Closed). By accurately defining these stages and their associated probabilities, the Platform Administrator ensures that the forecast reflects a realistic revenue prediction.
Sales Quotes (Option A) are for generating customer-facing documents. List Views (Option C) are for managing individual records but do not provide the multi-quarter aggregation and benchmarking capabilities required by the sales director.