Agentforce-Specialist Salesforce Certified Agentforce Specialist (AI-201) Spring 26 Update Free Practice Exam Questions (2026 Updated)

The correct answer is B because Agent Script is built for hybrid reasoning: flexible LLM-driven conversation plus deterministic procedural control. Declarative prompt text gives the model guidance and conversational flexibility, but it does not guarantee that steps happen in an exact order. Procedural instructions are used when business-critical logic must execute reliably, such as identity verification before a credit check. Salesforce’s Agent Script fundamentals describe the - > arrow as the signal for procedural logic and explain that conditionals, running actions, and setting variables belong in that deterministic logic path. The same guidance distinguishes procedural logic from prompt text assembled for the LLM. Option A is wrong because procedural instructions can run actions that connect to Flows, Apex, or APIs. Option C is a tooling distraction, not a reasoning-pattern distinction.

The AgentForce Testing Center Guide specifies that all testing activity—including prompt tests, structured batch runs, and evaluation sessions—consumes AI credits, which can be monitored directly through the Testing Center interface. The documentation states: “Testing Center provides visibility into testing performance, outcomes, and credit usage. Administrators can view test credit consumption metrics to understand resource utilization across agents and environments.”

Agentforce Analytics (Option A) provides insights into performance, engagement, and operational metrics but does not directly track credit consumption tied to testing. Digital Wallet (Option B) manages AI credit balances across orgs but does not offer test-specific tracking. Therefore, Testing Center is the correct answer since it explicitly supports monitoring credit usage during agent testing activities.

References (AgentForce Documents / Study Guide):

AgentForce Testing Center Guide: “Monitoring Credit Consumption During Testing”

AgentForce Admin Handbook: “Tracking Usage and Test Costs”

AgentForce Study Guide: “Testing Resource Visibility and Credit Management”

The key reason for implementing Agent is its ability to streamline workflows and automate repetitive tasks. By leveraging AI, Agent can assist users in handling mundane, repetitive processes, such as automatically generating insights, completing actions, and guiding users through complex processes, all of which significantly improve operational efficiency.

Option A (Improving data entry and cleansing) is not the primary purpose of Agent, as its focus is on guiding and assisting users through workflows.

Option B (Allowing AI to perform tasks without user interaction) does not accurately describe the role of Agent, which operates interactively to assist users in real time.

Salesforce Agentforce Specialist References:

More details can be found in the Salesforce documentation: https://help.salesforce.com/s/articleView?id=sf.einstein_copilot_overview.htm

When refining Agent custom action instructions, it is considered best practice to provide examples of user messages that are expected to trigger the action. This helps ensure that the custom action understands a variety of user inputs and can effectively respond to the intent behind the messages.

Option B (consistent phrases) can improve clarity but does not directly refine the triggering logic.

Option C (specifying a persona) is not as crucial as giving examples that illustrate how users will interact with the custom action.

For more details, refer to Salesforce ' s Agent documentation on building and refining custom actions.

For no-code implementations, Prompt Builder allows Agentforce Specialists to create prompt templates that dynamically ground responses in Salesforce CRM data (e.g., past purchases) and Data Cloud insights (e.g., product interests) without custom coding. The standard foundation model (e.g., Einstein GPT) can synthesize this data into summaries, leveraging structured and unstructured sources (e.g., email/phone transcripts). Fine-tuning (B) or custom models (C) require code and are unnecessary here, as the use case does not involve unique data patterns requiring model retraining.

When configuring a custom prompt template to use related lists, the Agentforce Specialist must be aware of the maximum number of related list merge fields that can be included. Salesforce enforces limits to ensure prompt templates perform efficiently and do not overload the system with too much data. As a best practice, it ' s important to monitor and optimize the number of merge fields used.

Option B is correct because there is a limit on how many related list merge fields can be included in a prompt template.

Option A (text encoding) and Option C (XML/JSON rendering) are not key considerations in this context.

Salesforce Prompt Builder Documentation: https://help.salesforce.com/s/articleView?id=sf.prompt_builder.htm

Why is " Verify the retriever ' s filter criteria and data source connection " the correct answer?

