Last Updated On : 18-Nov-2026


Salesforce Agentforce Specialist - AI-201 Practice Test

Prepare with our free Salesforce Agentforce Specialist - AI-201 sample questions and pass with confidence. Our Agentforce-Specialist practice test is designed to help you succeed on exam day.

380 Questions
Salesforce 2026

Data 360 Fundamentals

Cloud Kicks uses a third-party agent for research and an Agentforce agent for customer service. Which purpose-built protocol allows cross-vendor agents to communicate?

A. Model Context Protocol (MCP)

B. Application Programming Interface (API)

C. Agent-to-Agent (A2A)

C.   Agent-to-Agent (A2A)

Explanation:

The Agent-to-Agent (A2A) protocol is designed to allow AI agents built by different vendors or frameworks to communicate, collaborate, and coordinate tasks with one another.

In this scenario, Cloud Kicks uses a third-party research agent and an Agentforce customer service agent. A2A enables these cross-vendor agents to exchange information and work together, even when they are built on different platforms.

Why the Other Options Are Incorrect:

Model Context Protocol (MCP): Primarily standardizes how AI applications and agents connect to external tools, data sources, and APIs.

Application Programming Interface (API): Enables software systems to exchange data and functionality, but it is not the specific purpose-built protocol for cross-vendor agent collaboration.

References:

Salesforce: Agent-to-Agent (A2A) Protocol — Explains how agents from different platforms discover, communicate, and collaborate.

Salesforce Architects: Agentic Integration Patterns — Explains when to use A2A for cross-agent delegation versus MCP for external tool integration.

Amid their busy schedules, sales reps at Universal Containers dedicate time to follow up with prospects and existing clients via email regarding renewals or new deals. They spend many hours throughout the week reviewing past communications and details about their customers before performing their outreach. Which standard Agent action helps sales reps draft personalized emails to prospects by generating text based on previous successful communications?

A. Agent Action: Summarize Record

B. Agent Action: Find Similar Opportunities

C. Agent Action: Draft or Revise Sales Email

C.   Agent Action: Draft or Revise Sales Email

Universal Containers is testing an agent with a “Reset Password” action restricted by the guard available when @variables.isVerified == True. During a single conversation turn, the large language model successfully sets the isVerified flag to true using @utils.setVariables, but fails to invoke the “Reset Password” action immediately afterward. What must the Agentforce Specialist consider regarding how the reasoning engine evaluates action availability?

A. The action is available from the start; the reasoning engine’s intent to solve the user’s issue automatically overrides the available when guard.

B. The action becomes available immediately; available when conditions dynamically reevaluate after every variable change within a single turn.

C. The action remains unavailable for that turn; available when conditions control action visibility to the LLM and evaluate before the reasoning cycle begins, so the action will not be callable until the next turn.

C.   The action remains unavailable for that turn; available when conditions control action visibility to the LLM and evaluate before the reasoning cycle begins, so the action will not be callable until the next turn.

Explanation:

Why C is correct:
This question tests a critical nuance in how the Atlas Reasoning Engine evaluates guard conditions and action availability within a single conversational turn. The execution order is:

Before each reasoning cycle begins, the system evaluates all available when guard conditions based on the current state of variables at that moment.

The system then presents the list of available actions to the LLM for that turn.

The LLM reasons and decides which action (if any) to invoke.

The action executes, and variables are updated (e.g., via @utils.setVariables).

Crucially, the available when conditions are NOT re-evaluated mid-turn.

In this scenario:

At the start of the turn, @variables.isVerified was false (or not yet set to true).

The guard condition @variables.isVerified == True was evaluated before the reasoning cycle began, so the "Reset Password" action was not included in the list of available actions for the LLM to choose from.

The LLM then used @utils.setVariables to set isVerified = True as part of its reasoning or as a side effect of another action.

However, because the "Reset Password" action was already excluded from the available actions for that turn, the LLM cannot invoke it—even though the variable is now true. The LLM cannot call an action that wasn't presented to it.

The action will only become available in the next turn, after the system re-evaluates the guard condition with the updated variable state at the start of the next reasoning cycle.

Why A is incorrect:
The reasoning engine does not override guard conditions. Guard conditions are deterministic and strictly enforced. The LLM cannot "auto-override" them based on intent. If the guard evaluates to false, the action is simply not visible to the LLM, regardless of the user's intent.

Why B is incorrect:
Available when conditions do not dynamically re-evaluate after every variable change within a single turn. They are evaluated once per turn, at the beginning of the reasoning cycle. Mid-turn variable updates (via @utils.setVariables) do not trigger a re-evaluation of action visibility until the next turn.

