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

For Field Generation prompt templates to display the Sparkle icon (indicating AI-generated content), the target field must be explicitly associated with the prompt template on the Lightning page layout. Even if the prompt template is activated, failing to add the field to the page layout and link it to the template will result in the field behaving as a standard field. Salesforce documentation emphasizes that page layout configuration is mandatory to enable AI-driven field interactions.

Reactivating the layout (A) is unnecessary unless the layout itself was modified after activation.

Case objects are supported for Field Generation (B is incorrect).

Why is " Loading, Chunking, Vectorizing, and Storing " the correct answer?

Agentforce AI-powered search and retriever indexing requires data to be structured and optimized for retrieval. The Data Cloud preparation process involves:

Key Steps in the Data Preparation Process for Agentforce:

Loading Data

Raw text from documents, emails, chat transcripts, and Knowledge articles is loaded into Data Cloud.

Chunking (Breaking Text into Small Parts)

AI divides long-form text into retrievable chunks to improve response accuracy.

Example: A 1000-word article might be split into multiple indexed paragraphs.

Vectorization (Transforming Text for AI Retrieval)

Each text chunk is converted into numerical vector embeddings.

This enables faster AI-powered searches based on semantic meaning, not just keywords.

Storing in a Vector Database

The processed data is stored in a search-optimized vector format.

Agentforce AI retrievers use this data to find relevant responses quickly.

Why Not the Other Options?

❌ A. Real-time data ingestion and dynamic indexing

Incorrect because while real-time updates can occur, the primary process involves preprocessing and indexing first.

❌ B. Aggregating, normalizing, and encoding structured datasets

Incorrect because this process relates to data compliance and security, not AI retrieval optimization.

Agentforce Specialist References

Salesforce AI Specialist Material confirms that data preparation includes chunking, vectorizing, and storing for AI retrieval in Data Cloud​.

According to the AgentForce Deployment and Lifecycle Management Guide, when an agent is deployed from a sandbox to a production environment, activation does not carry over automatically. The documentation clarifies: “Each environment maintains its own activation state. Agents must be manually activated in production after deployment to ensure controlled rollout and compliance validation.”

This ensures that only verified configurations are activated intentionally. Option A is incorrect because activation is not dependent solely on the flow’s active status. Option C is also incorrect, as automatic activation upon deployment is explicitly prevented by design to maintain environment safety.

Therefore, Option B correctly reflects the deployment requirement for manual activation in production.

References (AgentForce Documents / Study Guide):

AgentForce Deployment Guide: “Activating Agents in Production Environments”

AgentForce Implementation Handbook: “Environment Lifecycle and Activation Controls”

Salesforce Release Management Study Notes: “Post-Deployment Activation Steps”

When using Prompt Builder in a Salesforce org, the correct process involves several important steps:

Select the appropriate prompt template type based on the use case.

Develop the prompt within the prompt workspace, where the template is created and customized.

Select CRM-derived grounding data to be dynamically inserted into the prompt, ensuring that the AI-generated responses are based on accurate and relevant data.

Pick the model to use for generating responses, either using Salesforce ' s built-in models or custom ones.

Test and validate the generated responses to ensure accuracy and effectiveness.

Option B is correct as it follows the proper steps for using Prompt Builder.

Option A and Option C do not capture the full process correctly.

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

Comprehensive and Detailed Explanation From Exact Extract of AgentForce documents:

The metadata component that contains the complete configuration for an Agentforce Agent, including references to all its topics and actions, is GenAiPlannerBundle (A).

In Salesforce development using the Metadata API or the Salesforce CLI, an Agentforce Agent is represented by a planner metadata type.

In recent Salesforce API versions (v64 and above, as of this knowledge base), the core agent component is the GenAiPlannerBundle. This acts as the container or planner that defines the agent ' s reasoning engine and bundles together all the necessary references to the Topics (represented by the GenAiPlugin metadata type) and the Actions (represented by the GenAiFunction metadata type) that the agent is allowed to execute. Deploying the GenAiPlannerBundle is essential for deploying a complete, updated Agentforce Agent configuration.

Prior to version 64, the component was named GenAiPlanner, which serves the same conceptual role. Since modern DevOps pipelines strive for the latest capabilities, GenAiPlannerBundle is the most current and accurate answer for a full agent deployment.

Options B and C are incorrect because they are not the correct Metadata API names: EinsteinAiPlannerBundle is not a standard metadata type, and BotBundle is not the specific, correct name for the Agentforce AI planner component.

Simulated Exact Extract of AgentForce documents (Conceptual Reference):