If agent answers are not satisfactory when using PDF files as a knowledge source, the issue is likely caused by:

Retriever misconfiguration

If filters are too broad or too restrictive, AI may fail to find relevant information.

Checking filter logic and retrieval scope helps improve accuracy.

Incorrect data source connection

If the retriever is not properly linked to the PDF storage location, it may fail to retrieve relevant information.

Ensuring a stable connection between Salesforce Data Cloud and the retriever prevents retrieval failures.

Parsing Issues with PDF Files

If PDFs are not properly indexed, AI may struggle to extract relevant content.

Ensuring structured document formatting improves AI comprehension.

Why Not the Other Options?

❌ A. Analyze the data mapping between source fields and Data Cloud object fields.

Incorrect because data mapping issues primarily affect structured CRM data, not PDF-based knowledge sources.

The issue likely stems from retrieval settings, not field mapping.

❌ B. Check that the agent has the PDF file field permission access for the data library.

Incorrect because permission access issues would prevent AI from accessing PDFs entirely rather than causing poor response quality.

AI can still generate responses, even if they are inaccurate, which means the issue lies in retriever settings, not permissions.

Agentforce Specialist References

Salesforce AI Specialist Material details how retriever filters and data sources impact AI-generated answers​.

Salesforce Certification Guide mentions the importance of verifying retriever configurations for accurate knowledge retrieval​.

In this scenario, Universal Containers wants to bring data from unified Data Cloud objects into prompt templates, and the best way to do that is through a Data Cloud-triggered flow. This type of flow is specifically designed to trigger actions based on data changes within Salesforce Data Cloud objects.

Data Cloud-triggered flows can listen for changes in the unified data model and automatically bring relevant data into the system, making it available for prompt templates. This ensures that the data is both real-time and up-to-date when used in generative AI contexts.

For more detailed guidance, refer to Salesforce documentation on Data Cloud-triggered flows and Data Cloud integrations with generative AI solutions.

In the AgentForce Architecture and Reasoning Engine Overview, Salesforce explains that the large language model (LLM) drives topic and action selection. The documentation states: “AgentForce uses an LLM to interpret user intent, map it to existing topics, and trigger the appropriate action when available. If no matching topic or action is found, the LLM attempts to generate a direct response using its available context.”

This design ensures dynamic adaptability—the agent can choose the correct topic and associated action based on natural language understanding. Option A is incorrect because topic-to-utterance mapping is a configuration aid, not the selection mechanism. Option C is incorrect because the reasoning engine does not select actions by name—it interprets user intent via the LLM and executes mapped actions if relevant.

Therefore, Option B reflects the official operational flow of AgentForce’s LLM-driven reasoning process.

References (AgentForce Documents / Study Guide):

AgentForce Reasoning Engine Overview

AgentForce Builder User Guide: “Topic, Action, and LLM Selection Flow”

AgentForce Study Guide: “How the LLM Chooses Topics and Executes Actions”

According to the AgentForce for Service Configuration Guide, when implementing Service Agents on Email, administrators must create an Email Configuration to connect the agent with the appropriate email channel and templates. The documentation specifies: “To enable Service Agents to handle emails, create an Email Configuration that links the agent to the email address, template, and routing parameters. This configuration allows the Service Agent to read, interpret, and respond using the defined template.”

Option B (creating an Omni-Channel flow) applies to routing live messages or chats, not configuring email agents.

Option C is incorrect because Service Agents do not automatically connect to email templates — a manual configuration is required.

Thus, Option A is correct as it aligns with Salesforce’s documented process for connecting email templates to AgentForce Service Agents.

References (AgentForce Documents / Study Guide):

AgentForce for Service Setup Guide: “Creating Email Configurations for Service Agents”

Salesforce Service Cloud Email Configuration Overview

AgentForce Study Guide: “Deploying Service Agents on Email Channels”

To address security compliance concerns and provide visibility into the prompt text sent to the LLM, how it is masked, and the masked response, the Agentforce Specialist should recommend enabling the audit trail in the Einstein Trust Layer. This feature captures and logs the prompts sent to the large language model (LLM) along with the masking of sensitive information and the AI ' s response. This audit trail ensures full transparency and compliance with security requirements.

