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

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.

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 categories46. Report Filters (Option B) exclude records47. 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.

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.

To create a "guided" experience combined with "routing and authorizations," a Platform Administrator should leverage the power of Flow Builder and the Approval Process engine. Flow Builder is used to create the user-facing interface (Screen Flow) that guides the employee through the expense report submission, ensuring all necessary data is collected in a structured way. This replaces a static page layout with a dynamic, step-by-step wizard. Once the data is captured and the record is created, the Flow can automatically submit the record into an Approval Process. The Approval Process then handles the "routing and authorizations" by sending the report to the appropriate manager or director for sign-off. While Quick Actions (Option B) can launch flows, they are a entry point rather than the logic engine itself. Validation Rules (Option A) only prevent errors but do not guide users or route records. Together, Flow and Approvals provide a seamless end-to-end automation for complex business requirements like expense management.

In Salesforce, dashboards can be configured to run as a specific user, known as the Running User. This user's security settings determine which data is visible to anyone viewing the dashboard. To allow users with restricted record access (due to a Private sharing model) to see company-wide totals, the Platform Administrator should set the dashboard to "Run as a specified user" who has "View All" permissions or is high enough in the role hierarchy to see all records. This creates a "Static Dashboard." While the viewers cannot click into individual records they don't own, they can see the summarized totals and charts for the entire organization. Using a Dynamic Dashboard or filtering by role (Option B) would still respect individual sharing and hide data. Changing folder settings (Option D) only affects who can open the dashboard, not the data displayed within it.

Generative AI models are inherently probabilistic, meaning they do not produce the exact same output every time, even when given the same input. When a Platform Administrator uses the Prompt Builder to test a template, each "Preview" or "Test" execution initiates a fresh, unique call to the Large Language Model (LLM). Because the LLM considers a range of linguistic possibilities and probabilities for each word it generates, the resulting text will vary slightly (or significantly) with each iteration. This behavior is expected and is a core characteristic of generative AI. To ensure consistent and high-quality results, administrators must refine their instructions to be as specific as possible, narrowing the LLM's range of creative interpretation. Options A, C, and D are incorrect because the Prompt Builder is designed to provide real-time feedback from the actual LLM to help administrators debug and perfect the prompt's logic before it is deployed to end-users or agents.

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.

A common cause of errors in an Approval Process is a breakdown in the "Approver" chain. If an approval step is configured to route to a specific user or a manager who has been deactivated, Salesforce will throw an error when the current step tries to advance. The Platform Administrator should check the "Next Approver" field on the record or the step definition in Setup to ensure the target user is active and has a valid Salesforce license. While field visibility (Options B and C) is important for the user experience, missing field access typically doesn't "error out" the approval engine itself; it just prevents the user from seeing the data. Checking for inactive users is the first step in troubleshooting runtime errors in automated routing processes.

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.

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.