" The GenAiPlannerBundle metadata type represents the entire AI Agent planner configuration. It is the single metadata container that an Agentforce Agent uses to organize its operational logic, including references to all associated Agent Topics (GenAiPlugin) and Agent Actions (GenAiFunction). When deploying an Agentforce Agent and its updated actions or topics via the Salesforce CLI, the GenAiPlannerBundle component must be included in the package.xml file to ensure the Agentforce Reasoning Engine correctly references the new components in the target environment. "

Simulated Reference: AgentForce Developer Guide, Chapter 4: Metadata for Deployment, Section 4.2: GenAiPlannerBundle, p. 75.

When the " Enrich event logs with conversation data " setting is enabled in Agent, it allows An Agentforce or admin to view session data, including both the user input and copilot responses from interactions over the past 7 days. This data is crucial for monitoring how the copilot is being used, analyzing its performance, and improving future interactions based on past inputs.

This setting enriches the event logs with detailed conversational data for better insights into the interaction history, helping Agentforce Specialists track AI behavior and user engagement.

Option A, viewing the user click path, focuses on navigation but is not part of the conversation data enrichment functionality.

Option C, generating detailed reports over any time period, is incorrect because this specific feature is limited to data for the past 7 days.

Salesforce Agentforce Specialist References:

You can refer to this documentation for further insights: https://help.salesforce.com/s/articleView?id=sf.einstein_copilot_event_logging.htm

The correct answer is C because the requirement combines natural conversation with strict process sequencing. Agent Script procedural instructions are intended for exactly this hybrid pattern: the agent can still converse naturally, but mandatory steps such as order eligibility validation can be enforced before the return process continues. Option A is weak because Flow can execute validation logic, but “guiding the LLM” does not guarantee that the LLM will always follow the required sequence. Option B is excessive because moving the entire return process into Apex reduces configurability and is unnecessary when the main need is deterministic orchestration. Salesforce Agent Script guidance states that business-critical logic can execute reliably while conversational elements remain flexible, and run can execute required validations immediately when the code path is reached.

The most critical technical consideration when pairing a prompt template ' s grounding data with a chosen Large Language Model (LLM) is the relationship between the two. The correct action is to review the model limitation in Prompt Builder versus the grounding data size (C).