References:
Salesforce Official Documentation: "Agentforce Guard Conditions and Evaluation Timing" – explains that available when conditions are evaluated at the start of each reasoning cycle and are not re-evaluated mid-turn, even if variables change during the turn.

Trailhead Module: "Build Agentforce Agents with Agent Builder" > Unit: "Control Action Availability with Guard Conditions" – describes the turn-by-turn evaluation cycle and emphasizes that actions must be available at the beginning of the turn for the LLM to invoke them.

An Agentforce Specialist is evaluating an agent conversation. What is the reason why intents and session metrics within Observability are important to consider?

A. To evaluate the agent’s overall performance

B. To evaluate why the agent was unable to answer a user’s question

C. To evaluate the deflection rate of the agent

A.   To evaluate the agent’s overall performance

Explanation:

The question addresses the strategic value of tracking intents and session-level telemetry within the Agentforce Observability dashboard.

The importance of these metrics is explained below:

Intents and session metrics provide a macro-level, holistic view of how effectively the agent is functioning across all customer interactions.

By tracking these core metrics, administrators can measure key performance indicators (KPIs) such as containment rates, transaction times, step-by-step reasoning accuracy, and tool classification success. This allows organizations to evaluate the agent's overall performance and operational health over time.

While macro analysis helps surface specific drop-offs or failures, those are individual subsets of the broader goal: ensuring the agent as a whole meets business standards.

Why the Other Options Are Incorrect
B. ❌ To evaluate why the agent was unable to answer a user’s question
Pinpointing exactly why a specific question failed requires looking into micro-level conversational details, transcript traces, and LLM reasoning logs of a single session, rather than evaluating aggregate session metrics and overall intent distributions.

C. ❌ To evaluate the deflection rate of the agent
While deflection rate is an important metric, it is only one data point calculated from session outcomes (e.g., whether a session escalated to a human agent). Intent and session metrics cover a broader scope, including action execution accuracy, topic classification quality, and overall task completion efficiency.

Reference
Salesforce Agentforce Management and Analytics Guide: Monitoring Overall Agent Performance with Observability. Use session metrics and intent matching distributions to track agent health, system throughput, and operational trends across the organization.

Exam Tip
When a question asks about the primary objective of high-level dashboard features like intent structures and session tracking:

Look for answers that describe overall or end-to-end agent performance rather than narrow metrics (like deflection) or isolated debugging use cases.

A customer is authenticated and identified as being either bronze, silver, or gold membership level. Those levels define which subagents or actions are available to the agent to perform specific tasks as per the level-based entitlements. What is the best way to ensure the agent responds appropriately?

A. Use before reasoning to set custom variables that will be used in filters and flow logic.

B. Use after reasoning to set custom variables that will be used in filters and flow logic.

C. Use Agent Router to set custom variables that will be used in filters and flow logic.

A.   Use before reasoning to set custom variables that will be used in filters and flow logic.

Explanation:

"Before reasoning" logic executes prior to the LLM's reasoning step in the agent's processing cycle. This is the correct place to set custom variables (such as the customer's membership level — bronze, silver, or gold) because:

The variable needs to be established and available before the agent reasons about which topics, subagents, or actions it should consider or expose for the interaction.

Since entitlements (which subagents or actions are available) depend on this membership level, the value must be determined and injected into context before the LLM starts reasoning — so the reasoning process itself can correctly filter or scope what's available based on that variable.

This ensures filters and flow logic downstream (e.g., action visibility, subagent routing conditions) have the correct membership-level value to reference from the very start of the reasoning cycle, ensuring accurate and consistent entitlement enforcement.

Why the Other Options Are Incorrect
B. ❌ Use after reasoning
Setting the variable after reasoning means the LLM would have already reasoned about and potentially selected topics, actions, or subagents without knowing the customer's membership level. This defeats the purpose, since entitlement filtering must influence what the agent considers during reasoning, not after decisions are already made.

C. ❌ Use Agent Router
Agent Router is responsible for routing conversations to the appropriate agent (e.g., determining which top-level agent should handle an interaction), not for setting custom session or context variables used in downstream filters or flow logic within a single agent's topics or actions. It operates at a different architectural layer than variable-setting for entitlement logic.

Reference
Salesforce Agentforce documentation — "Before Reasoning and After Reasoning in Agent Configuration" (setting context variables before reasoning to influence topic, action, and subagent availability based on business logic such as entitlements).

Page 1 out of 76 Pages