Try Before You Buy

Download a free sample of any of our exam questions and answers

  • 24/7 customer support, Secure shopping site
  • Free One year updates to match real exam scenarios
  • If you failed your exam after buying our products we will refund the full amount back to you.

Latest [Jul 02, 2026] Plat-Admn-201 Exam Questions – Valid Plat-Admn-201 Dumps Pdf [Q51-Q71]

Share

Latest [Jul 02, 2026] Plat-Admn-201 Exam Questions – Valid Plat-Admn-201 Dumps Pdf

Plat-Admn-201 Practice Test Questions Answers Updated 160 Questions


Salesforce Plat-Admn-201 Exam Syllabus Topics:

TopicDetails
Topic 1
  • Productivity and Collaboration: This domain addresses activity management, Chatter collaboration, Salesforce mobile app customization, and AppExchange applications including managed and unmanaged packages.
Topic 2
  • Object Manager and Lightning App Builder: This domain focuses on Salesforce data architecture, including object relationships, field customization, page layout management, and understanding the implications of field deletions on dependent features.
Topic 3
  • Configuration and Setup: This domain covers foundational administrative tasks including company settings, user interface configuration, user management with licenses and access controls, and implementing security measures through login restrictions and the Salesforce sharing model.
Topic 4
  • Sales and Marketing Applications: This domain addresses sales cycle management from leads to opportunities, including productivity features, lead automation, campaign management, forecasting, and Einstein for Sales capabilities.
Topic 5
  • Agentforce AI: This domain introduces AI-powered agents in Salesforce, covering use cases, configuration in Agent Builder, security considerations, and troubleshooting agent permissions.
Topic 6
  • Automation: This domain covers automation tools for streamlining business processes, including assignment and escalation rules, Flow configuration for various scenarios, and approval process setup.

 

NEW QUESTION # 51
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?

  • A. Flow Orchestration
  • B. Flow Builder
  • C. Quick Action
  • D. Outbound Message

Answer: B

Explanation:
Flow Builder is the recommended tool for automating updates to multiple related records based on a change to a single record. A "Record-Triggered Flow" can be configured to execute whenever an Opportunity is updated to "Closed Won". The flow can then find all other Opportunities related to the same Account where the "IsClosed" field is false, and use an Update Records element to set their stage to "Closed Lost". Outbound Messages (Option B) are used for notifying external systems, not for internal data updates. Flow Orchestration (Option C) is designed for multi-user, complex business processes and would be overly complicated for this simple record update. Quick Actions (Option D) require a user to click a button, which does not meet the requirement for automatic rendering upon the stage change.


NEW QUESTION # 52
A VP of sales needs to report on records owned by individuals in various parts of the role hierarchy. The organization-wide default is set to Private. What should a Platform Administrator configure to achieve this?

  • A. Permission Sets
  • B. Sharing Rules
  • C. Restriction Rules
  • D. Field-Level Security

Answer: B

Explanation:
When the Organization-Wide Default (OWD) for an object is set to Private, users can only see records they own or those shared with them. While the Role Hierarchy automatically grants "upward" visibility (managers see what subordinates own), it does not naturally allow for "lateral" visibility or visibility across different branches of the hierarchy. To solve this, a Platform Administrator should use Sharing Rules. Sharing Rules allow the admin to create exceptions to the Private OWD based on record ownership or specific criteria. For example, the admin can create an "Owner-based Sharing Rule" that shares all records owned by the "East Coast Sales" role with the VP of Sales (or a Public Group the VP belongs to). This provides a scalable way to grant the necessary visibility for reporting without making the data public to the entire company. Sharing Rules are a core security feature that ensures the right people have access to the right data while maintaining the principle of least privilege.


NEW QUESTION # 53
The client services and customer support teams share the same profile but have different permission sets. The custom object Retention related list needs to be restricted to the client services team on the Lightning record page layout. What should a Platform Administrator use to fulfill this request?

  • A. Sharing Settings
  • B. Component Visibility
  • C. Page Layout Assignment
  • D. Record Type Assignment

Answer: B

Explanation:
When users share the same profile but require different user interface experiences, Component Visibility is the most effective tool. In the Lightning App Builder, the administrator can select the
"Related List" component (or a "Related List - Single" component for Retention) and add a visibility filter. The filter can be set to "User > Permission > Custom Permission" or "User > Profile," but since they share a profile, the best approach is to filter based on a Permission Set or a specific user field. This allows the Retention list to be visible only to the Client Services team members while remaining hidden for the Customer Support team, even though they are looking at the same record. Page Layout Assignment (Option A) and Record Type Assignment (Option C) are profile-based and would not work since the teams share a profile. Sharing Settings (Option D) control access to the data itself, but the request specifically asks to hide the UI element (the related list).


