Free Salesforce ADM-201 Practice Exam with Questions & Answers | Set: 2

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.

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.

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.

In Salesforce, a flow must be Active for it to execute in a production environment. When an administrator builds or updates a flow, it is saved as a new version. Even if the logic is perfect and passes all debug tests, the flow will not run for end-users unless the administrator explicitly clicks the " Activate " button. If a flow is intended to create records but nothing is happening, the first troubleshooting step is always to verify the status in the Flow Builder or the Flows list in Setup. A flow version that is simply " Saved " but not " Active " will remain dormant. Option D is unlikely because the Flow Builder usually prevents saving a record-triggered flow without a trigger defined. Option C ( " Read Only " ) is not a state that would prevent a flow from running. Option B ( " Flow URL " ) only applies to specific types of screen flows launched via custom links, whereas the question implies a general failure of the automation to execute.

To ensure a consistent, weekly " check-in " occurs, the Platform Administrator should enable the creation of recurring tasks. This feature allows a sales rep to create a single task (e.g., " Monday Check-in " ) and set a recurring frequency of " Weekly " on " Mondays. " Salesforce then automatically generates the next task in the series once the current one is completed. This is the most effective way to provide reps with a constant reminder in their task list. Additionally, because these are standard Task records, the administrator can easily build a report and a dashboard component to track the completion status of these check-ins for the VP. Time-based workflow (Option A) is typically for one-off alerts based on a date field, not for a permanent weekly habit. Email actions (Option C) and alerts (Option D) notify users but do not create the trackable task record required for the dashboard component.

In Salesforce, a many-to-many relationship allows each record of one object to be linked to multiple records of another object and vice versa. This is achieved by using a Junction Object. A junction object is a custom object that sits between the two objects you want to relate. To implement this correctly, the administrator must follow two specific steps: first, create the custom object to serve as the " junction " ; second, create two Master-Detail relationship fields on that new junction object. One master-detail field points to the first custom object, and the second points to the other. Because these are master-detail relationships, the junction record ' s visibility and deletion behavior are controlled by its parents. This structure allows for powerful reporting and roll-up summaries on both parent objects. Using simple lookup relationships (Option D) would not enforce the strict data integrity or the specific roll-up capabilities that define a true many-to-many relationship in the Salesforce architecture.

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.

To provide reps with an " easy way " to perform a repetitive sequence of manual tasks, Macros are the ideal solution. A Macro allows a user to perform multiple steps—such as changing a Case Status, reassigning the Case Owner, and sending a pre-written email—with a single click. When combined with Quick Actions, Macros can navigate the user interface, populate fields, and submit changes automatically. This significantly reduces manual data entry and ensures that the company ' s required support process is followed consistently. Case Assignment Rules (Option A) and Autolaunched Flows (Option D) are fully automated and trigger on save, which might not be appropriate if the rep needs to decide when to trigger the support request. Quick Text (Option C) only assists with typing but does not automate field changes or ownership transfers.

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.

The Mobile Only app is the default navigation experience in the Salesforce mobile app when no other Lightning apps have been assigned to a user for mobile use64. In this configuration, the navigation menu is controlled globally via the " Salesforce Navigation " setup page6565. A key behavior of this interface is that the first four items placed in the navigation list become the " persistent " icons that appear in the navigation bar at the bottom of the mobile screen for quick access66. These same items also appear at the top of the " Menu " tab67. Option A is incorrect because pages must have a corresponding Tab created before they can be added to the navigation menu68. Option B is incorrect because the " Mobile Only " navigation is a single global setting for the entire org; if you need different menus for different profiles, you must create and deploy specific Lightning Apps69. Option D is incorrect because standard objects do not appear automatically; the administrator must explicitly add them to the navigation list in Setup70. Understanding this behavior is essential for ensuring mobile users have a streamlined and intuitive interface