Salesforce Certified Agentforce Specialist (AI-201) Exam Questions

Answer : A

When using related list merge fields in a prompt template associated with the Account object in Prompt Builder, the Activities related list is not supported due to it being a polymorphic field. Polymorphic fields can reference multiple different types of objects, which makes them incompatible with some merge field operations in prompt generation.

Option B is incorrect because person accounts do not limit the availability of merge fields for the Account object.

Option C is irrelevant since even if no related lists are available at runtime, the prompt can still generate based on other available data fields.

For more information, refer to Salesforce documentation on supported fields and limitations in Prompt Builder.

Answer : B

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

Answer : C

TheTemperaturehyperparameter controls the randomness of model outputs:

Low Temperature (e.g., 0.2): More deterministic, consistent responses.

High Temperature (e.g., 1.0): More creative, varied responses.

Presence Penalty (Option A): Discourages repetition of tokens, unrelated to randomness.

Variability (Option B): Not a standard hyperparameter in Einstein Studio.

Einstein Studio Documentation:Model Hyperparameters

Explicitly states 'Temperature adjusts the balance between predictable and random outputs.'

Answer : A

Context of the QUESTIO N NO: Universal Containers (UC) wants to harness generative AI to boost sales productivity. They are wary of public AI virtual assistants (like generic chatbots) that lack sufficient UC-specific data to generate useful business responses.

Why Fine-Tune an Einstein AI Model with CRM Data?

Company-Specific Relevance: By fine-tuning Einstein AI with UC's CRM data (accounts, opportunities, products, and historical interactions), the model learns the enterprise-specific context. This ensures that the generative outputs are accurate and tailored to UC's sales scenarios.

Security and Compliance: Using Salesforce Einstein within the Salesforce ecosystem keeps data under UC's control, aligning with trust, security, and compliance requirements.

Better Predictions: Einstein AI can produce more relevant insights (e.g., recommended next steps, content suggestions, or AI-generated email responses) when it has been trained on real, high-quality internal data.

Why Not Build an AI Model with Einstein Discovery (Option B)?

Einstein Discovery Use Case: Einstein Discovery is best suited for predictive and prescriptive analytics (e.g., analyzing large data sets for patterns, scoring leads, or predicting churn). While it provides advanced analytics, it is not primarily designed for generative text-based interactions for end-user consumption in a conversational format.

Why Not Enable Agentforce (Option C)?

Agentforce Overview: ''Agentforce'' (sometimes referencing a pilot or non-mainstream name) typically focuses on interactive help or workforce collaboration. It does not inherently solve the problem of large-scale generative AI using internal CRM data. Moreover, you still need a robust generative engine fine-tuned on company data.

Outcome: Fine-tuning the Einstein AI model with UC's CRM data (Answer A) is the most direct, Salesforce-native solution to provide generative AI responses that are aligned with UC's context, driving productivity gains and ensuring data privacy.

Salesforce Agentforce Specialist Reference & Documents

Salesforce Official: Einstein GPT Overview

Discusses how Einstein GPT can be fine-tuned with specific CRM data to deliver contextually relevant, generative AI responses.

Salesforce Trailhead: Get Started with Salesforce Einstein

Explains the fundamentals of AI within the Salesforce platform, including training and optimizing Einstein models.

Salesforce Documentation: Einstein Discovery

Details how Einstein Discovery is primarily used for advanced analytics and predictions, not direct generative text solutions.

Salesforce Agentforce Specialist Study Guide

Provides the official outline of Einstein AI capabilities, referencing how to configure and fine-tune models for specialized enterprise use cases.

Answer : B

Comprehensive and Detailed Explanation From Exact Extract of AgentForce Documents:

According to the AgentForce Troubleshooting and Optimization Guide, hallucinations --- instances where the agent fabricates details such as weblinks or data --- often occur due to issues in prompt construction or retrieved content grounding. The recommended diagnostic process involves inspecting the prompt template instructions and reviewing the resolved prompt output, including the actual retrieved knowledge chunks.

By examining these areas, the AgentForce Specialist can determine whether the hallucinated content originates from ambiguous prompt phrasing, missing grounding variables, or irrelevant retrieval results. This approach ensures an evidence-based investigation directly linked to the agent's reasoning and generation steps.

Option A is incorrect because hallucination guardrails are defined in prompts and actions, not topic names or classification descriptions. Option C is also incorrect since simply adding ''ALWAYS'' to instructions does not enforce factual grounding and is not a documented troubleshooting method.

Therefore, per AgentForce best practices, the correct process is Option B -- Examine the prompt instructions and contents of the chunks in the resolved prompt output.

Answer : C

The correct answer is C because persistent routing to the wrong subagent usually indicates semantic overlap in subagent purpose, description, or entry conditions. Agentforce uses subagent descriptions and instructions to determine which capability is relevant to the user's intent. If ''Claims Intake'' and ''Policy Inquiry'' both describe insurance policy details, claims eligibility, or coverage questions too broadly, the reasoning engine can classify claims requests into the wrong subagent. Procedural instructions and Flows are not the normal root cause of intent classification failure. Global instructions can influence overall behavior, but they should not be used as the primary routing definition for competing subagents. Salesforce Agent Script guidance emphasizes that topic or subagent descriptions help the model understand when a topic is relevant during classification.

Answer : B

The correct answer is B because deterministic fee calculation and reuse require state management, not conversational memory. The fee should be calculated by a Flow action, then stored in a context variable so the same validated value can be referenced later in the conversation. This prevents the large language model from recalculating, rounding differently, or hallucinating a new value during the refund summary. Option A is incomplete because simply exposing a Flow output once does not guarantee stable reuse throughout the session. Option C is unsafe because system instructions do not enforce calculation accuracy or persistence. Salesforce guidance states that variables can be used in filters, instructions, and action inputs, and Agent Script supports deterministic logic, setting variables, and running actions.