SalesForce ADM-201 - Questions & Answers

Case Escalation Rulesare 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 delay 63. Reports (Option A) and Dashboards (Option B) provide information but do not physically move records or perform automated reassignments.

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 time 57. The flow can then query all relevant Account records and perform the logic of counting open cases and updating the parent record autonomously 58.
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 edit 59. Autolaunched flows (Option C) must be called by another process, such as a button or Apex, and do not have their own timing mechanism 60.
"Automation event triggered flow" (Option D) is not a standard type of flow used for recurring batch processing

The Activity Timeline is a standard Lightning component that displays open tasks, upcoming events, and past activities (like logged calls or sent emails) in a chronological view. If this timeline is missing from an Account page, it is usually because the component has been removed from the Lightning Record Page layout. To fix this, the Platform Administrator should open the Account record in the Lightning App Builder.
From the list of standard components on the left, the admin must drag the Activities component onto the page canvas-typically in the right-hand column or a dedicated tab. Once the page is saved and activated, the timeline will be visible to users. Visibility of the timeline is a layout configuration, not a specific "Edit access" permission (Option B). Running a report (Option C) might confirm if data exists, but it won't fix the UI issue. There is no "button" for the Activity Timeline in the Object Manager (Option D); it is managed
strictly as a component within the App Builder.

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.

In Salesforce reporting, aBucket Columnis 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.

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.

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 tool 54. 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

A Roll-up Summary Field is a powerful feature that calculates values from related records and displays them on a master record. However, this functionality is natively available only on the "Master" side of a Master-Detail relationship. For standard objects, Salesforce provides a built-in Master-Detail-like relationship between Accounts and Opportunities. Specifically, the Account object acts as the master, and the Opportunity object acts as the detail. This relationship allows a Platform Administrator to create roll-up summary fields on the Account to calculate the sum of "Total Opportunity Amount," the "Minimum Close Date," or a "Count" of all related opportunities. Other standard objects like Contacts (Option B) and Cases (Option C) have a lookup relationship to Accounts rather than a master-detail relationship, and therefore do not support native roll-up summaries 20. Campaigns (Option D) also do not share this specific relationship with Accounts21. If an administrator needs to roll up data from these other objects, they would typically need to use a custom solution like Flow Builder or a third-party app, whereas Opportunities are supported natively out of the box.

When naming actions for an AI agent, consistency is key to helping the Large Language Model (LLM) categorize and understand the available tools. Following a consistent naming convention, such as starting all retrieval actions with the verb "Get," allows the agent to more easily map user intent (e.g., "I need information about...") to the appropriate action. This reduces ambiguity during the reasoning phase of the agentic loop. Using inconsistent verbs like Find, Retrieve, or Identify (Option D) can confuse the model regarding which action is most appropriate for a given task. Removing verbs entirely (Option A) makes it harder for the model to distinguish between an action (doing something) and a data object (a thing).
Adding "Salesforce" (Option B) is generally redundant as the agent's context is already within the Salesforce environment.