Important Salesforce Certified Agentforce Specialist (AI-201) Exam Questions

Answer: A

Explanation:

The correct answer is A. Since historical policy versions must remain searchable, the solution is not deletion; it is deterministic retrieval scoping. A custom retriever with a dynamic filter can use the customer's Contract record to pass the applicable policy version at runtime. That limits candidate chunks before semantic ranking, reducing the risk that the LLM receives the wrong policy version. Option B helps add context to chunks, but it still leaves the LLM to choose among versions after retrieval, which is weaker for legal accuracy. Option C creates unnecessary operational complexity by splitting every policy version into separate data streams. Data 360 retrievers are designed to search indexes and can be customized with filters and runtime filter values for more precise grounding.

Answer: C

Explanation:

The AgentForce API Integration Guide defines the Agent API as the framework that enables external web or mobile applications to communicate directly with Salesforce-hosted agents. This API supports message exchange, session management, and context persistence --- allowing developers to build custom chat interfaces while maintaining secure, real-time connectivity with the AgentForce reasoning engine.

Option A (A2A) is for inter-agent collaboration within Salesforce, not for external web integration. Option B (MCP) --- Model Context Protocol --- is used for context sharing between models and tools, not for front-end integration.

Therefore, the correct framework for enabling communication between a custom website chat interface and an AgentForce agent is Option C -- Agent API, as it provides the structured interface for external client applications.

Answer: C

Explanation:

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.

Answer: C

Explanation:

The correct answer is C. The problem is inconsistent LLM-selected behavior, so the fix must remove discretion from the reasoning engine for the mandatory fraud check. Salesforce explains that run inside reasoning.instructions is deterministic: the action executes immediately when the code path is reached. Placing run @actions.fraud_check before run @actions.process_refund enforces the fraud check before the refund is processed. Option A describes exposing or suggesting an action to the LLM, which is not enough for mandatory compliance logic. Option B invents a side effect; deterministic action execution does not remove the agent's ability to use an empathetic tone in generated responses. The key distinction is forced procedural execution versus optional LLM tool selection.

Answer: B

Explanation:

UC wants to streamline the use of Generative AI by reducing the time reps spend typing prompts and ensuring consistency, leveraging their existing prompt knowledge. Let's evaluate the options.

Option A: Agent Builder and Action: Query Records.Agent Builder in Agentforce Studio creates autonomous AI agents with actions like 'Query Records' to fetch data. While this could retrieve information, it's designed for agent-driven workflows, not for simplifying manual prompt entry or ensuring consistency across user inputs. This doesn't directly address UC's concerns and is incorrect.

Option B: Einstein Prompt Builder and Prompt Templates.Einstein Prompt Builder, part of Agentforce Studio, allows users to create reusable prompt templates that encapsulate specific instructions and grounding for Generative AI (e.g., using public models via the Atlas Reasoning Engine). UC can predefine prompts based on their known language, saving time for reps by eliminating repetitive typing and ensuring consistency across sales and service teams. Templates can be embedded in flows, Lightning pages, or agent interactions, perfectly addressing UC's needs. This is the correct answer.

Option C: Einstein Recommendation Builder.Einstein Recommendation Builder generates personalized recommendations (e.g., products, next best actions) using predictive AI, not Generative AI for freeform prompts. It doesn't support custom prompt creation or address time/consistency issues for reps, making it incorrect.

Why Option B is Correct:

Einstein Prompt Builder's prompt templates directly tackle UC's challenges by standardizing prompts and reducing manual effort, leveraging their familiarity with Generative AI language. This is a core feature for such use cases, as per Salesforce documentation.

Salesforce Agentforce Documentation: Einstein Prompt Builder -- Details prompt templates for consistency and efficiency.

Trailhead: Build Prompt Templates in Agentforce -- Explains time-saving benefits of templates.

Salesforce Help: Generative AI with Prompt Builder -- Confirms use for streamlining rep interactions.