NEW QUESTION # 54
Cloud Kicks (CK) is partnering with a used shoe store and second-hand bicycle emporium. CK has an automated business process it wants to run once a week to count the number of open cases related to an Account. Which flow should a Platform Administrator recommend automating within Flow Builder for this business process?

  • A. Scheduled flow
  • B. Record triggered flow
  • C. Autolaunched flow
  • D. Automation event triggered flow

Answer: A

Explanation:
For any business process that needs to run at a specific time interval (in this case, "once a week"), a Scheduled flow is the standard tool. A scheduled flow allows the Platform Administrator to define a frequency (Daily, Weekly, or Once) and a start time57. The flow can then query all relevant Account records and perform the logic of counting open cases and updating the parent record autonomously58. Record-triggered flows (Option B) are inappropriate here because the count needs to happen on a schedule rather than being triggered by an individual record edit59. Autolaunched flows (Option C) must be called by another process, such as a button or Apex, and do not have their own timing mechanism60. "Automation event triggered flow" (Option D) is not a standard type of flow used for recurring batch processing


NEW QUESTION # 55
Ursa Major Solar has its business hours set from 9:00 AM to 5:00 PM for the reps that are on Pacific Time. The reps on Eastern Time need business hours set to start 3 hours earlier to cover for support. How should a Platform Administrator solve for this issue?

  • A. Create one set of business hours per time zone.
  • B. Allow the reps to set business hours manually.
  • C. Adjust the current business hours to accommodate the Eastern time zone.
  • D. Set temporary business hours for each time zone.

Answer: A

Explanation:
Salesforce allows for the creation of multiple Business Hours records to support global teams working in different time zones. To solve the requirement for Ursa Major Solar, the Platform Administrator should create two distinct sets of business hours: one for "Pacific Support" (9 AM - 5 PM PT) and one for "Eastern Support" (9 AM - 5 PM ET). This is essential because Business Hours are used by the system to calculate escalation rules and milestones correctly. For example, an escalation rule for an Eastern-based case 1should start counting at 9 AM ET, not 9 AM PT. Adjusting the current record to "accommodate" both (Option A) would result in a 12-hour window that doesn't accurately reflect either team's true availability. Users cannot manually set their own business hours (Option B) in a way that affects system automation. Creating one set per time zone ensures that the support team's performance metrics and automated routing are accurate and localized.


NEW QUESTION # 56
A Platform Administrator at Universal Containers needs an automated way to delete records based on field values. Which automated solution should the administrator use?

  • A. Flow Orchestration
  • B. Flow Builder
  • C. Automation Studio
  • D. Mass Delete Records

Answer: B

Explanation:
Flow Builder is the standard and most versatile tool for performing automated data maintenance, including the deletion of records. A "Schedule-Triggered Flow" can be configured to run at specific intervals (e.g., daily at midnight) to find records that meet certain criteria-such as Leads that have been "Unqualified" for over a year-and use the "Delete Records" element to remove them from the system. While the "Mass Delete Records" tool (Option C) exists in the Setup menu, it is a manual administrative tool and cannot be scheduled or fully automated based on complex field-level logic. Automation Studio (Option B) is a Marketing Cloud tool, not a core Salesforce platform feature for record management. Flow Orchestration (Option D) is used for complex, multi-user business processes rather than simple data cleanup tasks. Therefore, for recurring, criteria-based record deletion, Flow Builder is the recommended solution.


NEW QUESTION # 57
Ursa Major Solar wants to roll out the Salesforce mobile app, and the first information it wants its users to see is the Top Opportunities report. What should a Platform Administrator configure to achieve this?

  • A. Enable Mobile Home for the Salesforce mobile app.
  • B. Add the Dashboards tab to the Salesforce mobile app.
  • C. Add the Reports tab to the Salesforce mobile app.
  • D. Enable Today for the Salesforce mobile app.

Answer: A

Explanation:
Mobile Home is a customizable landing page for the Salesforce mobile app that acts as the default "start page" for users. It allows administrators to add various "cards" or "widgets," including reports, pinned records, and upcoming events. By enabling and configuring Mobile Home, a Platform Administrator can place a specific Report card (such as "Top Opportunities") at the very top of the screen, ensuring it is the first thing users see upon opening the app. While adding the Reports tab (Option A) or Dashboards tab (Option D) allows users to find the information, it does not automatically present specific report data on the home screen. The "Today" feature (Option B) focuses on calendar events and tasks rather than customized reporting data17.


