Salesforce Updated ADM-201 Exam Questions and Answers by maxim

Salesforce allows Queues to be designated as assigned approvers in an approval process. When a record is submitted for approval and routed to a queue, an email notification is sent to all queue members (depending on queue settings). The core behavior is that any member of the queue can " claim " the request and either approve or reject it. Once one member takes action, the step is considered complete, and the queue is treated as a single decision-making entity. Unanimous approval (Option A) is a specific setting for multiple individual assigned approvers, but it does not apply to queues in this way. Option C is incorrect because the purpose of a queue is to notify all members to ensure a timely response. Queues are supported for most standard and all custom objects (negating Option D).

Creating effective Agentforce prompts requires a focus on clarity and simplicity to ensure the Large Language Model (LLM) follows instructions accurately. According to Salesforce best practices, administrators should use natural, easy-to-understand language and provide clear, concise instructions1919. This approach helps the AI accurately reason through the task without becoming confused by overly complex or nested logic (Option A). While technical accuracy is important, relying heavily on jargon or abbreviations (Option B) can sometimes lead to unexpected results if the LLM interprets those terms differently in various contextsFurthermore, providing high-level theoretical concepts (Option C) often results in vague or " creative " answers that may not be helpful for technical troubleshooting, which requires specific and actionable steps22. Using direct instructions like " Summarize the issue in three bullet points " is more effective than broad guidelines.

In Salesforce, certain dependencies prevent a user record from being deactivated. One of the most common blockers is if the user is the Running User of a Dashboard. Because the dashboard relies on that user ' s security context to display data to others, deactivating them would break the dashboard. To resolve this, the administrator must first change the running user of the dashboard to someone else. Being part of an Opportunity Team (Option C) or Account Team (Option D) does not prevent deactivation; the user simply remains on the team but is inactive. For Assignment Rules (Option B), while you cannot delete a user in a rule, deactivation is usually permitted, though it may result in an error when the rule attempts to assign a record to the inactive user. However, the " Running User " requirement is a hard system block.

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.