Pass the Salesforce Administrator ADM-201 Questions and answers with Dumpstech

Case Assignment Rules are the standard Salesforce tool for automatically routing cases to specific users or queues based on record criteria. A single assignment rule can contain multiple "Rule Entries" processed in a specific order. To meet this requirement, the Platform Administrator would create a rule with two entries: one that checks if the Account's "Level" field equals "Platinum" and routes it to the Priority Support Queue, and another that checks if the level is "Silver" or "Gold" and routes it to the Regular Support Queue. This automation happens the moment the case is created, ensuring that high-value customers receive immediate attention from the appropriate team. Escalation Rules (Option A) are used to move a case after it has been sitting for a period of time, not for initial routing. Workflow Rules (Option D) are a legacy tool that cannot natively assign cases to queues in the same direct manner as Assignment Rules.

Opportunity Contact Roles allow sales reps to link multiple Contacts to a single Opportunity and assign a specific "Role" to each, such as "Decision Maker," "Influencer," or "Economic Buyer." This provides the visibility needed to understand the "buying committee" for a deal. It also allows for the designation of a "Primary Contact." Opportunity Teams (Option A) are used to track internal staff working the deal. Account Teams (Option B) track collaboration at the account level but are not deal-specific. Standard fields (Option C) are insufficient for tracking a "one-to-many" relationship between an opportunity and multiple contacts with unique roles. Contact Roles are the standard feature designed exactly for stakeholder management in the sales process.

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 Mass Transfer Records tool is a built-in Salesforce feature designed specifically for the scenario of a person leaving the company or changing roles. It allows a Platform Administrator to select a "From" user and a "To" user and then choose specific record types to transfer, such as Accounts and Opportunities. A major advantage of this tool is that it gives the administrator the option to transfer related records (like open opportunities or cases) and keep existing teams (like Account Teams) intact during the move. While Data Loader (Option A) or Dataloader.io (Option B) could technically perform a bulk update of the "OwnerId" field, they require several steps, including exporting data, manipulating CSV files, and re-uploading. The Data Import Wizard (Option D) is primarily for creating or updating records from an external file and does not have a dedicated "transfer" function. Mass Transfer is the fastest and safest standard way to reassign ownership within the Setup menu.

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.

When relating two objects where the child records must persist even if the parent record is deleted, a Lookup Relationship is the correct choice18. In this scenario, the Shipment object should have a lookup field pointing to the Account. Unlike a Master-Detail relationship (Option B), which automatically deletes child records (cascade delete) when the master is deleted, a Lookup relationship allows the child record to remain in the system, either by clearing the lookup field or simply leaving it as is. Option A and D are architecturally incorrect because the relationship field is always created on the "child" or "many" side of the relationship (Shipments) to point to the "parent" (Account). Using a Lookup relationship ensures data retention for historical shipment tracking while still allowing the shipment items to be visible via a related list on the Account page.

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 transition users from a standard "tab-based" application to a Lightning Console app, the Platform Administrator must use the App Manager in Setup. The App Manager is where all Lightning apps are created, edited, and assigned to user profiles. Within the App Manager, the admin can create a new app and select "Console Navigation" as the navigation style39. Console apps allow users to work on multiple records simultaneously in a workspace tab-based layout, which is highly effective for productivity in fast-paced environments like sales or support40. The Lightning App Builder (Option A) is used to design the pages within the app, but the app's overall structure and navigation style are defined in the App Manager41. Screen Flow (Option B) and Omni-Channel (Option D) are specialized tools that can be used within a console but do not create the console app itself.

To make a Screen Flow available to users on a specific record, such as a Case, the Platform Administrator should add the Flow component to the Lightning Record Page. Using the Lightning App Builder, the admin can drag the Flow component onto the page and select the specific "Service Question" flow from the list8888. This allows the flow to be embedded directly into the workspace where the service reps are already looking at case details9. While flows can be placed on a Home Page (Option B), that would not provide the case-specific context needed for the reps10. Page Layouts (Option A) are used for standard fields and related lists but do not natively host dynamic screen flow components11. Component Filters (Option D) are used to show or hide the flow based on certain criteria, but the distribution itself is handled by placing it on the Lightning Page12.

To manage a structured, multi-step sign-off requirement like the one described by the finance team, the Approval Process is the standard and most effective tool. An approval process allows an administrator to define a sequence of "Approval Steps." In this scenario, Step 1 would be configured to route the request to the Seller's Manager. Only after the manager approves does the record move to Step 2, which would be configured to route the request to the specific Finance Team member. This ensures the "manager first" logic is strictly enforced. Approval processes also provide a native "Approval History" related list, which serves as a vital audit trail for the finance team to verify that all necessary signatures were obtained before the deal was finalized. Using a screen flow (Option A) or quick actions (Option C) would lack the built-in locking mechanism and formal status tracking that the Approval engine provides. A Lightning Web Component (Option B) would require significant custom coding for a process that is easily handled by standard "click-not-code" configuration.