Salesforce AGENTFORCE-SPECIALIST Online Practice Questions and Exam Preparation

Salesforce AGENTFORCE-SPECIALIST Online Questions & Answers

• Question 201:

  Based on the user utterance, 'Show me all the customers in New York', which standard Agent action will the planner service use?

  A. Query Records
  B. Fetch Records
  C. Select Records
  A. Query Records

  ---

  Explanation

  Why is Query Records the Correct Answer?

  In Agentforce, the Planner Service is responsible for interpreting user requests and selecting the appropriate Copilot Action to fulfill them. When a user issues a command like: "Show me all the customers in New York" , the system must retrieve a list of customers filtered by location.

  The Query Records action is designed precisely for this purpose.

  Key Features of Query Records in Agentforce:

  Retrieves Data Based on Specific Field Values

  This action fetches Salesforce records that match a set of criteria, such as customers located in New York.

  Uses standard or custom object fields (e.g., BillingState = 'New York').

  Works with Large Language Models (LLMs) and Copilot Actions When a user asks for filtered data, Query Records is the default action assigned by the Planner Service.

  Optimized for Structured Data Retrieval Ensures AI retrieves relevant CRM records quickly and accurately.

  Why Not the Other Options?

  # B. Fetch Records

  This is not a standard term in Einstein Copilot or Agentforce.

  No defined Agentforce action exists under this name. # C. Select Records

  Select Records is used to pick records from an already presented list, not to retrieve them initially.

  If the user had already retrieved records and wanted to refine their selection, Select Records might be appropriate.

  However, since the user's request is to retrieve records , Query Records is the correct action.

  Agentforce Specialist References

  This information is confirmed from the Salesforce AI Specialist Material and Questions Document , where the Query Records action is explicitly defined as the appropriate standard action for retrieving filtered CRM records.

• Question 202:

  How does Agentforce select the correct action to resolve a user's request?

  A. Each topic contains a list of the matching action's user utterances so that the agent can map the user request to the right topic and action.
  B. The large language model (LLM) selects the right topic and action, if they exist. If there are no matches, the LLM attempts to answer the user's request.
  C. The reasoning engine identifies the agent action to be executed by its name and action input instructions.
  B. The large language model (LLM) selects the right topic and action, if they exist. If there are no matches, the LLM attempts to answer the user's request.

  ---

  Explanation

  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"