NEW QUESTION # 58
Cloud Kicks has the organization wide defaults for Opportunity set to Private. Which two features should a Platform Administrator use to open up access to opportunity records for sales users working on collaborative deals? 63

  • A. Role hierarchy
  • B. Profiles
  • C. Sharing set
  • D. Sharing rules

Answer: A,D

Explanation:
When an object's Organization-Wide Default (OWD) is set to Private, the "Record Sharing" engine must be used to grant additional access.
Sharing Rules: These allow the administrator to grant lateral access to records based on criteria or ownership (e.g., share all "Large Deals" with the "Strategic Sales" group).
Role Hierarchy: This standard feature automatically grants vertical access, ensuring that managers and users higher in the hierarchy can see and edit records owned by their subordinates.
Profiles (Option D) control what actions a user can perform (Create, Read, Edit) but do not grant access to specific records that the user does not own in a Private model. A Sharing Set (Option B) is a specific feature used for Experience Cloud (Community) users to grant them access to records related to their account and is not used for standard internal sales users.


NEW QUESTION # 59
Northern Trail Outfitters has two different sales processes: one for business opportunities with four stages and one for partner opportunities with eight stages. Both processes will vary in page layouts and picklist value options. What should a Platform Administrator configure to meet these requirements?

  • A. Validation rules that ensure that users are entering accurate sales stage information
  • B. Different page layouts that control the picklist values for the opportunity types
  • C. Separate record types and sales processes for the different types of opportunities
  • D. Public groups to limit record types and sales processes for opportunities

Answer: C

Explanation:
To manage different business requirements for a single object like Opportunities, Salesforce utilizes a combination of Record Types and Sales Processes. A Sales Process is a specific feature for the Opportunity object that allows an administrator to select which "Stage" picklist values are visible. In this scenario, the admin would create one Sales Process for "Business" (4 stages) and another for "Partner" (8 stages). Once these processes are defined, they are linked to Record Types. Record Types are the engine that allows different users to see different Page Layouts and picklist options based on the "type" of record they are creating. This architecture ensures that users working on Partner deals are guided through the appropriate eight stages and see the relevant fields on their layout, while Business users have a streamlined four-stage experience. This separation is critical for maintaining data integrity and ensuring that the reporting for each pipeline is accurate. It prevents confusion by only showing users the options that are relevant to the specific context of the deal they are managing.


NEW QUESTION # 60
What are three characteristics of a master-detail relationship?

  • A. The owner field on the detail records is the owner of the master record.
  • B. Each object can have up to five master-detail relationships.
  • C. Permissions for the detail record are set independently of the master.
  • D. The master object can be a standard or custom object.
  • E. Roll-up summaries are supported in master-detail relationships.

Answer: A,D,E

Explanation:
A Master-Detail Relationship is a tight coupling between two objects that provides several unique functionalities:
Master Object Types: The master can be either a standard object (like Account) or a custom object (Option B).
Roll-up Summaries: This relationship type is the only one that natively supports Roll-up Summary fields, allowing the master record to calculate counts, sums, or averages of fields on the detail records (Option C).
Ownership and Security: The detail record inherits its owner and its security/sharing settings from the master record. Consequently, there is no "Owner" field on a detail record; it is always owned by the owner of the master (Option D).
Option A is incorrect because detail records cannot have independent permissions. Option E is incorrect because an object can only have a maximum of two master-detail relationships. This relationship is ideal for parent-child scenarios where the child's existence is entirely dependent on the parent.


NEW QUESTION # 61
The sales and service teams at Cloud Kicks would like to have more visibility into their pipeline and stay on top of every case. A Platform Administrator needs to quickly create dashboards for each of the teams but does not know where to start. What should the administrator do?

  • A. Use the Salesforce Labs Field Service Dashboards for service teams from AppExchange.
  • B. Use the Salesforce Labs CRM Dashboards for sales teams from AppExchange.
  • C. Manually create dashboards without using any prebuilt templates or packages.
  • D. Enable Einstein Analytics and build custom dashboards using advanced analytics tools.

Answer: B

Explanation:
For an administrator who needs to deliver high-quality dashboards "quickly" and "doesn't know where to start," the AppExchange is the best resource. Salesforce Labs provides several free, pre-configured dashboard packages (like the "CRM Dashboards") that include standard components for sales pipeline, lead tracking, and case management. These packages serve as an excellent baseline that can be installed in minutes and then customized to fit the specific needs of Cloud Kicks. Manually creating everything (Option D) is time-consuming. Einstein Analytics (Option B) is a separate, more complex product that requires extra licensing and setup. Option A is too narrow, as it focuses specifically on "Field Service" rather than general sales and service visibility.


