Practice Free Plat-Admn-201 Exam Online Questions
Ursa Major Solar wants to see collaboration and updates across various Chatter groups, records, and announcements from the CEO in a single place.
What should a Platform Administrator configure to achieve this?
- A . Chatter Group
- B . Chatter Daily Digest
- C . Chatter Feed
- D . Chatter Stream
D
Explanation:
A Chatter Stream is a custom feed that users (or administrators) can create to consolidate updates from multiple sources. You can combine feeds from specific groups, individual people (like the CEO), and specific records into a single view. This allows users to stay organized and monitor diverse sets of information in one place without having to navigate between different groups or records. A Chatter Group (Option A) is for a specific set of members. A Daily Digest (Option B) is an email summary. A Chatter Feed (Option C) is a general term for the individual lists of updates but does not natively allow for the targeted "multi-source" consolidation that a Stream provides.
Marketing users at Cloud Kicks have been completing the Lead Source field inconsistently, with values like Web, Website, and Online. To ensure data quality, a Platform Administrator needs to standardize these records.
Which Flow should the administrator use to clean up these inconsistent Lead Source values?
- A . Segment triggered flow
- B . Record triggered flow
- C . Schedule-triggered flow
- D . Screen flow
C
Explanation:
When an administrator needs to perform a "cleanup" of existing data in bulk, a Schedule-triggered flow is the most efficient choice. This type of flow can be configured to run once (or on a recurring schedule) and process all Lead records that meet the "inconsistent" criteria (e.g., Lead Source equals ‘Website’ or ‘Online’)46. The flow can then automatically update those records to the standard "Web" value. A Record-triggered flow (Option B) only works on records as they are being created or updated, so it would not fix historical data unless every record was manually touched Screen flows (Option D) require manual user interaction for each record. 53Segment-triggered flows (Option A) are used in Data Cloud marketing conte54xts rather than standard core record cleanup.
Sales reps miss key fields when filling out an opportunity record through the sales process. Reps need to move forward in stages but are unable to enter a previous stage.
Which three options should a Platform Administrator use to address this need?
- A . Mark fields required on the page layout.
- B . Use Flow to mark fields required.
- C . Configure Opportunity Path.
- D . Use validation rules.
- E . Enable guided selling.
A, C, D
Explanation:
To ensure data integrity and guide sales reps through a structured process, a Platform Administrator should use a combination of tools. Opportunity Path (Option C) provides a visual representation of the stages and allows the admin to highlight "Key Fields" and "Guidance for Success" for each stage, making it clear what information is needed to progress. To enforce the entry of that data, Validation Rules (Option D) are used to prevent a user from moving to the next stage if specific fields are blank (e.g., AND(IsChanged(StageName), IsBlank(Discovery_Notes__c))). Additionally, marking fields as required on the Page Layout (Option A) ensures that the most fundamental data points are always captured. While Flow (Option B) can perform many tasks, it is not the primary way to mark fields as "required" in the UI. "Guided Selling" (Option E) is a specific term often associated with Salesforce CPQ rather than standard Opportunity management. Using Path, Validation Rules, and Page Layout requirements provides a robust framework for managing the sales lifecycle effectively.
Which Salesforce feature allows a Platform Administrator to automate3 the routing of records to specific users for review and decision-making based on predefined criteria?
- A . Assignment Rules
- B . Validation Rules
- C . Approval Process
- D . Schema Builder
C
Explanation:
An Approval Process is the dedicated Salesforce feature for managing workflows that require human "review and decision-making." Unlike Assignment Rules (Option A), which simply change the owner of a record, an Approval Process locks the record to prevent further changes and routes a formal request to an "Approver." This approver can then choose to Approve, Reject, or Reassign the request. The process can include multiple steps, entry criteria (e.g., "only if discount > 10%"), and specific automated actions that occur once the final decision is made. Validation Rules (Option B) are used to prevent saving bad data, not for routing. Schema Builder (Option D) is a visualization tool for the data model. Therefore, when a business process requires an official "sign-off" or "decision," the Approval Process engine is the correct architectural choice.
The call center manager at Ursa Major Solar wants to provide agents with a case dashboard that can be drilled down by case origin, status, and owner.
What should a Platform Administrator add to the dashboard to fulfill the request?
- A . Dashboard Filter
- B . Dashboard Widget
- C . Combination Chart
- D . Bucket Column
A
Explanation:
To provide a single dashboard that allows users to "drill down" or toggle between different data subsets, the administrator should add Dashboard Filters. A dashboard filter allows the manager or agent to select a value (e.g., "Origin = Phone" or "Status = New"), and all components on the dashboard will instantly refresh to show only the data matching that criteria. Salesforce allows up to three filters per dashboard, which perfectly accommodates the request for origin, status, and owner. While a Bucket Column (Option D) can group data within a report, it does not provide the interactive "drill down" capability on the dashboard itself. Widgets (Option B) are the components themselves, and Combination Charts (Option C) display multiple data sets in one visual but do not offer filtering functionality.
Universal Containers wants to ensure that cases are routed to the right people at the right time, but there is a growing support organization. The business wants to be able to move people around and adjust the work they get without having to request extra assistance or rely on the administrator teams.
Which tool allows the business to control its own assignment of work?
- A . Case Assignment Rules
- B . Email-to-Case
- C . Omni-Channel
- D . Lead Assignment Rules
C
Explanation:
Omni-Channel is a comprehensive service tool designed to route work items (like Cases, Leads, or custom objects) to the most available and qualified support agents in real-time. Unlike Case Assignment Rules, which are often static and require administrative intervention to update complex logic, Omni-Channel allows for more dynamic management through the use of Queues and Presence Statuses. By using Omni-Channel, a support manager or "Supervisor" can monitor agent workloads and adjust capacity or move people between service channels without needing to modify the underlying system configuration or involve the Platform Administrator. It supports various routing models, such as "Least Active" or "Most Available," ensuring that work is distributed fairly and efficiently. This flexibility is vital for growing organizations that need to scale their support operations quickly while maintaining high service levels. Furthermore, it provides the business with the autonomy to manage its workforce effectively, as managers can see who is logged in and what they are working on, allowing for immediate adjustments to handle spikes in case volume.
A Platform Administrator has been asked to change the data type of an auto number to a text field.
What should the administrator be aware of before changing the field?
- A . Existing field values will remain unchanged.
- B . Changing Auto Number field to Text is prevented.
- C . Existing field values will be deleted.
- D . Existing field values will be converted.
A 10
Explanation:
In Salesforce, when a Platform Administrator changes a field’s data type from Auto Number to Text, the operation is considered "safe" regarding data retention. The existing values that were automatically generated by the system (e.g., "INV-1001") will remain unchanged and stay within the field as static text strings12. However, once the change is saved, the system will no longer increment or automatically generate new numbers for future records; users will have to enter data manually. It is important to note that the reverse operation―changing a Text field to an Auto Number―is different, as it would require the administrator to decide whether to overwrite existing data or only number new records14.
Options B, C, and D are incorrect because Salesforce explicitly supports this specific conversion without deleting or fundamentally transforming the existing data into a different format other than plain text.
A Platform Administrator at Ursa Major Solar imported records into an object by mistake.
Which two tools should the administrator use to undo this import?
- A . Weekly Data Export
- B . Data Loader
- C . Data Import Wizard
- D . Mass Delete Records
B, D
Explanation:
To "undo" a mistaken import, the administrator must delete the incorrectly created records.
Two standard tools facilitate this:
Mass Delete Records (Option D): This is a browser-based tool in Setup that allows administrators to delete up to 250 records at a time (standard) or use criteria to identify and remove larger sets of records. It is the quickest way for smaller mistakes.
Data Loader (Option B): For large-scale errors, the administrator can use the Success file generated during the original import (which contains the new record IDs) and perform a "Delete" operation.
The Data Import Wizard (Option C) is for adding or updating data, but it does not have a "Delete" function. Weekly Data Export (Option A) is a backup tool and cannot be used to remove existing data from the system.
Northern Trail Outfitters wants emails received from customers to generate cases automatically.
How should a Platform Administrator ensure that the emails are sent to the correct queue?
- A . Create an escalation rule to send cases to the correct queue.
- B . Use a custom email service to set the owner of the case upon creation.
- C . Utilize a flow to identify the correct queue and assign the case.
- D . Configure Email-to-Case so emails are delivered to the correct queue.
D
Explanation:
The most efficient and standard way to automate case creation from inbound emails is by using Email-to-Case. When setting up Email-to-Case, the Platform Administrator configures "Routing Addresses". For each routing address (e.g., [email protected] or [email protected]), the administrator can specify a default owner or queue for the cases created via that specific address. This ensures that when a customer sends an email to the "Support" address, it is automatically routed to the Support Queue, and an email to the "Billing" address is routed to the Billing Queue. This configuration is handled directly within the Email-to-Case setup pages and does not require additional escalation rules (Option A) or complex custom flows (Option C) for the initial assignment. While a custom email service (Option B) is possible, it is a developer-centric approach that is generally unnecessary given the robust native capabilities of the standard Email-to-Case feature. This setup streamlines the intake process and ensures that customer issues are immediately visible to the correct service team34.
Cloud Kicks needs to change the owner of a case when it has been open for more than 7 days.
What should a Platform Administrator use to complete this requirement?
- A . Escalation Rules
- B . Auto Response Rules
- C . Assignment Rules
- D . Validation Rules
A 48
Explanation:
Escalation Rules are designed specifically to perform actions when a Case record has remained in a certain state (like "Open") for a specified period. In this scenario, the Platform Administrator would set an escalation rule entry with the age set to 168 hours (7 days). When this time threshold is reached, the rule can automatically reassign the case to a new owner or a management queue51. Assignment Rules (Option C) are only triggered upon the initial creation of a record or when manually triggered by a user, and they do not have a built-in "timer" capability to fire days later52. Auto-Response Rules (Option B) are only for sending automated emails to customers, not for internal ownership changes53. Validation Rules (Option D) are used to prevent data entry errors and cannot change record ownership54.