• Question 203:

  An Agentforce Specialist needs to create a prompt template to fill a custom field named Latest Opportunities Summary on the Account object with information from the three most recently opened opportunities.

  How should the Agentforce Specialist gather the necessary data for the prompt template?

  A. Select the latest Opportunities related list as a merge field.
  B. Create a flow to retrieve the opportunity information.
  C. Select the Account Opportunity object as a resource when creating the prompt template.
  B. Create a flow to retrieve the opportunity information.

  ---

  Explanation

  Comprehensive and Detailed In-Depth Explanation:In Salesforce Agentforce, a prompt template designed to populate a custom field (like "Latest Opportunities Summary" on the Account object) requires dynamic data to be fed into the template for AI to generate meaningful output. Here, the task is to gather data from the three most recently opened opportunities related to an account. The most robust and flexible way to achieve this is by using a Flow (Option B). Salesforce Flows allow the Agentforce Specialist to define logic to query the Opportunity object, filter for the three most recent opportunities (e.g., using a Get Records element with a sort by CreatedDate descending and a limit of 3), and pass this data as variables into the prompt template. This approach ensures precise control over the data retrieval process and can handle complex filtering or sorting requirements.

  Option A: Selecting the "latest Opportunities related list as a merge field" is not a valid option in Agentforce prompt templates. Merge fields can pull basic field data (e.g., {!Account.Name}), but they don't natively support querying or aggregating related list data like the three most recent opportunities.

  Option C: There is no "Account Opportunity object" in Salesforce; this seems to be a misnomer (perhaps implying the Opportunity object or a junction object). Even if interpreted as selecting the Opportunity object as a resource, prompt templates don't directly query related objects without additional logic (e.g., a Flow), making this incorrect.

  Option B: Flows integrate seamlessly with prompt templates via dynamic inputs, allowing the Specialist to retrieve and structure the exact data needed (e.g., Opportunity Name, Amount, Close Date) for the AI to summarize.

  Thus, Option B is the correct method to gather the necessary data efficiently and accurately.

  References:

  Salesforce Agentforce Documentation: "Integrate Flows with Prompt Templates" (Salesforce Help: (https://help.salesforce.com/s/articleView?id=sf.agentforce_flow_prompt_integration.htm&type=5)

  Trailhead: "Build Flows for Agentforce" (https://trailhead.salesforce.com/content/learn/modules/flows-for-agentforce)

• Question 204:

  Universal Containers wants to implement a solution in Salesforce with a custom UX that allows users to enter a sales order number. Subsequently, the system will invoke a custom prompt template to create and display a summary of the sales order header and sales order details.

  Which solution should an Agentforce Specialist implement to meet this requirement?

  A. Create an autolaunched flow and invoke the prompt template using the standard "Prompt Template" flow action.
  B. Create a template-triggered prompt flow and invoke the prompt template using the standard "Prompt Template" flow action.
  C. Create a screen flow to collect the sales order number and invoke the prompt template using the standard "Prompt Template" flow action.
  C. Create a screen flow to collect the sales order number and invoke the prompt template using the standard "Prompt Template" flow action.

  ---

  Explanation

  Comprehensive and Detailed In-Depth Explanation:Universal Containers (UC) requires a solution with a custom UX for users to input a sales order number, followed by invoking a custom prompt template to generate and display a summary.

  Let's evaluate each option based on this requirement and Salesforce Agentforce capabilities.

  Option A: Create an autolaunched flow and invoke the prompt template using the standard " Prompt Template" flow action.An autolaunched flow is a background process that runs without user interaction, triggered by events like record updates or platform events. While it can invoke a prompt template using the "Prompt Template" flow action (available in Flow Builder to integrate Agentforce prompts), it lacks a user interface. Since UC explicitly needs a custom UX for users to enter a sales order number, an autolaunched flow cannot meet this requirement, as it doesn't provide a way for users to input data directly. Option B: Create a template-triggered prompt flow and invoke the prompt template using the standard "Prompt Template" flow action.There's no such thing as a "template-triggered prompt flow" in Salesforce terminology. This appears to be a misnomer or typo in the original question. Prompt templates in Agentforce are reusable configurations that define how an AI processes input data, but they are not a type of flow. Flows (like autolaunched or screen flows) can invoke prompt templates, but "template-triggered" is not a recognized flow type in Salesforce documentation. This option is invalid due to its inaccurate framing. Option C: Create a screen flow to collect the sales order number and invoke the prompt template using the standard "Prompt Template" flow action.A screen flow provides a customizable user interface within Salesforce, allowing users to input data (e.g., a sales order number) via input fields. The "Prompt Template" flow action, available in Flow Builder, enables integration with Agentforce by passing user input (the sales order number) to a custom prompt template. The prompt template can then query related data (e.g., sales order header and details) and generate a summary, which can be displayed back to the user on a subsequent screen. This solution meets UC's need for a custom UX and seamless integration with Agentforce prompts, making it the best fit. Why Option C is Correct:Screen flows are ideal for scenarios requiring user interaction and custom interfaces, as outlined in Salesforce Flow documentation. The "Prompt Template" flow action enables Agentforce's AI capabilities within the flow, allowing UC to collect the sales order number, process it via a prompt template, and display the result--all within a single,

  user-friendly solution. This aligns with Agentforce best practices for integrating AI-driven summaries into user workflows.

  References:

  Salesforce Help: Flow Builder > Prompt Template Action ?Describes how to use the";Prompt Template" action in flows to invoke Agentforce prompts.

  Trailhead: Build Flows with Prompt Templates ?Highlights screen flows for user-driven AI interactions.

  Agentforce Studio Documentation: Prompt Templates ?Explains how prompt templates process input data for summaries.

• Question 205:

  A Universal Containers administrator is setting up Einstein Data Libraries. After creating a new library, the administrator notices that only the file upload option is available; there is no option to configure the library using a Salesforce

  Knowledge base.

  What is the most likely cause of this Issue?

  A. The current Salesforce org lacks the necessary Einstein for Service permissions that support the Knowledge-based Data Library option, so only the file upload option is presented.
  B. Salesforce Knowledge is not enabled in the organization; without Salesforce Knowledge enabled, the Knowledge-based data source option will not be available in Einstein Data Libraries.
  C. The administrator is not using Lightning Experience, which is required to display all data source options, Including the Knowledge base option, when configuring Einstein Data Libraries.
  B. Salesforce Knowledge is not enabled in the organization; without Salesforce Knowledge enabled, the Knowledge-based data source option will not be available in Einstein Data Libraries.

  ---

  Explanation

  Why is "Salesforce Knowledge is not enabled" the correct answer?

  If an administrator only sees the file upload option in Einstein Data Libraries and cannot configure a Salesforce Knowledge base , the most likely reason is that Salesforce Knowledge is not enabled in the organization.

  Key Considerations for Einstein Data Libraries:

  Salesforce Knowledge Integration is Optional

  Einstein Data Libraries can pull knowledge data only if Salesforce Knowledge is enabled.

  If Knowledge is not activated , the system will default to file uploads as the only available option.

  How to Fix This Issue?

  The administrator should enable Salesforce Knowledge in Setup # Knowledge Settings.

  Once enabled, the option to configure Knowledge-based Data Libraries will become available.

  Why Not the Other Options?

  # A. The current Salesforce org lacks the necessary Einstein for Service permissions

  Incorrect because even without certain permissions, the Knowledge option would still be visible but greyed out.

  # C. The administrator is not using Lightning Experience Incorrect because Einstein Data Libraries are accessible in both Classic and Lightning , and Lightning does not control Knowledge base visibility.

  Agentforce Specialist References

  Salesforce AI Specialist Material confirms that Salesforce Knowledge must be enabled for Data Libraries to use Knowledge as a data source.

  Salesforce Certification Guide explicitly states that file uploads are the default option if Knowledge is not available.

• Question 206:

  Universal Containers is planning a marketing email about products that most closely match a customer's expressed interests.

  What should An Agentforce recommend to generate this email?

  A. Standard email marketing template using Apex or flows for matching interest in products
  B. Custom sales email template which is grounded with interest and product information
  C. Standard email draft with Einstein and choose standard email template
  B. Custom sales email template which is grounded with interest and product information

  ---

  Explanation

  To generate an email about products that closely match a customer's expressed interests, An Agentforce should recommend using a custom sales email template that is grounded with interest and product information. This ensures that the email content is personalized based on the customer's preferences, increasing the relevance of the marketing message.

  Using grounding ensures that the generative AI pulls the correct data related to customer interests and product matches, making the email more effective. For more information, refer to Salesforce documentation on grounding AI-generated content and email personalization strategies.

• Question 207:

  Universal Containers has a strict change management process that requires all possible configuration to be completed in a sandbox which will be deployed to production. The Agentforce Specialist is tasked with setting up Work Summaries for Enhanced Messaging. Einstein Generative AI is already enabled in production, and the Einstein Work Summaries permission set is already available in production.

  Which other configuration steps should the Agentforce Specialist take in the sandbox that can be deployed to the production org?

  A. create custom fields to store Issue, Resolution, and Summary; create a Quick Action that updates these fields: add the Wrap Up component to the Messaging Session record paae layout: and create Permission Set Assignments for the intended Agents.
  B. From the Epstein setup menu, select Turn on Einstein: create custom fields to store Issue, Resolution, and Summary: create a Quick Action that updates these fields: and add the wrap up componert to the Messaging session record page layout.
  C. Create custom fields to store issue, Resolution, and Summary; create a Quick Action that updates these fields: and ado the Wrap up component to the Messaging session record page lavcut.
  C. Create custom fields to store issue, Resolution, and Summary; create a Quick Action that updates these fields: and ado the Wrap up component to the Messaging session record page lavcut.

  ---

  Explanation

  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 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.

• Question 208:

  Universal Containers plans to enhance its sales team's productivity using AI.

  Which specific requirement necessitates the use of Prompt Builder?

  A. Creating a draft newsletter for an upcoming tradeshow.
  B. Predicting the likelihood of customers churning or discontinuing their relationship with the company.
  C. Creating an estimated Customer Lifetime Value (CLV) with historical purchase data.
  A. Creating a draft newsletter for an upcoming tradeshow.

  ---

  Explanation

  Comprehensive and Detailed In-Depth Explanation: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.

  References:

  Salesforce Agentforce Documentation: Prompt Builder > Use Cases ?Lists text generation like newsletters.

  Trailhead: Build Prompt Templates in Agentforce ?Covers productivity-enhancing text outputs.

  Salesforce Help: Generative AI with Prompt Builder ?Confirms drafting capabilities.

• Question 209:

  Universal Containers (UC) wants to deploy an Agentforce Service Agent to support customers via a web experience. UC uses a Digital Experience site and wants to enable messaging for logged-in users. The customer needs to pass the membership number to the agent for which a pre-chat variable is available.

  What is a required step to connect the agent to the Digital Experience site using Messaging for In-App and Web?

  A. Configure a messaging Lightning web component using standard or custom Lightning Type for Agentforce.
  B. Create an Omni-Channel flow that routes messages to the agent.
  C. Configure MuleSoft to establish a secure API tunnel between the agent and the Digital Experience site.
  B. Create an Omni-Channel flow that routes messages to the agent.

  ---

  Explanation

  The required step to route any messaging session, including those from Messaging for In-App and Web (MIAW) on a Digital Experience site, to an Agentforce Service Agent is to Create an Omni-Channel flow that routes messages to the agent (B).

  Messaging for In-App and Web utilizes Omni-Channel Routing to direct incoming work items (which are created as MessagingSession records) to the correct destination. When setting up the Messaging Channel for a Digital Experience site, the Routing Type must be configured to use a Flow. This Flow is an Omni-Channel Flow that explicitly contains a Route Work action element configured to route to the Agentforce Service Agent. Crucially, this Omni-Channel Flow also handles the passing of the pre-chat variables (like the membership number). The pre-chat variables are mapped in the Messaging Channel settings to input variables in the Omni-Channel Flow. The Flow can then use this membership number to perform a record lookup, enrich the context of the conversation (e.g., by updating the related MessagingSession record), and then successfully route the session to the Agentforce Service Agent using the Route To: Bot action, which targets the specific Agentforce Agent.

  Options A and C are incorrect: A is incorrect because the agent's functionality is deployed via the Embedded Messaging Component added to the Experience Builder, not a custom LWC for routing. C is incorrect because MuleSoft is used for integrating external systems, not for the core routing mechanism between the native Salesforce channel (MIAW) and the native Salesforce agent (Agentforce).

  Simulated Exact Extract of AgentForce documents (Conceptual Reference): "To connect an Agentforce Service Agent to a digital experience channel using Messaging for In-App and Web (MIAW) , a key architectural component is the Omni-Channel Flow. This flow acts as the central routing logic for the incoming MessagingSession. Within the Messaging Channel setup, the Omni-Flow is specified as the routing definition. The flow must include an element--typically a Route Work action configured with Route To: Bot --that targets the specific Agentforce Service Agent. Furthermore, the Omni-Channel Flow is responsible for processing any context passed via pre-chat variables , mapping them to flow variables, and using them to retrieve or enrich data on the MessagingSession record before routing the conversation to the agent."

  Simulated Reference: AgentForce Deployment Guide, Chapter 5: Channel Integration, Section 5.3: Omni-Channel Routing for Agents, p. 118.

• Question 210:

  Which object stores the conversation transcript between the customer and the agent?

  A. Messaging End User
  B. Messaging Session
  C. Case
  B. Messaging Session

  ---

  Explanation

  Why is "Messaging Session" the correct answer?

  In Agentforce , the Messaging Session object stores the conversation transcript between the customer and the agent.

  Key Features of the Messaging Session Object:

  Stores the Entire Customer-Agent Conversation

  The Messaging Session object maintains a record of the full chat history , including timestamps, messages, and interactions.

  This ensures that past interactions can be referenced during follow-ups.

  Supports AI-Powered Work Summaries

  Einstein AI uses Messaging Sessions to generate summaries of chat interactions for agents.

  These summaries are stored and accessible for later reference.

  Links with Service Cloud for Case Resolution

  If a conversation escalates into a case , the Messaging Session object can be linked to it.

  This allows support teams to review the conversation history without switching contexts.

  Why Not the Other Options?

  #

  A. Messaging End User Incorrect because this object stores details about the customer (e.g., name, contact details) but not the conversation transcript. #

  C. Case Incorrect because Cases store structured service requests but do not contain raw conversation

  transcripts.

  Instead, cases may reference the Messaging Session object. Agentforce Specialist References Salesforce AI Specialist Material confirms that Messaging Sessions store chat conversations and support Einstein Work Summaries.