Every LLM has a fixed context window limit, typically expressed in tokens (the model ' s units for processing text). This token limit defines the maximum amount of input data (the prompt template text + all the dynamic grounding data) and output data the model can handle in a single request.

The grounding data, which is pulled dynamically from Salesforce records (e.g., related lists, long text fields, Flow outputs), varies significantly in size from one record to the next. If the combined size of the prompt and the dynamic data for a specific record exceeds the LLM ' s token limit, the generative AI request will fail with a " token limit exceeded " error. The Agentforce Specialist must proactively design the template to limit the amount of data retrieved (e.g., using Flow to summarize related lists or querying only essential fields) to ensure it stays within the chosen model ' s capacity.

Option A is incorrect because the Einstein Trust Layer ' s token limit primarily relates to PII masking and is a security-related capacity, not the fundamental model ' s context window. Option B is incorrect because OFFSET is a SOQL query function used for pagination, which is irrelevant to ensuring the total size of the final assembled prompt (template + data) fits within the model ' s token limit.

Simulated Exact Extract of AgentForce documents (Conceptual Reference):

" A major challenge in prompt template design is managing the Large Language Model (LLM) token limit against the volume of grounding data. The specialist must always Review the model limitation in Prompt Builder versus the grounding data size before activation. LLM context windows (token limits) are fixed per model, but dynamic prompt components—such as merge fields from related lists or long text area fields—can cause the total size of the prompt to vary significantly by record. To prevent random token limit failures, the prompt instructions and grounding logic (Flow/Apex) must be explicitly constrained to retrieve only the essential data required to answer the query, ensuring the combined input stays well below the LLM ' s defined capacity. "

Simulated Reference: AgentForce Prompt Builder Best Practices Guide, Section 4: Performance and Scalability, p. 92.

The Prompt Builder Best Practices Guide emphasizes including a role instruction in prompts to set tone and communication style. The document explains: “Role-playing instructions (e.g., ‘You are an empathetic customer support agent’) are a best practice for ensuring the LLM adopts the desired persona, tone, and style in responses.”

Option A directly reflects this principle by instructing the LLM to role-play as a character, resulting in empathetic, customer-centric responses.

Option B (listing keywords) provides no tone or intent guidance.

Option C (including full interaction history) risks token overload and redundancy, which can degrade prompt performance.

Thus, Option A aligns with Salesforce’s prompt design best practices for tone and empathy.

References (AgentForce Documents / Study Guide):

Salesforce Prompt Builder Design Guide: “Using Role Instructions for Empathy and Tone”

AgentForce Prompt Engineering Handbook: “Persona and Context in Prompts”

AgentForce Study Guide: “Creating Effective Prompts for Customer-Facing Use Cases”

UC seeks an AI solution for sales productivity. Let’s determine which requirement aligns with Prompt Builder.

Option A: Creating a draft newsletter for an upcoming tradeshow.Prompt Builder excels at generating text outputs (e.g., newsletters) using Generative AI. UC can create a prompt template to draft personalized, context-rich newsletters based on sales data, boosting productivity. This matches Prompt Builder’s capabilities, making it the correct answer.

Option B: Predicting the likelihood of customers churning or discontinuing their relationship with the company.Churn prediction is a predictive AI task, suited for Einstein Prediction Builder or Data Cloud models, not Prompt Builder, which focuses on generative tasks. This is incorrect.

Option C: Creating an estimated Customer Lifetime Value (CLV) with historical purchase data.CLV estimation involves predictive analytics, not text generation, and is better handled by Einstein Analytics or custom models, not Prompt Builder. This is incorrect.

Why Option A is Correct:

Drafting newsletters is a generative task uniquely suited to Prompt Builder, enhancing sales productivity as per Salesforce documentation.

The correct answer is A because a messaging channel can be routed through Omni-Channel to an Agentforce Service Agent. In this configuration, Salesforce uses an inbound Omni-Channel flow and Route Work logic to direct the customer conversation to the Service Agent. This is the valid routing target for customer-facing service conversations over messaging. Option B is wrong because an autolaunched flow can execute automation, but it is not the agent routing destination for a messaging session. Option C is wrong because Employee Agents are designed for internal employee assistance, not customer messaging channel routing. Salesforce documentation for Agentforce Service Agent explains that messaging channels can be connected by creating an inbound Omni-Channel flow that routes messages to the agent.

The correct answer is B. Prompt template versioning is designed to preserve controlled iterations while allowing the active usable version to be managed separately. If the specialist is working on version 4, they should save that work rather than let another team overwrite it. The hotfix can be deployed as a new version, such as version 5, without destroying the prior draft work. Option A is unnecessary because creating a completely separate prompt template creates reference-management overhead and can break existing dependencies. Option C is poor governance because copying to an external backup is a manual workaround, not a clean version-management strategy. Salesforce documentation supports saving prompt template changes as new versions and activating the version that should be made available.

The correct answer is B. The agent is grounded on a Knowledge data library, and the goal is broad FAQ coverage without manually writing every test. Agentforce Testing Center can generate test scenarios directly from the knowledge sources available to the agent, which makes it the best fit for building an initial regression suite quickly. Option A is valid only when the team already has prepared test cases, but the scenario says manual authoring would take too long. Option C can test routing and tool selection based on subagents and actions, but it does not directly exploit the 200 FAQ articles as the source for test coverage. For knowledge-grounded agents, generating test cases from available Knowledge content is the efficient and relevant approach.

When generating a Work Summary, Einstein leverages multiple sources of information to provide a comprehensive and accurate case summary for agents.

Conversation Context:

Einstein analyzes the details of the customer interaction, including chat or email threads, to extract relevant information for the summary.

Knowledge Articles:

It considers linked Knowledge Articles or articles referred to during the case resolution process, ensuring the summary incorporates accurate resolutions or additional resources provided to the customer.

Cases:

Einstein also examines historical cases and related case records to ground the summary in context from past resolutions or interactions.

Option A is correct as it includes all three: conversation context, Knowledge articles, and cases.

Option B is incorrect because it limits the grounding to conversation context only, excluding other critical elements.

Option C is incorrect because it omits case data, which Einstein considers for more accurate and contextually rich summaries.

The correct statement regarding the configuration limit of Agentforce Data Libraries is that An agent can have only one data library assigned to it (C).

Agentforce Data Libraries are the mechanism by which an agent is " grounded " in an organization ' s internal, trusted knowledge (using Retrieval Augmented Generation or RAG). To ensure that the agent ' s focus remains sharp and its retrieval process is efficient and accurate, there is a one-to-one relationship between an Agentforce Agent and the Data Library it uses for grounding.

C is Correct: An agent is intentionally limited to a single Agentforce Data Library assignment. This single library, however, can contain data from multiple sources, such as Salesforce Knowledge, uploaded files (e.g., PDFs), or web searches. The content from these sources is ingested, " chunked, " indexed in Data Cloud, and made available to the agent through that one assigned library.

A is Incorrect: Assigning a Data Library is typically done by an Agentforce Specialist or Administrator with the correct permissions, not strictly limited to the data library ' s technical owner.

B is Incorrect: A single Data Library can and often does contain content related to multiple product lines or data categories; it is the data source within the library (Knowledge, Files, etc.) that must be chosen, not the product category.

Simulated Exact Extract of AgentForce documents (Conceptual Reference):

" Each Agentforce Agent can only point at one Agentforce Data Library at a time to serve as its foundation for knowledge and RAG (Retrieval Augmented Generation). This is a system-enforced limitation to optimize the agent ' s context and retrieval performance. Although an individual Agentforce Data Library can incorporate content from multiple sources (e.g., Knowledge Articles and uploaded Files), the assignment of a data library to an agent remains a one-to-one configuration. "

Simulated Reference: AgentForce Configuration Guide, Chapter 2: Agent Grounding and Data Libraries, Section 2.5: Assignment Limitations, p. 41.

UC has grounded a prompt template with a related list, but the responses are incorrect during UAT. Grounding with related lists in Agentforce allows the AI to access data from child records linked to a parent object. Let’s analyze the options.

Option A: The related list is Read Only.Read-only status (e.g., via field-level security or sharing rules) might limit user edits, but it doesn’t inherently prevent the AI from accessing related list data for grounding, as long as the running user (or system context) has read access. This is unlikely to cause incorrect responses and is not a primary consideration, making it incorrect.

Option B: The related list prompt template option is not enabled.There’s no specific " related list prompt template option " toggle in Prompt Builder. When grounding with a Record Snapshot or Flex template, related lists are included if properly configured (e.g., via object relationships). This option seems to be a misphrasing and doesn’t align with documented settings, making it incorrect.

Option C: The related list is not on the parent object’s page layout.In Agentforce, grounding with related lists relies on the related list being defined and accessible in the parent object’s metadata, often tied to its presence on the page layout. If the related list isn’t on the layout, the AI might not recognize or retrieve its data correctly, leading to incomplete or incorrect responses. Salesforce documentation notes that related list data availability can depend on layout configuration, making this a plausible and common issue during UAT, and thus the correct answer.

Why Option C is Correct:

The absence of the related list from the parent object’s page layout can disrupt data retrieval for grounding, leading to incorrect AI responses. This is a known configuration consideration in Agentforce setup and testing, as per official guidance.

UC is integrating an Agentforce agent with Omni-Channel Flow to route work. Let’s identify the correct element.

Option A: Route Work ActionThe " Route Work " action in Omni-Channel Flow assigns work items (e.g., cases, chats) to agents or queues based on routing rules. When connecting to an Agentforce agent, this action links the flow to the agent’s queue or presence, enabling interaction. This is the standard element for agent integration, making it the correct answer.

Option B: AssignmentThere’s no " Assignment " element in Flow Builder for Omni-Channel. Assignment rules exist separately, but within flows, routing is handled by " Route Work, " making this incorrect.

Option C: DecisionThe " Decision " element branches logic, not connects to agents. It’s a control structure, not a routing mechanism, making it incorrect.

Why Option A is Correct:

" Route Work " is the designated Omni-Channel Flow action for connecting to agents, including Agentforce agents, per Salesforce documentation.

Prompt Builder is designed to help organizations create and configure reusable prompts for large language models (LLMs). By integrating generative AI responses into workflows, Prompt Builder enables customization of AI prompts that interact with Salesforce data and automate complex processes. This tool is especially useful for creating tailored and consistent AI-generated content in various business contexts, including customer service and sales.

It is not a tool for Apex programming (as in option A).

It is also not limited to real-time suggestions as mentioned in option C. Instead, it provides a flexible way for companies to manage and customize how AI-driven responses are generated and used in their workflows.

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

The correct answer is A because the requirement is immediate, deterministic sequencing after account creation. Procedural instructions in Agent Script are designed for multi-step workflows where the agent must run actions in a required order without waiting for another user turn. The specialist should structure the workflow so that after account creation succeeds, the procedural logic runs the verification email step before advancing to profile setup. Option B is weaker because making an action available does not force immediate execution. Option C is phrased incorrectly because run belongs in Agent Script procedural instructions, not inside the create account action itself. Salesforce Agent Script recipes describe action chaining with run, step tracking, procedural instructions, and automatic follow-up action execution in multi-step workflows.