Free Practice Questions for Salesforce ADM-201 Exam

The Kanban view provides a visual representation of a set of records, such as an opportunity pipeline, organized by a specific field like " Stage " . It allows sales teams to see all their deals as cards in columns. The primary benefit of Kanban is its " drag-and-drop " functionality, which lets users move a card from one column to another to automatically update the stage, effectively " moving opportunities forward " with minimal effort. While reports (Option A) and dashboards (Option B) provide visual summaries, they do not allow for the interactive, one-click record updates that the Kanban view offers11. Standard list views (Option D) show data in a grid format which is less visual for tracking pipeline progress compared to the column-based Kanban layout.

In Salesforce, access to reports and dashboards is determined by the folder in which they are stored. If a dashboard is in a shared folder, anyone with access to that folder can view it. To " temporarily remove " a specific dashboard from public view without affecting the rest of the folder ' s contents, the Platform Administrator should edit the dashboard ' s properties and move it to a private dashboards folder (such as " My Private Dashboards " ). Once moved, only the administrator (and those with high-level " View All Data " permissions) can see it while the changes are being made. Removing view access to the shared folder (Option A) would hide all dashboards in that folder, which is not the goal. Permission sets (Option C) control functional access (the ability to create or edit dashboards) but not individual record/dashboard visibility. Private groups (Option D) are for Chatter collaboration, not for managing dashboard folder security.

Effective Agentforce instructions must be explicit about the data format, the source of the data, and the requirements for the input. Option D is the best choice because it provides the most detail for the Large Language Model (LLM). It specifies the format (18 character ID / three-digit code), the source (conversation history or user input), and the logic/dependency (required only when the product ID is present). This level of detail prevents the agent from guessing or providing incomplete data to the underlying Salesforce action. Options A and C are too vague and could lead to errors. Option B is better but lacks the explicit " Required " tag and format details found in Option D. High-quality instructions act as a contract between the agent ' s natural language understanding and the structured data requirements of the Salesforce system.

The most efficient and descriptive way to troubleshoot a flow is to use the native Debug feature within the Flow Builder. This tool allows the Platform Administrator to " run " the flow in a safe environment, simulating the creation or update of a record. As the flow executes, the Debugger provides a step-by-step panel showing exactly how variables were assigned, which paths were taken in " Decision " elements, and whether any " Update " or " Create " elements failed. It explicitly highlights where an error occurred and provides a detailed error message. While general Debug Logs (Option D) can capture flow information, they are much harder to read and require setting specific trace flags. The Setup Audit Trail (Option A) only shows configuration changes, not runtime errors. Email logs (Option B) are only useful if the flow is failing to send an email. The Flow Debugger is the primary tool for administrators to refine logic and fix issues before activating automation.

A Bucket Column in a Salesforce report allows a user to group multiple field values into larger, more meaningful categories (buckets) without needing to create a new custom field or modify the underlying data. For instance, if a " Industry " picklist has twenty different values like " Banking, " " Insurance, " and " Venture Capital, " a sales rep can create a bucket called " Financial Services " and place all three values inside it. When the report is run, these records are displayed under the " Financial Services " header. This is the ideal solution for ad-hoc reporting needs where the user wants to see data summarized in a way that doesn ' t exactly match the existing picklist structure. Report Filters (Option C) would exclude data rather than categorizing it. Unique Count (Option B) simply tells you how many distinct values exist in a column. Charts (Option D) are for visualization. Bucketing is a powerful, self-service tool for users to reorganize data for analysis.

When a single picklist field needs to show different values to different users or for different business contexts, Record Types are the configuration point. While the master list of all possible values is defined in " Fields and Relationships " (Option D) or a " Global Value Set " (Option C), the Record Type determines which of those values are " available " for a specific type of record. For example, a " Wholesale " record type might show different discount levels than a " Retail " record type. If users are seeing inconsistent or incorrect options, the Platform Administrator must go to the specific Record Type settings for the Opportunity object, find the picklist in question, and move values between the " Available " and " Selected " columns. This provides a tailored user experience and prevents users from selecting values that do not apply to the specific type of record they are managing.

10

When a business needs a specific11, complex functional tool (like a mortgage calculator) on a tight timeline and zero budget, Flow Solutions on the AppExchange are the best resource. Many Flow Solutions are provided for free by Salesforce Labs or other partners. These are pre-built, " installable " flows that an administrator can download and customize. Because they are built using standard Flow Builder logic, they can be easily integrated into a website or Experience Cloud site to capture user input and generate Lead records automatically. Bolt Solutions (Option A) are full industry templates that often require more setup and licensing. Lightning Data (Option C) is for data enrichment, not functional calculators. Flow Solutions empower administrators to deliver complex automation and specialized UI components quickly and cost-effectively.

The Setup Audit Trail is the primary tool for tracking administrative and configuration changes within a Salesforce organization. It records a history of modifications made by any administrator, including the date and time of the change, which user made it, and exactly what was altered (e.g., creating a new field, changing a profile permission, or modifying a workflow rule). The history is available for the last six months of activity. Health Check (Option A) is a security tool that compares your settings against Salesforce standards. History Tracking (Option C) and Feed Tracking (Option D) are used to track changes to records (like an Account ' s phone number), whereas the Setup Audit Trail is dedicated to tracking metadata and system configuration.

Deal Change Highlights is a feature in Lightning Experience that helps sales teams quickly identify recent changes to opportunities. In list views and the Kanban view, changes to the " Amount " or " Close Date " fields are highlighted with green (for positive changes) or red (for negative changes) arrows and text for seven days. This allows reps and managers to visually prioritize deals that have recently shifted in value or timing without having to open each record. Big Deal Alerts (Option A) send emails for high-value deals. Report Filters (Option B) are for general data analysis. The Opportunity Path (Option D) helps guide users through stages but does not highlight recent field-level data changes in a list format.

The Data Import Wizard is the most efficient and user-friendly tool for importing a relatively small number of records (up to 50,000) when those records involve standard objects like Accounts and Contacts simultaneously. A key advantage of this tool is its built-in capability to handle " Account and Contact " imports in a single pass, which includes automatic matching to prevent duplicates based on name or email. For a volume of 300 records, the browser-based wizard is much faster to set up than the Data Loader, as it does not require a separate installation or complex CSV mapping for simple standard objects. While the Data Loader (Option D) and Dataloader.io (Option C) can handle this volume, they are typically preferred for much larger datasets (up to 5 million records) or more complex custom objects. The " Wizard " provides a guided experience that is ideal for sales reps or administrators performing routine data entry tasks.