Option A (Einstein Shield Event logs) is focused on system events rather than specific AI prompt data.

Option B (debug logs) would not provide the necessary insight into AI prompt masking or responses.

For further details, refer to Salesforce ' s Einstein Trust Layer documentation about auditing and security measures.

The AgentForce Developer Integration Guide specifies that Flex prompt templates are the correct type for custom or embedded integrations, such as invoking a prompt from a Lightning Web Component (LWC).

Flex templates are designed for general-purpose use cases and can be called programmatically via Apex, Flow, or LWC APIs. They offer flexible input and output structures, allowing developers to integrate AgentForce reasoning into custom applications and UI components.

Option A, Field Generation, is used to populate or update Salesforce fields, not for external invocation. Option B, Sales Email, is specific to generating pre-formatted communication messages and cannot be invoked directly from LWCs.

Therefore, the correct template type for a prompt used within a Lightning Web Component is Option C – Flex, as it is purpose-built for dynamic, reusable, and programmatic use cases.

In Salesforce Data Cloud, a custom search index is created to enable efficient retrieval of data (e.g., documents, records) for AI-driven processes, such as grounding Agentforce responses. Let’s evaluate the options based on Data Cloud’s functionality.

Option A: A retriever that shares the name of the custom search index.When a custom search index is created in Data Cloud, a corresponding retriever is automatically generated with the same name as the index. This retriever leverages the index to perform contextual searches (e.g., vector-based lookups) and fetch relevant data for AI applications, such as Agentforce prompt templates. The retriever is tied to the indexed data and is ready to use without additional configuration, aligning with Data Cloud’s streamlined approach to AI integration. This is explicitly documented in Salesforce resources and is the correct answer.

Option B: A dynamic retriever to allow runtime selection of retriever parameters without manual configuration.While dynamic behavior sounds appealing, there’s no concept of a " dynamic retriever " in Data Cloud that adjusts parameters at runtime without configuration. Retrievers are tied to specific indexes and operate based on predefined settings established during index creation. This option is not supported by official documentation and is incorrect.

Option C: A predefined Apex retriever class that can be edited by a developer to meet specific needs.Data Cloud does not generate Apex classes for retrievers. Retrievers are managed within the Data Cloud platform as part of its native AI retrieval system, not as customizable Apex code. While developers can extend functionality via Apex for other purposes, this is not an automatic outcome of creating a search index, making this option incorrect.

Why Option A is Correct:

The automatic creation of a retriever named after the custom search index is a core feature of Data Cloud’s search and retrieval system. It ensures seamless integration with AI tools like Agentforce by providing a ready-to-use mechanism for data retrieval, as confirmed in official documentation.

The correct answer is C because Agent-to-Agent protocol is designed for interoperability between agents across different platforms, vendors, or systems. In this scenario, Agentforce must collaborate with a third-party warehouse logistics agent to request shipping reroutes. That is cross-agent collaboration, not just tool access or data retrieval. Model Context Protocol is more appropriate when an agent needs standardized access to tools, resources, or external context. Advanced Data Retrieval is not the relevant open standard for autonomous cross-platform agent collaboration. A2A provides the pattern for agents to discover, communicate, coordinate tasks, and delegate work securely across system boundaries. Salesforce’s Agentforce interoperability guidance explicitly separates MCP-style tool/context access from A2A-style agent collaboration.

When creating a custom action in Agent, one of the available options is to use Flows. Flows are a powerful automation tool in Salesforce, allowing the Agentforce Specialist to define custom logic and actions within the Copilot system. This makes it easy to extend Copilot ' s functionality without needing custom code.

While Apex triggers and SOQL are important Salesforce tools, Flows are the recommended method for creating custom actions within Agent because they are declarative and highly adaptable.

For further guidance, refer to Salesforce Flow documentation and Agent customization resources.