NEW QUESTION # 62
A sales manager receives a URL to a Dashboard folder containing several dashboards. However, when the sales manager clicks on the URL, a message appears stating, "We couldn't find the record you're trying to access." What is the reason for this?

  • A. View access has not been granted to the Dashboard folder.
  • B. The sales manager does not have the correct permission set.
  • C. The sales manager needs the correct sales user profile.
  • D. The Dashboard folder is set to Private.

Answer: A

Explanation:
In Salesforce, access to reports and dashboards is controlled at the Folder level. Even if a user has the direct URL to a dashboard, they cannot view it unless the folder containing that dashboard has been shared with them. When a user receives the "We couldn't find the record" error, it typically means they lack View access to the folder. To resolve this, the owner of the folder (or an administrator) must go to the folder's sharing settings and explicitly add the sales manager, their role, or a public group they belong to. Options A and B are less likely because standard sales profiles usually have the general "Run Reports" and "View Dashboards" permissions; the issue here is specific record-level access to that folder's content. Option C is a specific state of a folder (Private to the creator), which is essentially the same as saying access has not been granted to others.


NEW QUESTION # 63
A Platform Administrator at Ursa Major Solar wants to add prepopulated subjects for Tasks and Events. Tasks should have the subjects "Schedule Site Visit" and "Send Contract", while Events should have the subjects "Site Visit" and "Ride Along". What should the administrator configure to achieve this requirement?

  • A. Create a new custom Subject picklist field on Activity and add the field values.
  • B. Add the new values to the predefined field values for the global actions New Event and New Task.
  • C. Add Schedule Site Visit and Send Contract picklist values for the Task subject field. Add Site Visit and Ride Along picklist values for the Event subject field.
  • D. Include Schedule Site Visit, Send Contract, Site Visit, and Ride Along picklist values for the Activity subject field.

Answer: C

Explanation:
Tasks and Events are both part of the Activity object, but they often require different picklist values for the standard Subject field. To achieve this, the Platform Administrator must manage the picklist values for the Subject field specifically for each record type or activity type. In the Object Manager, under the Activity object (or Task/Event objects individually in some setups), the admin should edit the Subject field. Because Task and Event are distinct entities with their own picklist value sets for the Subject field, the admin can add "Schedule Site Visit" and "Send Contract" to the Task Subject list and "Site Visit" and "Ride Along" to the Event Subject list. This ensures that when a user creates a Task, they only see task-related subjects, and when they create an Event, they see event-related subjects. Option D is incorrect because it would mix all values together, causing confusion for the users. Option A (Predefined Field Values) is used to set a single default value for a field when an action is clicked, but it does not manage the available list of options in a picklist.


NEW QUESTION # 64
Once an opportunity reaches the negotiation stage at Cloud Kicks, the Amount field becomes required for sales users. Sales managers need to be able to move opportunities into this stage without knowing the amount. How should a Platform Administrator require this field during the negotiation stage for sales users but allow their managers to make changes?

  • A. Create a formula field to fill in the field for managers.
  • B. Configure a validation rule to meet the criteria.
  • C. Assign the Administrator profile to the managers.
  • D. Make the field required for all users.

Answer: B

