Salesforce AGENTFORCE-SPECIALIST Online Practice Questions and Exam Preparation

Salesforce AGENTFORCE-SPECIALIST Online Questions & Answers

• Question 161:

  An Agentforce at Universal Containers is working on a prompt template to generate personalized emails for product demonstration requests from customers. It is important for the Al-generated email to adhere strictly to the guidelines, using only associated opportunity information, and to encourage the recipient to take the desired action.

  How should the Agentforce Specialist include these instructions on a new line in the prompt template?

  A. Surround them with triple quotes (""").
  B. Make sure merged fields are defined.
  C. Use curly brackets {} to encapsulate instructions.
  A. Surround them with triple quotes (""").

  ---

  Explanation

  In Salesforce prompt templates, instructions that guide how the Large Language Model (LLM) should generate content (in this case, personalized emails) can be included by surrounding the instruction text with triple quotes ("""). This formatting ensures that the LLM adheres to the specific instructions while generating the email content.

  The use of triple quotes allows the AI to understand that the enclosed text is a directive for how to approach the task, such as limiting the content to associated opportunity information or encouraging a specific action from the recipient.

  Refer to Salesforce Prompt Builder documentation for detailed instructions on how to structure prompts for generative AI.

• Question 162:

  Universal Containers has grounded a prompt template with a related list. During user acceptance testing (UAT), users are not getting the correct responses.

  What is causing this issue?

  A. The related list is Read Only.
  B. The related list prompt template option is not enabled.
  C. The related list is not on the parent object's page layout.
  C. The related list is not on the parent object's page layout.

  ---

  Explanation

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

  References:

  Salesforce Agentforce Documentation: Grounding with Related Lists ?Notes dependency on page layout configuration.

  Trailhead: Ground Your Agentforce Prompts ?Highlights related list setup for accurate grounding.

  Salesforce Help: Troubleshoot Prompt Responses ?Lists layout issues as a common grounding problem.

• Question 163:

  Universal Containers (UC) has configured an Agentforce Data Library using Knowledge articles. When testing in Agent Builder and the Experience Cloud site, the agent is not responding with grounded Knowledge article information.

  However, when tested in Prompt Builder, the response returns correctly.

  What should UC do to troubleshoot the issue?

  A. Create a new permission set that assigns "Manage Knowledge" and assign it to the Agentforce Service Agent User.
  B. Ensure the assigned User permission set includes access to the prompt template used to access the Knowledge articles.
  C. Ensure the Data Cloud User permission set has been assigned to the Agentforce Service Agent User.
  C. Ensure the Data Cloud User permission set has been assigned to the Agentforce Service Agent User.

  ---

  Explanation

  Comprehensive and Detailed In-Depth Explanation:UC has set up an Agentforce Data Library with Knowledge articles, and while Prompt Builder retrieves the data correctly, the agent fails to do so in Agent Builder and Experience Cloud. Let's troubleshoot the issue.

  Option A: Create a new permission set that assigns "Manage Knowledge" and assign it to the Agentforce Service Agent User.The "Manage Knowledge" permission is for authoring and managing Knowledge articles, not for reading or retrieving them in an agent context. The Agentforce Service Agent User (a system user) needs read access to Knowledge, not management rights. This option is excessive and irrelevant to the grounding issue, making it incorrect.

  Option B: Ensure the assigned User permission set includes access to the prompt template used to access the Knowledge articles.Prompt templates in Prompt Builder don't require specific permissions beyond general Einstein Generative AI access.

  Since the Prompt Builder test works, the template and its grounding are accessible to the testing user. The issue lies with the agent's runtime access, not the template itself, making this incorrect.

  Option C: Ensure the Data Cloud User permission set has been assigned to the Agentforce Service Agent User.When Knowledge articles are grounded via an Agentforce Data Library, they are often ingested into Data Cloud for indexing and retrieval. The Agentforce Service Agent User, which runs the agent, needs the "Data Cloud User" permission set (or equivalent) to access Data Cloud resources, including the Data Library. If this permission is missing, the agent cannot retrieve Knowledge article data during runtime (e.g., in Agent Builder or Experience Cloud), even though Prompt Builder (running under a different user context) succeeds. This is a common setup oversight and aligns with the symptoms, making it the correct answer.

  Why Option C is Correct:The Agentforce Service Agent User's lack of Data Cloud access explains the failure in agent-driven contexts while Prompt Builder (likely run by an admin with broader permissions) succeeds. Assigning the "Data Cloud User" permission set resolves this, per Salesforce documentation.

  References:

  Salesforce Agentforce Documentation: Data Library Setup > Permissions ?Requires Data Cloud access for agents.

  Trailhead: Ground Your Agentforce Prompts ?Notes Data Cloud User permission for Knowledge grounding.

  Salesforce Help: Agentforce Security > Agent User Setup ?Lists required permission sets.

• Question 164:

  Universal Containers wants to systematically validate agent responses before deployment using a scalable testing process.

  Which Testing Center approach should the company implement?

  A. Upload a structured CSV test template and run batch test cases in Testing Center.
  B. Manually interact with the agent in Builder until responses seem correct.
  C. Use pilot users in production to flag incorrect responses post-launch.
  A. Upload a structured CSV test template and run batch test cases in Testing Center.

  ---

  Explanation

  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.

  References:

  AgentForce Testing Guide --"Using CSV Test Templates for Automated Batch Evaluation."

• Question 165:

  Universal Containers has multiple Salesforce orgs, each with a unique customer service agent where a verification agent must pass customer identity data to downstream agents handling account modifications. The customer ID must remain secure and persistent across agent handoffs without exposure to large language model (LLM) modification.

  What is the most appropriate configuration?

  A. Store customer identity information in conversation variables created by the first agent and have other agents read those same conversation variables.
  B. Use conversation memory to store the verified customer ID and share it with all downstream agents for context continuity.
  C. Use the Agent API to start the downstream agent's session and pass the verified customer ID as a read-only context variable, ensuring security and preventing LLM alteration.
  C. Use the Agent API to start the downstream agent's session and pass the verified customer ID as a read-only context variable, ensuring security and preventing LLM alteration.

  ---

  Explanation

  The AgentForce Inter-Agent Communication and Security Configuration Guide specifies that when Agent API to initiate the downstream agent's session. The verified data should be passed as a read-only context variable, ensuring persistence across sessions while preventing modification by the large language model (LLM).

  This setup maintains data integrity and security compliance by isolating sensitive variables from the LLM's reasoning layer. Context variables passed via the Agent API are immutable during runtime, ensuring they cannot be altered or exposed in agent-generated responses.

  Option A adds unnecessary data persistence and complexity.

  Option B is insecure because conversation variables are exposed to the LLM context, risking unintended modification or leakage. Therefore, the most secure and compliant configuration is Option C -Use the Agent API to pass verified IDs as read-only context variables between agents.

• Question 166:

  An Agentforce Specialist notices that a prompt template sometimes exceeds token limits depending on the record being processed.

  What is the primary reason for this behavior?

  A. The LLM dynamically adjusts token limits
  B. The prompt template includes variable-length data
  C. The Trust Layer increases token usage
  B. The prompt template includes variable-length data

  ---

  Explanation

  Prompt templates often include dynamic data from records. Since record data varies in length, the total token count changes, sometimes exceeding limits.

  Option A is incorrect because token limits are fixed.

  Option C does not impact token count variability.

  Therefore, Option B explains the issue.

• Question 167:

  Once a data source is chosen for an Agentforce Data Library, what is true about changing that data source later?

  A. The data source can be changed through the Data Cloud settings.
  B. The Data Retriever can be reconfigured to use a different data source.
  C. The data source cannot be changed after it is selected.
  C. The data source cannot be changed after it is selected.

  ---

  Explanation

  Why is "The data source cannot be changed after it is selected" the correct answer?

  When configuring an Agentforce Data Library , the data source selection is permanent. Once a data source is set, it cannot be modified or replaced. This design ensures data consistency, security, and reliability within Salesforce's AI-driven environment. Key Considerations in Agentforce Data Library Data Source Lock-In The chosen data source remains fixed to maintain data integrity and avoid inconsistencies.

  Any updates or modifications require creating a new Data Library instead of modifying the existing one.

  Why Can't the Data Source Be Changed?

  The data source defines the foundation of AI-driven workflows , and any modification would disrupt processing logic.

  Agentforce tools rely on structured datasets to enable AI-powered recommendations , and changing data sources could lead to inconsistencies in grounding techniques.

  Workarounds for Changing Data Sources

  If an organization needs to use a different data source, a new Agentforce Data Library must be created and configured from scratch.

  Old data can be manually migrated into the new data source for continuity.

  Why Not the Other Options?

  # A. The data source can be changed through the Data Cloud settings.

  Incorrect because once the data source is linked to an Agentforce Data Library, it cannot be altered, even via Data Cloud settings.

  # B. The Data Retriever can be reconfigured to use a different data source.

  Incorrect as the Data Retriever works within the constraints of the selected data source and does not provide an option to swap data sources post-selection.

  Agentforce Specialist References

  The Salesforce AI Specialist Material and Salesforce Instructions for the Certification confirm that once a data source is set for an Agentforce Data Library, it cannot be changed.

• Question 168:

  What is the role of the large language model (LLM) in understanding intent and executing an Agent Action?

  A. Find similar requested topics and provide the actions that need to be executed.
  B. Identify the best matching topic and actions and correct order of execution.
  C. Determine a user's topic access and sort actions by priority to be executed.
  B. Identify the best matching topic and actions and correct order of execution.

  ---

  Explanation

  Comprehensive and Detailed In-Depth Explanation:In Agentforce, the large language model (LLM), powered by the Atlas Reasoning Engine, interprets user requests and drives Agent Actions. Let's evaluate its role.

  Option A: Find similar requested topics and provide the actions that need to be executed.While the LLM can identify similar topics, its role extends beyond merely finding them--it matches intents to specific topics and determines execution.

  This option understates the LLM's responsibility for ordering actions, making it incomplete and incorrect.

  Option B: Identify the best matching topic and actions and correct order of execution.The LLM analyzes user input to understand intent, matches it to the best-fitting topic (configured in Agent Builder), and selects associated actions. It also determines the correct sequence of execution based on the agent's plan (e.g., retrieve data before updating a record). This end-to-end process--from intent recognition to action orchestration--is the LLM's core role in Agentforce, making this the correct answer.

  Option C: Determine a user's topic access and sort actions by priority to be executed.Topic access is governed by Salesforce permissions (e.g., user profiles), not the LLM. While the LLM prioritizes actions within its plan, its primary role is intent matching and execution ordering, not access control, making this incorrect.

  Why Option B is Correct:The LLM's role in identifying topics, selecting actions, and ordering execution is central to Agentforce's autonomous functionality, as detailed in Salesforce documentation.

  References:

  Salesforce Agentforce Documentation: Atlas Reasoning Engine ?Outlines LLM's intent and action handling.

  Trailhead: Understand Agentforce Technology ?Explains topic matching and execution.

  Salesforce Help: Agentforce Actions ?Confirms LLM's role in orchestrating responses.

• Question 169:

  An administrator at Universal Containers is setting up a new Sales Development Representative (SDR) Agent. The agent's purpose is to nurture cold leads before connecting them to the assigned sales rep.

  To ensure the agent has all the necessary access to the leads in the North America sales region, what should the administrator data?

  A. Assign the user in the highest-level role within the North America role hierarchy as the SDR Agent User.
  B. Grant View All record permission of the Lead object to the `Einstein Agent User' profile,
  C. Create a criteria-based sharing rule to grant access to targeted lead records to SDR Agent User.
  C. Create a criteria-based sharing rule to grant access to targeted lead records to SDR Agent User.

  ---

  Explanation

  According to the AgentForce Security and Data Access Configuration Guide , the best practice for ensuring an agent (such as an SDR Agent) can access specific records while maintaining security is to use criteria-based sharing rules. The documentation states: "When an AI Agent needs access to a subset of records (for example, regional leads), create a sharing rule granting access to that agent's user context based on defined criteria such as region or ownership." Option A (assigning the highest-level role) provides excessive access beyond the intended scope, violating the principle of least privilege.

  Option B (View All permission) gives global object access, which is not secure.

  Therefore, Option C ensures that the SDR Agent has controlled, region-specific access to lead records.

  References (AgentForce Documents / Study Guide):

  AgentForce Security and Access Guide: "Using Sharing Rules for AI Agent Access Control"

  AgentForce Implementation Handbook: "Regional Access Configuration for SDR Agents" Salesforce Data Security Study Guide

• Question 170:

  Which Agentforce feature helps service agents respond to repeat customer inquiries with the most relevant AI-suggested replies?

  A. Case Reply Analysis
  B. Service AI Grounding
  C. Einstein Reply Recommendations
  D. Customer Query Matching
  C. Einstein Reply Recommendations

  ---

  Explanation

  Einstein Reply Recommendations suggests AI-generated response templates based on historical customer interactions.