ADM-201 domain - 8% of the exam

Agentforce

Agentforce is 8% of the ADM-201 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

24
Practice questions
2
Objectives
24
Medium

Where people go wrong

  • Routing by anything but the topic description

    The wrong answers name the wrong mechanism for choosing a topic: the order topics were created, a literal keyword match on action labels, org-wide defaults, or assignment rules. The reasoning engine instead compares the request with each topic's classification description. When two topics overlap, such as Billing Enquiries and Outage Reports, the first fix is sharper descriptions and scope instructions, not extra actions or merging the topics.

    See it in a sample question
  • Picking a neighbouring prompt template type

    Every wrong option in these questions is a template type that also reads record data, so each looks close. Each type has its own job. Record Summary condenses one record's fields into a summary. Field Generation drafts a value for a single field that the user can accept. Sales Email composes an outbound email from the record. Flex is the general-purpose type, which could be built to do these jobs but is not the one designed for them.

    See it in a sample question
  • Giving an agent a capability without an action

    The wrong answers offer a validation rule, a page layout, a report folder, a prompt template or a topic instruction as the way to give an agent a capability. None of these performs work: validation rules only gate a save, page layouts arrange fields, a Record Summary template only generates text, and an instruction cannot make the agent take an action it has not been given. The right build is an autolaunched flow exposed as a custom action and assigned to the topic that handles the job.

    See it in a sample question
  • Treating a greeting or a setting as grounding

    Generic or invented answers get blamed on the wrong lever: a welcome message, a session timeout, a higher creativity setting, a worked example, or required fields. None of these feeds company data into the response. Grounding does: an Agentforce Data Library that indexes Knowledge articles, connected policy content, or merge fields in a prompt template that resolve to the record's current values at run time.

    See it in a sample question
  • Using debug logs where testing or analytics belong

    The wrong answers reach for Debug Logs, flow debug logs, or the setup audit trail to check an agent. Debug Logs capture low-level execution detail and a flow debug log shows only what one action did, so neither shows whether the agent chose the right topic. Pre-launch checks use sample utterances in Testing Center or the conversation preview. Outcomes and escalations after launch come from Agentforce analytics.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free sampleAgentforcemedium

When a user sends a request to an Agentforce agent, how does the agent decide which set of actions to consider for that request?

  • AIt applies the first matching assignment rule entry and uses the actions linked to that rule.
  • BIt evaluates the requester's place in the role hierarchy and considers only actions owned above that user.
  • CIt runs every action defined in the agent in sequence and keeps whichever result the user accepts.
  • DIt uses the reasoning engine to classify the request against the topic descriptions and selects the matching topic. Correct
An Agentforce agent uses its reasoning engine to classify a request against topic descriptions and then draws on that topic's actions. The agent interprets the user's request with the Atlas Reasoning Engine and matches it to a topic by comparing the request to each topic's classification description, and only the actions belonging to that selected topic are then considered, which is why topic classification, not sharing or routing rules, drives action selection.

Why A is wrong: Assignment rules route records such as cases and leads; they play no part in an agent's reasoning. The first-matching-entry wording is a real concept borrowed from the wrong feature.

Why B is wrong: The role hierarchy governs record sharing, not action selection. It is tempting because hierarchy drives visibility elsewhere, but it does not choose which topic an agent uses.

Why C is wrong: Agents do not brute-force every action; that would be inefficient and unsafe. The idea is plausible to someone unaware of topic classification but misrepresents how reasoning works.

Why D is correct: Correct. The Atlas Reasoning Engine interprets the request, matches it to a topic using the topics' classification descriptions, then works from that topic's available actions.

Free sampleAgentforcemedium

Which prompt template type in Prompt Builder is purpose-built to generate a concise summary grounded in the field values of a single record?

  • ARecord Summary, which is designed to return a short summary built from the fields of the record it is grounded on. Correct
  • BField Generation, which is designed to produce content that populates one specific field on a record when a user requests it.
  • CSales Email, which is designed to draft a personalised outbound email addressed to a related contact or lead.
  • DFlex, which is a freeform template that accepts several inputs and is used when no standard template shape fits the task.
The Record Summary prompt template type is purpose-built to summarise the field values of a single grounded record. Prompt Builder offers several template types for different jobs, and the Record Summary type is the one designed to take a single record's fields as grounding and return a concise, readable summary of that record.

Why A is correct: Record Summary is the template type made specifically to condense a single record's field values into a readable summary.

Why B is wrong: Field Generation does ground on a record, but its job is to fill an individual field, not to return an overall summary of the record.

