2026 Realistic Plat-Admn-201 100% Pass Guaranteed Download Exam Q&A
Accurate Plat-Admn-201 Answers 365 Days Free Updates
NEW QUESTION # 88
A sales manager at DreamHouse Realty wants sales users to have a quick way to view and update the opportunities in their pipeline expected to close in the next 90 days. What should a Platform Administrator do to accomplish this request?
- A. Enable Sales Console and show users how to open a tab for each opportunity in the pipeline that meets the requirements.
- B. Create a custom report and schedule the sales users to receive it each day as a reminder to update their opportunities.
- C. Make a new Sales dashboard and add a component that shows all opportunities that meet the criteria.
- D. Create a list view on the Opportunity object and recommend users switch the view to Kanban to edit by drag and drop.
Answer: D
Explanation:
To provide both a "quick view" and a way to "update" records efficiently, a List View combined with the Kanban view is the most effective solution. The Platform Administrator can create a public list view with the filter "Close Date equals NEXT 90 DAYS." By switching this list view to the Kanban display, sales reps can see their deals organized by stage. The Kanban view allows for rapid updates via drag-and-drop, which automatically changes the Stage field, and provides side-panel editing for other key fields. While reports (Option A) and dashboards (Option B) are good for visualization, they are not optimized for the rapid, bulk record updates the manager is requesting. The Kanban view is a native productivity feature designed specifically to streamline pipeline management for sales users.
NEW QUESTION # 89
Sales managers would like to know what could be implemented to surface important values based on the stage of the opportunity? Which tool should a Platform Administrator use to meet this requirement?
- A. Workflow Rules
- B. Dynamic Forms
- C. Path Key Fields
- D. Opportunity Processes
Answer: C
Explanation:
The Opportunity Path is a visual tool that guides sales reps through the stages of a sales cycle. One of its most powerful features for administrators is the ability to define Key Fields for each individual stage. For example, when an opportunity is in the "Discovery" stage, the administrator can choose to display fields like "Budget" and "Decision Maker." When the deal moves to "Negotiation," the Path can be configured to surface "Contract Terms" and "Discount Percentage." This ensures that reps are prompted to enter and review the most relevant data at exactly the right time in the process. While Dynamic Forms (Option D) can show or hide fields on the main record page, the Path specifically organizes this information at the top of the record in a way that is directly tied to the sales methodology. Workflow Rules (Option A) are a legacy automation tool that cannot modify the user interface. Path Key Fields empower sales teams to maintain focus and data accuracy throughout the deal lifecycle.
NEW QUESTION # 90
Cloud Kicks wants to make sure clients are getting the attention they need and cases are not sitting longer than the Service Level Agreement (SLA) it has with its clients. Which standard feature helps route cases to a Tier 2 team if they have not been addressed in a specific amount of time?
- A. Auto Response Rules
- B. Milestone and Entitlements
- C. Omni Channel Routing
- D. Escalation Rules
Answer: D
Explanation:
Escalation Rules are specifically designed to ensure that cases do not violate a company's Service Level Agreements (SLAs). When a case meets predefined criteria and remains open for a specific duration--such as two hours or seven days--the escalation rule automatically triggers. A Platform Administrator can configure these rules to perform two primary actions: reassigning the case to a different user or queue (such as a Tier 2 support team) and sending notification emails to managers or the new owner to ensure the delay is addressed. While Milestones and Entitlements (Option A) are used to track and display SLA compliance on a record, Escalation Rules are the functional engine used to physically "route" or move the record based on time- based triggers. Omni-Channel (Option B) handles real-time routing based on agent availability rather than time-elapsed thresholds. Auto-Response Rules (Option C) are used only to send initial confirmation emails to customers upon case creation.
NEW QUESTION # 91
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. Use Campaign Hierarchy where the monthly events roll up to a parent Campaign.
- C. Add different record types for the monthly event types.
- D. Configure Campaign Member Statuses to record which event Members attended.
Answer: B
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.
NEW QUESTION # 92
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?
- A. Submit for Approval button
- B. Apex Triggers
- C. Einstein Next Best Action
- D. Flow Approvals
Answer: D
Explanation:
The requirement to have a record "signed off" by a specific individual (the CFO) based on a dollar threshold is a classic use case for an Approval Process . While the "Submit for Approval" button (Option A) allows a user to manually start the process, the prompt specifies that the process should happen "automatically"50. To achieve this automation, the Platform Administrator should use Flow Builder to trigger the approval process . A Record-Triggered Flow can be set to run when an Opportunity is created or updated and meets the criteria (Amount > $100,000) . The flow would then use the "Submit for Approval" action to launch the record into the predefined approval process without requiring the sales rep to click a button . Einstein Next Best Action (Option B) is a recommendation tool, not a workflow enforcement tool54. Apex Triggers (Option C) could perform this task, but Salesforce best practices recommend using "clicks not code" (Flow) whenever possible for such requirements . Using Flow to launch an Approval Process provides the necessary automation, routing, and audit trail the CFO requires
NEW QUESTION # 93
A Platform Administrator at Cloud Kicks has a custom picklist field on Lead, which is missing on the Contact when leads are converted. Which two steps should the administrator take to ensure these values are populated?
- A. Set the picklist field to be required on the Lead object.
- B. Create a custom picklist field on Contact.
- C. Map the picklist field on the Lead to the Contact.
- D. Update the picklist value with a validation rule.
Answer: B,C
Explanation:
2
When a Lead is converted into an Account, Contact, and Opportunity, standard fields are mapped automatically. However, custom fields require manual configuration to ensure d3ata flows through the conversion process. First, the Platform Administrator must create a corresponding custom picklist field on the Contact object (Option B) with the same values as the Lead field. Second, the administrator must go to the Lead Object Manager, select "Fields & Relationships," and click Map Lead Fields (Option C). Here, the admin explicitly maps the Lead custom picklist to the newly created Contact custom picklist. Without this mapping, the data will be lost during conversion. Validation rules (Option A) and making the field required (Option D) ensure data exists on the Lead but do not facilitate the transfer of that data to the Contact.
NEW QUESTION # 94
A group of sales reps can view each other's orders on a report; however, they would like a report to view just their own orders. What should a Platform Administrator do to set up a report for the sales reps? 31
- A. Filter by Opportunity Owner equals $USER.
- B. Set the Opportunity Filter for Primary as True.
- C. Set Organization Wide Defaults of Order object to Private.
- D. Save the report in a private folder for the user.
Answer: A
Explanation:
In Salesforce reporting, administrators can use relative date and user filters to make a single report template dynamic for every person who views it. By setting the filter to Opportunity Owner (or Order Owner) equals $USER, the report will automatically filter the results to show only those records owned by the individual currently logged in and viewing the report. This is much more efficient than creating separate reports for every rep. While setting the Organization-Wide Defaults to Private (Option C) would restrict general visibility, it does not help if the reps need to be able to see each other's data for other business reasons but simply want a "clean" personal view for daily tasks36. Saving the report in a private folder (Option D) only restricts who can see the report itself, not the data contained within it. Using the $USER variable is the standard way to provide personalized, relevant data views in a shared reporting environment.
NEW QUESTION # 95
A Platform Administrator needs to enable Agentforce for the service team. What is the most critical prerequisite for ensuring the Service Agents have a complete and accurate view of their customers?
- A. Configure a new Service Console layout.
- B. Verify Data Cloud is implemented.
- C. Activate Email-to-Case for the agent.
- D. Create new user profiles for the agent.
Answer: B
Explanation:
For an AI agent to provide "complete and accurate" support, it needs access to a unified, 360- degree view of the customer data. Data Cloud is the critical prerequisite because it ingests, harmonizes, and unifies data from multiple sources (Salesforce, external databases, legacy systems) into a single "Unified Profile." When Agentforce is "grounded" in Data Cloud, it can reference real-time customer interactions, purchase history, and cross-channel behavior that might not exist in a single Case or Contact record. Without Data Cloud, the agent's knowledge is limited to siloed data, which increases the risk of providing incomplete or irrelevant answers.
While Console layouts (Option B) and intake methods (Option A) are important for the UI, they do not provide the data foundation necessary for advanced AI reasoning.
NEW QUESTION # 96
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. Hide Report Types
- C. Standard Report Types
- D. Joined Report
Answer: B
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 # 97
Cloud Kicks has been seeing exponential growth and will be hiring an additional 10 sales reps and 15 support reps to its teams. The support team will need access to the Service Console to manage cases. A Platform Administrator will be assigning the users to existing custom sales and support profiles. How should the administrator ensure the support reps have the appropriate access to the console?
- A. Enable the Service Cloud User feature license for the support reps on the User Detail page.
- B. Assign the Salesforce Platform User License to the support reps.
- C. Create a permission set for the Service Console and assign it to the support reps.
- D. Build a Service Console using Lightning App Builder for the custom service profile.
Answer: A
Explanation:
Access to the Service Console and other advanced Service Cloud features (like Entitlements or Knowledge) requires a specific Feature License called the Service Cloud User. Even if a user's profile has the "Manage Cases" permission, they will not be able to access the specialized Console app unless the "Service Cloud User" checkbox is selected on their individual User record. This is a common administrative step when onboarding new support staff. Permission sets (Option B) grant functional permissions but cannot grant feature licenses. Assigning a "Platform User License" (Option D) would actually restrict them, as that license type does not include access to standard CRM objects like Cases or the Service Console.
NEW QUESTION # 98
A Platform Administrator is creating a new action instruction for an agent. This action, named createCase, is designed to generate a new Salesforce Case record based on the user's conversation with the agent. Which set of Action Instructions should the administrator use for the createCase action, according to best practices for action instructions?
- A. "The createCase code snippet is configured to create a case. It runs in the background to handle the user's request to log a new issue. Its purpose is to solve the customer's issue."
- B. "This action provides the ability to create a new case record in the Salesforce system. Its function is to simply save customer information as a record. Use this when the user wants to create a case."
- C. "Creates a new case record in the system for any type of customer inquiry. The purpose of this is to ensure a record of the interaction is saved."
- D. "Use this action to create a new Salesforce Case record. The goal is to document a customer's issue in the system. Use this when the user's intent is to create a formal record of their problem or question."
Answer: D
Explanation:
Best practices for Agentforce Action Instructions emphasize clarity, intent, and specific usage scenarios to help the LLM (Large Language Model) understand exactly when and why to trigger an action. Option B is the best choice because it explicitly defines the Action (create a Case), the Goal (document a customer's issue), and the User Intent (formal record of a problem or question). High-quality instructions act as a guide for the agent's reasoning process. Vague instructions, like those in Option A or C, may lead to the agent triggering the action at inappropriate times, such as during a simple inquiry that doesn't require a formal case.
Instructions that focus on "code snippets" (Option D) are less effective because the LLM needs to understand the functional business context rather than the technical implementation details to interact naturally with the user.
NEW QUESTION # 99
A sales rep typically has several open opportunities for each of their accounts. Which tool should a Platform Administrator suggest to the sales rep to obtain the total number of accounts associated with open opportunities in a report?
- A. Report Filter
- B. Group Rows
- C. Bucket Column
- D. Unique Count
Answer: D
Explanation:
When a report contains many rows where the same Account name appears multiple times (due to having several opportunities), a simple count of rows will not accurately represent the number of distinct accounts. To find the specific number of individual accounts, the Platform Administrator should use the Unique Count feature on the Account Name or Account ID column in the report builder. Selecting "Show Unique Count" provides a total at the bottom of the report (and in summary groupings) that counts each unique value only once, regardless of how many times it appears in the list. Bucket Columns (Option A) group data into categories. Report Filters (Option B) exclude records. Grouping Rows (Option D) visually organizes the report by Account but does not inherently provide a single summary number for the count of distinct accounts in the way that Unique Count does.
NEW QUESTION # 100
At Cloud Kicks, cases are being assigned a default Case Owner and showing a Created By and Last Modified By that is not expected. The company wants to change this to an integration user to alleviate confusion with the business. What should a Platform Administrator edit to change this in Salesforce?
- A. Support Settings
- B. Process Automation Settings
- C. Debug Logs
- D. Support Processes
Answer: A
Explanation:
In Salesforce, Support Settings is the primary configuration page for determining how the Service Cloud handles automated case updates. This section allows a Platform Administrator to define the "Default Case Owner" and the "Automated Case User." The Automated Case User is the user listed in the Case History for automated actions, such as those triggered by assignment rules, escalation rules, or Email-to-Case. If the business sees an "unexpected" user name in the Created By or Last Modified By fields during these automated processes, it is usually because this setting is pointing to a specific administrator or a system user. By updating the Automated Case User to a dedicated "Integration User," the admin ensures that the audit trail clearly distinguishes between manual edits made by staff and automated updates made by the system. This provides better clarity for the support team and prevents confusion regarding who is responsible for specific record changes.
NEW QUESTION # 101
A manager wants the sales team to update their opportunities on a regular basis. Which feature should a Platform Administrator implement to help with this?
- A. Scheduled Reports
- B. Big Deal Alerts
- C. Similar Opportunities
- D. Opportunity Update Reminders
Answer: D
Explanation:
Opportunity Update Reminders is a specific, automated feature in Salesforce designed exactly for this purpose. When enabled, it allows managers to automatically send an email to their direct reports with a list of their open opportunities. The email serves as a prompt for the reps to review their deals and ensure close dates, amounts, and stages are current. This is more effective than a general Scheduled Report (Option D) because it is a purpose-built notification system that can be configured by the manager. Big Deal Alerts (Option C) are for high-value deal notifications, not general pipeline hygiene. Similar Opportunities (Option A) helps with sales strategy but does not encourage record updates.
NEW QUESTION # 102
One of the sales managers at Universal Containers will be going on leave for several months. The executives want to make sure the sales manager does not log in to Salesforce while on leave. What should a Platform Administrator do to ensure the user is not able to log in while on leave?
- A. Restrict Login IP Addresses for the profile.
- B. Change the Login Hours for the profile.
- C. Freeze the user's account.
- D. Reassign the user's license during leave.
Answer: C
Explanation:
When a user needs to be temporarily prevented from logging in-but their records, role, and historical data need to remain intact-the best practice is to Freeze the user. Freezing an account stops the user from accessing the system immediately without "Deactivating" them. Deactivation can be problematic if the user is a "running user" for dashboards or is part of active hierarchy logic that might break if the account is disabled. Freezing is a simple "one-click" action on the user record. Reassigning the license (Option A) would require deactivating the user first. Changing login hours (Option B) or IP addresses (Option D) at the profile level would impact all users assigned to that profile, not just the individual manager on leave. Freezing provides a targeted and temporary solution for managing individual user access.
NEW QUESTION # 103
Universal Containers (UC) customers have provided feedback that their support cases are not being responded to quickly enough. UC wants to send all unassigned cases that have been open for more than 2 hours to an urgent Case queue and alert the support manager. Which feature should a Platform Administrator configure to meet this requirement?
- A. Case Dashboard Refreshes
- B. Case Escalation Rules
- C. Case Assignment Rules
- D. Case Scheduled Reports
Answer: B
Explanation:
Case Escalation Rules are specifically designed to automate actions when a case has remained in a certain state for a defined period of time. In this scenario, the requirement involves two specific time-based triggers: moving the case after 2 hours and alerting a manager. Escalation rules allow the administrator to define "Escalation Actions" that execute when the time threshold is reached, such as "Reassign to Queue" and "Notify Manager". Case Assignment Rules (Option D) only fire when a case is first created or manually triggered, not after a time delay63. Reports (Option A) and Dashboards (Option B) provide information but do not physically move records or perform automated reassignments.
NEW QUESTION # 104
One of the sales managers at Universal Containers will be going on leave for several months.
The executives want to make sure the sales manager does not log in to Salesforce while on leave. What should a Platform Administrator do to ensure the user is not able to log in while on leave?
- A. Restrict Login IP Addresses for the profile.
- B. Change the Login Hours for the profile.
- C. Freeze the user's account.
- D. Reassign the user's license during leave.
Answer: C
Explanation:
When a user needs to be temporarily prevented from logging in--but their records, role, and historical data need to remain intact--the best practice is to Freeze the user. Freezing an account stops the user from accessing the system immediately without "Deactivating" them. Deactivation can be problematic if the user is a "running user" for dashboards or is part of active hierarchy logic that might break if the account is disabled. Freezing is a simple "one-click" action on the user record. Reassigning the license (Option A) would require deactivating the user first.
Changing login hours (Option B) or IP addresses (Option D) at the profile level would impact all users assigned to that profile, not just the individual manager on leave. Freezing provides a targeted and temporary solution for managing individual user access.
NEW QUESTION # 105
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. Configure Opportunity Path.
- B. Use validation rules.
- C. Use Flow to mark fields required.
- D. Enable guided selling.
- E. Mark fields required on the page layout.
Answer: A,B,E
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.
NEW QUESTION # 106
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 # 107
Universal Containers wants to implement collaborative selling where multiple roles work together on customer accounts. Sales reps need full access to their assigned accounts, while customer support reps and sales engineers need access to opportunities and cases related to specific accounts they support. The sales manager wants to streamline the process by automatically adding the same team members to multiple accounts. Which feature should a Platform Administrator configure to meet this requirement?
- A. Configure role hierarchy to automatically grant account access to the appropriate teams.
- B. Set up default account teams with specified access levels for different team roles.
- C. Create sharing rules to grant access to opportunities and cases for support teams.
- D. Use permission sets to provide additional access to account-related records.
Answer: B
Explanation:
Account Teams are designed specifically for "collaborative selling," allowing multiple users to work together on a single Account . By using Account Teams, an administrator can define specific roles (e.g., Sales Engineer, Support Rep) and grant them varying levels of access (Read/Write or Read Only) to the Account and its related Opportunities and Case . To meet the manager's requirement of "streamlining" and "automatically adding" members, the administrator should encourage users to set up Default Account Teams . Once a user defines their default team in their personal settings, they can click a single button to add that entire team to any Account they own . Sharing Rules (Option B) are typically too broad for this requirement because they apply to all records meeting a criteria, rather than specific collaborative groups61. The Role Hierarchy (Option C) provides vertical access but doesn't easily handle the horizontal, project-based access required for support reps and engineers working on specific accounts62. Permission Sets (Option D) grant functional permissions (what a user can do) but do not grant access to specific data records in a collaborative way63.
NEW QUESTION # 108
Cloud Kicks has an administrator team that manages the org. The company has asked for a small subset of leadership users to have Modify All access, like the administrators have. How should the administrator team accomplish this?
- A. Assign the standard Platform User profile to the leadership users and edit the permissions to Modify All access.
- B. Assign the standard System Administrator profile to the leadership users that includes the Modify All access.
- C. Assign the standard User profile to the leadership users and add a custom permission set with Modify All access.
- D. Clone the standard User profile to the leadership users and assign a Modify All role to grant access.
Answer: C
Explanation:
Salesforce best practices dictate the Principle of Least Privilege, which means users should only be given the minimum level of access required to do their jobs. Assigning leadership users the
"System Administrator" profile (Option B) is dangerous because it grants them the ability to change the system configuration, delete fields, and manage users. Instead, the administrator should keep the leadership users on their standard functional profile and grant the "Modify All Data" permission via a Permission Set. This approach provides the users with the data visibility they need the ability to view and edit all records across the org) without giving them administrative control over the backend setup. Option A is incorrect because you cannot edit standard profiles directly. Option D is incorrect because "Roles" control record visibility and hierarchy, but they do not grant administrative permissions like "Modify All Data." Using a Permission Set is the most secure and flexible way to elevate data access for a specific group.
NEW QUESTION # 109
Cloud Kicks has hired a new sales executive who wants to implement a document merge solution in Salesforce. How should a Platform Administrator implement this solution?
- A. Download the solution from AppExchange.
- B. Install a package from the Partner Portal.
- C. Configure the package from Salesforce Setup.
- D. Create a managed package in AppExchange.
Answer: A
Explanation:
Salesforce does not provide a robust, native "document merge" engine that can handle complex templates, headers, and advanced formatting out of the box. Therefore, the standard practice for implementing such a solution is to download a third-party application from the AppExchange. The AppExchange is the primary marketplace for Salesforce-integrated solutions, offering popular document generation tools like Conga Composer, Nintex DocGen, or S-Docs. These tools allow administrators to create professional-grade documents (like quotes, contracts, and invoices) by merging Salesforce record data into Word, PDF, or Excel templates. As a Platform Administrator, the process involves researching the best-fit app for the requirements, installing the package into a Sandbox for testing, and then deploying it to Production. This approach is highly efficient because it leverages existing, vetted technology that is specifically designed to handle the complexities of document generation, saving the organization from trying to build a costly and difficult-to-maintain custom solution using code or complex automation.
NEW QUESTION # 110
The administrator at Universal Containers is creating a flow with several steps. How can the administrator check their work as they are developing the flow?
- A. Use debug logs in the Developer Console
- B. Use debug logs found in Setup
- C. Use the Debug tool in the flow builder
- D. Perform the same steps manually via the UI
Answer: C
NEW QUESTION # 111
Which two actions should a Platform Administrator perform with Case escalation rules?
- A. Reopen the Case.
- B. Change the Case Priority.
- C. Send email notifications.
- D. Reassign the Case.
Answer: C,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). 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 attention.
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 interface. Escalation rules focus specifically on the routing and notification aspects of case management to prevent tickets from "sitting" too long without a response.
NEW QUESTION # 112
......
Salesforce Plat-Admn-201 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
Plat-Admn-201 dumps Exam Material with 160 Questions: https://torrentvce.pass4guide.com/Plat-Admn-201-dumps-questions.html