Explanation:
A Validation Rule is the only way to enforce conditional requirement logic based on both record data (the stage) and user data (the user's profile or role). To achieve this, the Platform Administrator would write a formula that checks three things: if the Stage is "Negotiation," if the Amount field is blank, and if the user is not a manager. The formula would look something like:
AND(ISPICKVAL(StageName, "Negotiation"), ISBLANK(Amount), $Profile.Name <> "Sales Manager"). This allows the system to block standard sales users from saving the record without an amount, while the exception for the manager's profile allows them to bypass the requirement.
Making the field required on the page layout (Option A) would affect all users equally, failing to meet the requirement for managers. Assigning the Admin profile to managers (Option B) is a major security risk and violates the principle of least privilege.


NEW QUESTION # 65
At Cloud Kicks, sales reps use discounts on the opportunity record to help win sales on particular products. When an opportunity is won, they then have to manually apply the discount to the related opportunity products. The sales manager has asked if there is a way to automate this time-consuming task. What should a Platform Administrator use to deliver this requirement?

  • A. Prebuilt Macro
  • B. Formula Field
  • C. Approval Process
  • D. Flow Builder

Answer: D

Explanation:
To automate the update of related records (Opportunity Products) based on a change to a parent record (the Opportunity), Flow Builder is the most powerful and app7ropriate tool. Specifically, a
"Record-Triggered Flow" can be configured to fire whenever an Opportunity is updated to the
"Closed Won" stage. The flow can then use a "Get Records" element to find all Opportunity Product records associated with that specific Opportunity and an "Update Records" element to apply the discount value from the parent to each line item. Formula Fields are insufficient here because they are "read-only" and cannot physically push data into other records for permanent storage. Approval Processes manage status changes but are not designed for bulk child-record updates. Flow Builder provides the logic necessary to handle this "one-to-many" update scenario, significantly reducing manual data entry for sales reps and ensuring that the financial data on the products accurately reflects the agreed-upon deal terms.


NEW QUESTION # 66
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? 99

  • A. Existing field values will be converted.
  • B. Existing field values will remain unchanged.
  • C. Existing field values will be deleted.
  • D. Changing Auto Number field to Text is prevented.

Answer: B

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.


NEW QUESTION # 67
Ursa Major Solar classifies its accounts as Silver, Gold, or Platinum Level. When a new case is created for a Silver or Gold partner, it should go to the Regular Support Queue. When an account is Platinum Level, it should automatically go to the Priority Support Queue. What should a Platform Administrator use to achieve this?

  • A. Escalation Rules
  • B. Case Rules
  • C. Assignment Rules
  • D. Workflow Rules

Answer: C

Explanation:
Case Assignment Rules are the standard Salesforce tool for automatically routing cases to specific users or queues based on record criteria. A single assignment rule can contain multiple
"Rule Entries" processed in a specific order. To meet this requirement, the Platform Administrator would create a rule with two entries: one that checks if the Account's "Level" field equals
"Platinum" and routes it to the Priority Support Queue, and another that checks if the level is
"Silver" or "Gold" and routes it to the Regular Support Queue. This automation happens the moment the case is created, ensuring that high-value customers receive immediate attention from the appropriate team. Escalation Rules (Option A) are used to move a case after it has been sitting for a period of time, not for initial routing. Workflow Rules (Option D) are a legacy tool that cannot natively assign cases to queues in the same direct manner as Assignment Rules.


NEW QUESTION # 68
A Platform Administrator wants to limit the kinds of reports their users can create. Which tool should the administrator use?

  • A. Report Folder Sharing
  • B. Standard Report Types
  • C. Hide Report Types
  • D. Joined Report

Answer: C

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.


NEW QUESTION # 69
Cloud Kicks wants a report to categorize accounts into small, medium, and large based on the dollar value found in the Contract Value field. Which feature should a Platform Administrator use to meet this request?

  • A. Detail Column
  • B. Bucket Column
  • C. Group Rows
  • D. Filter Logic

Answer: B

Explanation:
In Salesforce reporting, a Bucket Column is the most efficient tool for categorizing records without the need for creating custom fields or complex formula logic. Bucketing allows an administrator to define ranges of values for a field-such as the "Contract Value" currency field-and assign a label to each range, such as "Small," "Medium," or "Large." This is particularly useful for grouping data into segments that do not exist natively in the data model. For example, if a "Small" account is defined as anything under $50,000 and "Large" is over $200,000, the bucket tool allows the admin to visually organize these in the report builder interface. Unlike Grouping Rows, which merely clusters identical values together, a Bucket Column transforms raw data into meaningful categories for visualization. This feature significantly enhances data storytelling by providing a summarized view of account distribution based on specific financial thresholds without impacting the actual Account record or requiring administrative overhead for new fields.


NEW QUESTION # 70
Cloud Kicks wants Agentforce to adapt its behavior based on real-time customer input. Which feature directly enables this capability?

  • A. Screen flow
  • B. Custom actions
  • C. Data Cloud
  • D. Tableau

Answer: B

Explanation:
Agentforce is built to be dynamic, meaning it doesn't just follow a static script but rather "reasons" through a problem using an agentic loop. The feature that directly allows an agent to adapt its behavior and take specific, real-time steps based on customer input is Custom Actions. When a customer provides information--such as a specific order number or a request to change an address--the agent identifies the user's intent and selects the most relevant action to execute.
These actions can be powered by Flows, Apex, or Prompt Templates, giving the agent the ability to interact with Salesforce data in real-time. While Data Cloud (Option A) provides the data foundation for grounding, it is the actions themselves that define the agent's behavioral capabilities. Screen flows (Option C) provide a guided UI for humans, but custom actions are what allow the agent to function autonomously. Tableau (Option D) is an analytics tool and does not drive real-time agent behavior.


NEW QUESTION # 71
......

Plat-Admn-201 dumps Sure Practice with 160 Questions: https://passguide.vce4dumps.com/Plat-Admn-201-latest-dumps.html