Why C is wrong: Sales Email grounds on CRM data too, but it produces an email message aimed at a recipient rather than a summary of a record.

Why D is wrong: Flex is the general-purpose option for custom needs; it could be built to summarise, but it is not the type purpose-built for record summaries.

Free sampleAgentforcemedium

At Broome Logistics, an administrator needs to build a custom action for an Agentforce agent that gathers three related records and updates a field when a customer confirms a booking change. The administrator wants to build this new automation with the strategic, declarative tool that Salesforce recommends. Which tool should the administrator use to build the action's logic?

  • AA Flow that performs the record retrieval and update, exposed as an agent action Correct
  • BA Workflow Rule that updates the field when the booking changes
  • CA Process Builder process triggered by the booking change
  • DA validation rule that recalculates the field on save
Flow is the strategic declarative tool for new automation and can be exposed as an Agentforce action. Salesforce positions Flow as the go-to declarative automation tool for new requirements, over legacy Workflow Rules and Process Builder. A flow can retrieve and update records and be made available to an agent as an action, which fits this multi-step requirement without code.

Why A is correct: Flow is the recommended declarative automation tool and can be surfaced as an Agentforce action, making it the correct way to build this multi-step logic without code.

Why B is wrong: Workflow Rules are a legacy automation tool that Salesforce no longer recommends for new work and cannot serve as the logic behind an Agentforce action, so this is the wrong choice.

Why C is wrong: Process Builder is a superseded tool that Salesforce is retiring and is not the recommended path for new automation, so it should not underpin a new agent action.

Why D is wrong: Validation rules only block or allow a save based on a condition and cannot retrieve related records or update fields, so they cannot implement this action's logic.

Free sampleAgentforcemedium

At Esperance Freight, an administrator is building a prompt template that drafts a customer update. Early tests show the model inventing shipment details that are not stored in Salesforce. The administrator wants the generated text to rely only on real data from the related Shipment record. What is the best way to achieve this in Prompt Builder?

  • AIncrease the response creativity setting so the model produces richer, more varied wording.
  • BPaste one fixed example shipment into the prompt as static text for the model to copy.
  • CGround the template by inserting merge fields that pull the Shipment record's data into the prompt. Correct
  • DAdd a validation rule that requires the Shipment fields to be populated before saving.
Ground a prompt template with record merge fields so generated text uses real CRM data rather than invented content. Grounding is how Prompt Builder supplies trustworthy context to the model: merge fields resolve to the current record's values when the prompt runs, anchoring the output in real data and reducing hallucination, which a creativity setting, a static example, or a validation rule cannot do.

Why A is wrong: Raising creativity might seem to improve quality, but it encourages the model to generate more of its own content, which makes invented details more likely, not less.

Why B is wrong: A worked example looks like helpful guidance, but static text does not change per record and still leaves the model free to fabricate values for the actual shipment.

Why C is correct: Grounding a prompt with merge fields injects the actual record values into the prompt at run time, so the model works from real Salesforce data instead of inventing shipment details.

Why D is wrong: Requiring the fields feels related because it guarantees data exists, but it never feeds that data into the prompt and so cannot stop the model inventing details.

Free sampleAgentforcemedium

At Albany Wholesale, an administrator has deployed an Agentforce agent to production and now needs to review how it is performing, including how often conversations reach a successful outcome and where the agent is escalating to humans. Where should the administrator look to monitor the agent's ongoing performance?

  • AThe debug logs generated when Apex classes execute
  • BThe Agentforce analytics and conversation reporting surfaces for the agent Correct
  • CThe setup audit trail that records configuration changes
  • DThe login history report under the user's profile
Administrators monitor a deployed Agentforce agent through its analytics and conversation reporting, not through debug logs or audit trails. Once an agent is live, its behaviour is monitored through Agentforce's built-in analytics and conversation reporting, which surface metrics such as resolution outcomes and escalations to human agents. Debug logs and audit trails serve unrelated technical and governance purposes.

Why A is wrong: Debug logs capture low-level execution detail for troubleshooting code and are not designed to summarise conversation outcomes or escalation trends, so they do not serve ongoing performance monitoring.

Why B is correct: Agentforce provides analytics and reporting on agent conversations, including outcomes and escalations, which is exactly what the administrator needs to monitor performance.

Why C is wrong: The setup audit trail tracks who changed org configuration and when, not how the agent handles conversations, so it cannot show outcome or escalation metrics.

Why D is wrong: Login history shows when users authenticate to the org and reveals nothing about agent conversation quality, so it is irrelevant to monitoring the agent.

Other domains in this exam

See also the ADM-201 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Salesforce. Original, blueprint-aligned practice material only.