The correct answer is B because Zero Copy Data Federation is designed for accessing external data without physically copying or ingesting that data into Data 360. This fits the requirement exactly: the data remains in the external system, storage duplication is avoided, and Salesforce can still use the connected data for Data 360-driven use cases. Option A is wrong because a semantic index supports meaning-based retrieval over indexed content, but it does not by itself solve the requirement to avoid duplication of structured external data. Option C is wrong because configuring a data stream imports or ingests data into Data 360, which contradicts the storage-cost and no-duplication requirement. Salesforce’s Zero Copy guidance states that external data can be accessed and used in Data 360 without duplicating it.

Agentforce Sales Agent provides real-time insights and AI-powered recommendations, which are designed to streamline the sales process and help sales representatives focus on key tasks to increase conversion rates. It offers features like lead scoring, opportunity prioritization, and proactive recommendations, ensuring that sales teams can interact with customers efficiently and close deals faster.

Option A: While tracking customer interactions is beneficial, it is only part of the broader capabilities offered by Agentforce Sales Agent and is not the primary objective for improving real-time productivity.

Option B: Agentforce Sales Agent does not automate the entire sales process but provides actionable recommendations to assist the sales team.

Option C: This aligns with the tool ' s core purpose of enhancing productivity and driving sales success.

Context of the Question

Universal Containers (UC) has a strict change management process that requires all possible configuration be completed in a sandbox and deployed to Production.

Einstein Generative AI is already enabled in Production, and the “Einstein Work Summaries” permission set is already available in Production.

The Agentforce Specialist needs to configure Work Summaries for Enhanced Messaging in the sandbox.

What Can Actually Be Deployed from Sandbox to Production?

Custom Fields: Metadata that is easily created in sandbox and then deployed.

Quick Actions: Also metadata-based and can be deployed from sandbox to production.

Layout Components: Page layout changes (such as adding the Wrap Up component) can be added to a change set or deployment package.

Why Option C is Correct

No Need to Turn on Einstein in Sandbox for Deployment: Einstein Generative AI is already enabled in Production; turning it on in the sandbox is typically a manual step if you want to test, but that step itself is not “deployable” in the sense of metadata.

Permission Set Assignments (as in Option A) are not deployable metadata. You can deploy the Permission Set itself but not the specific user assignments. Since the question specifically asks “Which other configuration steps should be taken in the sandbox that can be deployed to the production org?”, user assignment is not one of them.

Why Not Option A or B?

Option A: Mentions creating permission set assignments for agents. This cannot be directly deployed from sandbox to Production, as permission set assignments are user-specific and considered “data,” not metadata.

Option B: Mentions “Turn on Einstein.” But Einstein Generative AI is already enabled in Production. Additionally, “Turning on Einstein” is typically an org-level setting, not a deployable metadata item.

ConclusionThe main deployable items you can reliably create and test in a sandbox, and then migrate to Production, are:

Custom Fields (Issue, Resolution, Summary).

A Quick Action that updates those fields.

Page Layout Change to include the Wrap Up component.

Therefore, Option C is correct and focuses on actions that are truly deployable as metadata from a sandbox to Production.

Salesforce Agentforce Specialist References & Documents

Salesforce Trailhead: Work Summaries with Einstein GPTProvides an overview of how to configure Work Summaries, including the need for custom fields, quick actions, and UI components.

Salesforce Documentation: Deploying Metadata Between OrgsExplains what can and cannot be deployed via change sets (e.g., custom fields, page layouts, quick actions vs. user permission set assignments).

Salesforce Agentforce Specialist Study GuideOutlines which Einstein Generative AI and Work Summaries configurations are deployable as metadata.

Per the AgentForce Testing Center Operations Guide, the batch testing feature allows organizations to upload structured CSV test templates containing real-world user utterances, expected classifications, and desired outcomes. Once uploaded, these test cases are executed in bulk within the Testing Center to validate agent accuracy, reasoning consistency, and grounding before activation.

This structured approach supports repeatable, scalable testing and ensures objective evaluation across multiple topics and scenarios.

Option B (manual testing) is suitable for early prototyping but not scalable or auditable. Option C (relying on pilot feedback) occurs post-deployment and risks exposing users to unverified behavior.

Therefore, the recommended approach is Option A – Upload a structured CSV test template and run batch test cases in Testing Center.