Agentforce-Specialist Questions and Answers

In Salesforce Agentforce, a Data Library is a feature that allows organizations to upload files (e.g., PDFs, documents) to be used as grounding data for AI-driven agents. Once the Data Library is created and configured, the uploaded files are indexed to make their content searchable and usable by the AI (e.g., for retrieval-augmented generation or prompt enhancement). The key question is where this indexing occurs. Salesforce Agentforce integrates tightly with Data Cloud, a unified data platform that includes a vector database optimized for storing and indexing unstructured data like uploaded files. When a Data Library is set up, the files are ingested and indexed into Data Cloud’s vector database, enabling the AI to efficiently retrieve relevant information from them during conversations or actions.

Option A: Indexing files in a " location specified by the user " is not a feature of Agentforce Data Libraries. The indexing process is managed by Salesforce infrastructure, not a user-defined location.

Option B: This is correct. Data Cloud handles the indexing of uploaded files, storing them in its vector database to support AI capabilities like semantic search and content retrieval.

Option C: Salesforce File Storage (e.g., where ContentVersion records are stored) is used for general file storage, but it does not inherently index files for AI use. Agentforce relies on Data Cloud for indexing, not basic file storage.

Thus, Option B accurately reflects the process after a Data Library is created and configured in Agentforce.

Salesforce Agentforce Documentation: " Set Up a Data Library " (Salesforce Help: https://help.salesforce.com/s/articleView?id=sf.agentforce_data_library.htm & type=5)

Salesforce Data Cloud Documentation: " Vector Database for AI " (https://help.salesforce.com/s/articleView?id=sf.data_cloud_vector_database.htm & type=5)

In AgentForce documentation on Knowledge Indexing and Chunking Strategies, Salesforce emphasizes that when uploading large volumes of structured content such as HTML or documentation files, the system should use section-aware chunking. The guide states: “Section-aware chunking preserves the logical boundaries of headings, paragraphs, and sub-sections in structured documents like HTML or PDF files, allowing the agent to retrieve contextually accurate and relevant responses quickly.”

This method ensures that the agent does not split content mid-section or lose contextual relationships between headings and body text. It enhances both retrieval speed and answer precision.

Option A, semantic-based passage extraction, is better suited for free-text knowledge bases, where meaning needs to be inferred. Option B, conversation-based chunking, applies only to chat logs or dialogue histories. For HTML documentation and structured articles, section-aware chunking ensures optimized retrieval and minimal latency in AgentForce responses.

References (AgentForce Documents / Study Guide):

AgentForce Knowledge Management Guide: “Choosing the Right Chunking Strategy”

AgentForce Indexing and Retrieval Optimization Study Notes

AgentForce Developer Handbook: “Implementing Section-Aware Chunking for Structured Files”

To enable Sales Email prompt templates:

Permission Set: Assign the Prompt Template User permission set to the sales team to grant access to use pre-built templates.

Feature Activation: Enable Sales Emails in Salesforce Setup to activate the integration between prompt templates and email workflows.

Option B (Manager permission set): Required for creating/modifying templates, not for usage.

Option C (Data Cloud Admin): Unrelated to prompt template access.

The correct answer is C because Agent-to-Agent, or A2A, is the purpose-built protocol for communication and collaboration between AI agents across different vendors and platforms. In this scenario, Cloud Kicks has a third-party research agent and an Agentforce customer service agent. The requirement is direct cross-vendor agent communication, not just access to a tool or external endpoint. MCP is mainly used to connect agents with tools, resources, and external context. A generic API can integrate systems, but it is not the agent-interoperability protocol being tested here. Salesforce describes A2A as an open standard that allows AI agents from different platforms to securely communicate, collaborate, share context, and coordinate work.

Agentforce Optimization is the correct feature because the requirement is not just to inspect one failed conversation; it is to analyze performance patterns across many sessions. Salesforce describes Agent Optimization as a capability used to drill into sessions, analyze quality scores, and identify patterns that improve agent performance. That directly matches the need to find recurring escalation patterns, weak subagents, and misconfigured actions. Agentforce Session Tracing is useful for deep, turn-by-turn investigation of an individual interaction, but it is not the best fit for clustering performance gaps across thousands of conversations. Agentforce Health Monitoring is too generic and does not specifically provide the optimization analysis and quality-scoring workflow described in the question.

================

In this scenario, the Agent capability that best helps the agent is its ability to execute tasks based on available actions and answer questions using data from Knowledge articles. Agent can assist the service agent by providing relevant Knowledge articles on canceling and rebooking flights, ensuring that the agent has access to the correct steps and procedures directly within the workflow.

This feature leverages the agent’s existing context (the travel itinerary) and provides actionable insights or next steps from the relevant Knowledge articles to help the agent quickly resolve the customer’s needs.

The other options are incorrect:

B refers to invoking a flow to create a Knowledge article, which is unrelated to the task of retrieving existing Knowledge articles.

C focuses on generating Knowledge articles, which is not the immediate need for this situation where the agent requires guidance on existing procedures.

Salesforce Documentation on Agent

Trailhead Module on Einstein for Service

The correct answer is C because Salesforce applies different upload limits based on file type for file-based Agentforce Data Libraries. Text and HTML files have a smaller supported maximum of 4 MB, while PDF files can be uploaded up to 100 MB. Option A reverses the limits and is therefore incorrect. Option B invents a uniform 50 MB limit, which does not match Salesforce’s documented limits. This distinction matters during implementation because oversized text or HTML files must be reduced, split, or converted into a supported ingestion pattern before indexing. PDF files have a higher ceiling, but they still must meet processing and library requirements. Salesforce documentation for uploaded files states that users can upload up to 4 MB for text or HTML files and 100 MB for PDF files.

According to the AgentForce Product Overview and Deployment Guide, Salesforce recommends using purpose-built agents to maximize efficiency across departments. The documentation states:

“Each AgentForce agent type is optimized for a specific function — SDR Agent for sales development and lead nurturing, Service Agent for customer service and support cases, and Employee Agent for internal HR, IT, and productivity tasks.”

This separation ensures that each team benefits from a domain-specific agent equipped with the correct data access and actions.

Option B incorrectly assigns agent types to mismatched use cases, and Option C reduces efficiency and control by using a single generic agent for multiple domains, which goes against Salesforce’s modular AI design principle.

Thus, Option A best aligns with Salesforce’s guidance for role-based AgentForce deployment.

References (AgentForce Documents / Study Guide):

AgentForce Product Overview: “Agent Types and Use Cases”

AgentForce Implementation Guide: “Aligning Agents to Departmental Functions”

AgentForce Study Guide: “Optimizing Team Efficiency with Specialized Agents”

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.

The correct answer is B. Flex prompt templates are designed for custom input patterns, and Salesforce Prompt Builder allows specialists to define resources for the template. When the business wants to add a PDF as another input, the right declarative action is to add a file input/resource in the prompt template configuration, then use that resource in the prompt body. Option A is wrong because reindexing is a retrieval/search-index activity, not the standard way to add an input resource to a Flex template. Option C is wasteful and incorrect because an existing Flex template does not need to be discarded merely to add another input. The important design point is that Flex templates support custom resources and file inputs, so the existing template can be extended rather than rebuilt.

As documented in the AgentForce Prompt Template and BYOLLM (Bring-Your-Own-LLM) Deployment Guide, each prompt template references a specific LLM configuration by name and ID. When migrating components between environments (e.g., from sandbox to production), the referenced LLM must also exist in the target org with the exact same name and identifier.

If the LLM configuration is missing or named differently in production, the deployment fails, as the prompt template cannot resolve its model dependency.

Option A is incorrect because specifying a custom LLM type does not resolve the missing configuration issue. Option B is incorrect because BYOLLM is supported in production, provided it is correctly registered.

Therefore, the error occurs because the LLM name or configuration ID does not match between sandbox and production, making Option C the correct answer.

The correct answer is B because the issue is subagent misclassification caused by overlapping instructions or unclear routing boundaries. Agentforce routing depends on the agent understanding the purpose, scope, and availability of each subagent. If the billing and troubleshooting subagents are semantically competing, the correct fix is to tighten their descriptions, remove overlap, and use filters where deterministic gating is required. Option A is a weak keyword-ban strategy and will break on natural language variation. Option C creates rigid decision-tree routing and undermines the flexible, non-linear behavior expected from Agentforce agents. The best solution preserves autonomous reasoning while adding deterministic constraints where business routing must be protected. Filters and variables are specifically intended to control when subagents or actions are available.

The correct answer is C. In a multilingual RAG design, the embedding model must support semantic similarity across the languages involved in both the source content and user queries. Since the articles are in Spanish and users may ask questions in French or English, selecting the multilingual-e5-large embedding model broadly for the search index is the correct approach. Option A and Option B are too narrow because each excludes one of the languages in the complete requirement. The retriever does not simply match keywords; it compares vector representations of the query and indexed chunks. A multilingual embedding model improves cross-language retrieval by placing semantically similar text from different languages closer in vector space. Salesforce Data 360 search index guidance identifies multilingual content and embedding-model selection as key retrieval considerations.

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”

Comprehensive and Detailed Explanation From Exact Extract of AgentForce Documents:

According to the AgentForce Orchestration and Action Sequencing Guidelines in the official documentation, deterministic execution order is best achieved by using custom state variables and conditional logic rather than relying solely on LLM reasoning or topic instructions.

AgentForce’s orchestration framework allows developers to define variables that represent the successful completion of specific actions (e.g., “sessionsRetrieved,” “eligibilityVerified,” etc.). Subsequent actions can then include conditional filters that only allow execution if prior steps have been completed. This approach ensures that actions execute in a strict, logical sequence — preventing the LLM from reordering steps arbitrarily.

Option A (relying on topic instructions) provides guidance to the LLM but does not enforce execution order programmatically, which means errors can still occur if the reasoning engine interprets steps differently. Option C (priority and sequence indicators) assists in contextual selection but does not create dependency-based control between actions.

Therefore, per AgentForce best practices, the correct approach is Option B – using custom variables with conditional filters. This guarantees deterministic workflow sequencing, prevents premature action execution, and aligns with the “Action Dependency and Conditional Execution Model” described in the AgentForce Implementation Guide.

The correct answer is B because the requirement is to discover a recurring misclassification pattern across production sessions without manually reading transcripts. Agent Optimization is built for this observability use case. It extends session tracing capabilities with additional data structures that track session moments and user intent, allowing teams to understand intent clusters and recurring behavior patterns. Option A is too manual because querying raw session tracing data still requires analysis work and does not directly provide clustered intent insights. Option C is useful for predeployment or regression testing, but it does not analyze actual production sessions unless the test set already reflects the live problem. Salesforce documentation describes Agent Optimization as tracking session moments and user intent through additional DLOs and DMOs.

The correct answer is C because available when controls whether an action is visible to the reasoning engine for that reasoning cycle. If the action was hidden when the turn began, setting isVerified to true during that same turn does not retroactively expose the hidden action for immediate invocation. The action becomes available only when the next reasoning cycle starts and the guard condition evaluates against the updated variable state. Option A is dangerous because model intent never overrides an availability guard. Option B is wrong because treating action visibility as continuously re-evaluated inside the same turn would break deterministic gating. Salesforce documentation describes available when as a way to control flow based on state, and variables can be used in filters and action control.

To address security compliance concerns and provide visibility into the prompt text sent to the LLM, how it is masked, and the masked response, the Agentforce Specialist should recommend enabling the audit trail in the Einstein Trust Layer. This feature captures and logs the prompts sent to the large language model (LLM) along with the masking of sensitive information and the AI ' s response. This audit trail ensures full transparency and compliance with security requirements.

Option A (Einstein Shield Event logs) is focused on system events rather than specific AI prompt data.

Option B (debug logs) would not provide the necessary insight into AI prompt masking or responses.

For further details, refer to Salesforce ' s Einstein Trust Layer documentation about auditing and security measures.

Hybrid reasoning in Agent Script means combining flexible LLM-driven conversation with deterministic procedural control in the same agent logic. This is exactly why option C is correct. Salesforce describes Agent Script as supporting business-critical logic that executes reliably while allowing conversational elements to remain flexible. The - > syntax marks executable procedural logic, so steps such as identity verification can be enforced before account access. Option A is wrong because hybrid reasoning is not about using multiple LLMs at the same time. Option B is also wrong because hybrid reasoning is a language and execution model, not a separation of capabilities between Canvas View and Script View. The core exam point is deterministic enterprise workflow control plus LLM interpretation.

The hotel resort team needs an AI-generated guest summary with recommendations, displayed exclusively on the contact record page. Let’s assess the options.

Option A: Flow Model BuilderModel Builder in Salesforce creates custom predictive AI models (e.g., for scoring or classification) using Data Cloud or Einstein Platform data. It’s not designed for generating text summaries or embedding them on record pages, making it incorrect.

Option B: Agentforce BuilderAgent Builder in Agentforce Studio creates autonomous AI agents for tasks like lead qualification or customer service. While agents can provide summaries, they operate in conversational interfaces (e.g., chat), not as static content on a record page. This doesn’t meet the location-specific requirement, making it incorrect.

Option C: Prompt BuilderEinstein Prompt Builder allows creation of prompt templates that generate text (e.g., summaries, recommendations) using Generative AI. The template can pull data from contact records (e.g., activity preferences) and be embedded as a Lightning component on the contact record page via a Flow or Lightning App Builder. This ensures the summary is available only where specified, meeting the team’s needs perfectly and making it the correct answer.

Why Option C is Correct:

Prompt Builder’s ability to generate contextual summaries and integrate them into specific record pages via Lightning components aligns with the team’s requirements, as supported by Salesforce documentation.

The data scientist requires permissions for Einstein Studio (model management) and Prompt Builder (template creation). Note: " Einstein Studio " may be a misnomer for Data Cloud’s model management or a related tool, but we’ll interpret based on context. Let’s evaluate.

Option A: Prompt Template Manager and Prompt Template UserThere’s no distinct " Prompt Template Manager " or " Prompt Template User " permission set in Salesforce—Prompt Builder access is typically via " Einstein Generative AI User " or similar. This option lacks coverage for Einstein Studio/Data Cloud, making it incorrect.

Option B: Data Cloud Admin and Prompt Template ManagerThe " Data Cloud Admin " permission set grants access to manage models in Data Cloud (assumed as Einstein Studio’s context), including viewing and editing AI models. " Prompt Template Manager " isn’t a real set, but Prompt Builder creation is covered by " Einstein Generative AI Admin " or similar admin-level access (assumed intent). This combination approximates the needs, making it the closest correct answer despite naming ambiguity.

Option C: Prompt Template User and Data Cloud Admin " Prompt Template User " isn’t a standard set, and user-level access (e.g., Einstein Generative AI User) typically allows execution, not creation. The data scientist needs to create templates, so this lacks sufficient Prompt Builder rights, making it incorrect.

Why Option B is Correct (with Caveat):

" Data Cloud Admin " covers model management in Data Cloud (likely intended as Einstein Studio), and " Prompt Template Manager " is interpreted as admin-level Prompt Builder access (e.g., Einstein Generative AI Admin). Despite naming inconsistencies, this fits the requirements per Salesforce permissions structure.

The correct answer is B because Zero Copy Data Federation is designed for accessing external data without physically copying or ingesting that data into Data 360. This fits the requirement exactly: the data remains in the external system, storage duplication is avoided, and Salesforce can still use the connected data for Data 360-driven use cases. Option A is wrong because a semantic index supports meaning-based retrieval over indexed content, but it does not by itself solve the requirement to avoid duplication of structured external data. Option C is wrong because configuring a data stream imports or ingests data into Data 360, which contradicts the storage-cost and no-duplication requirement. Salesforce’s Zero Copy guidance states that external data can be accessed and used in Data 360 without duplicating it.

Before creating a Field Generation prompt template in Agentforce, the Specialist must ensure that the target field is available on a Dynamic Form-enabled Lightning page layout. Field Generation prompt templates work by embedding AI-generated suggestions directly into editable record fields on the Lightning record page. This functionality requires Dynamic Forms, which allow fields to be placed and managed as individual components on the Lightning page. Without Dynamic Forms enabled, the AI cannot surface suggestions directly into the field.Generation templates.

Why is Outbound Omni-Channel Flow the Correct Answer?

In Agentforce, when a service agent ' s conversation needs to be escalated to a human agent queue, Outbound Omni-Channel Flow is the appropriate tool to facilitate this process.

Key Features of Outbound Omni-Channel Flow in Agentforce:

Automates Escalation to a Human Agent Queue

It ensures that service requests are dynamically routed to the most appropriate human agent, based on availability, skills, and predefined business logic.

Seamless Transition from AI to Human Agents

When Einstein Copilot or another AI-powered assistant identifies a case that requires human intervention, Omni-Channel Flow automatically routes the conversation.

Ensures Proper Prioritization & Load Balancing

By leveraging Omni-Channel routing rules, the system assigns conversations efficiently, avoiding delays in customer service.

Integration with Agentforce and Service Cloud

Works directly with Salesforce Service Cloud to route cases to the appropriate agent queue.

Why Not the Other Options?

❌ B. Screen Flow

Screen Flow is used for interactive guided processes where users manually enter data in predefined steps.

It does not support automated case routing to human agents in real time.

❌ C. Prompt Flow

Prompt Flow is designed to enhance AI-generated responses and workflows rather than routing service agent interactions to human agents.

It lacks Omni-Channel integration, which is necessary for real-time queue management.

Agentforce Specialist References

The importance of using Omni-Channel Flow for routing AI-generated interactions to human agents is supported in the Agentforce Specialist exam objectives and documentation:

Salesforce AI Specialist Material: Covers the importance of Omni-Channel routing for managing AI and human agent interactions​.

Salesforce Instructions for the Certification: Mentions routing AI-driven cases to human agents using automated flows​.

Agentforce Tools Documentation: Highlights Omni-Channel capabilities in Service AI​.

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.

The correct answer is C because the requirement is built around the essential prompt elements of task, context, constraints, and format. The task is to summarize support case notes. The context is the customer issue, troubleshooting steps, and next actions. The constraints are the five-sentence limit, plain-language requirement, no jargon, and the exact phrase to use when no next action exists. The format controls how the final summary should be presented. Option A is incorrect because “LLM Clarity Score” is not a prompt construct. Option B is weaker because token limits are not the same as business constraints such as sentence count and required wording. Salesforce guidance recommends prompts that clearly cover task, context, format, and constraints.

When creating a custom action for Einstein Bots in Salesforce (including Agentforce), Action Instructions are critical for defining how the bot processes and executes the action. These instructions guide the bot on the logic to follow, such as API calls, data transformations, or conditional steps. Testing and iterating on the instructions ensures the bot understands how to handle dynamic inputs, external integrations, and decision-making.

Salesforce documentation emphasizes that Action Instructions directly impact the bot’s ability to execute workflows accurately. For example, poorly defined instructions may lead to incorrect API payloads or failure to parse responses. The Einstein Bot Developer Guide highlights that refining instructions is essential for aligning the bot’s behavior with business requirements.

In contrast:

Action Name (A) is a static identifier and does not affect functionality.

Action Input (B) defines parameters passed to the action but does not dictate execution logic.

Thus, iterating on Action Instructions (C) ensures the action performs as expected.

Universal Containers (UC) aims to leverage Agentforce for Sales to assist sales reps with AI-generated plans that provide guidance and steps for closing deals. Let’s evaluate the options based on Agentforce for Sales features.

Option A: Create Account PlanWhile account planning is valuable for long-term strategy, Agentforce for Sales does not have a specific " Create Account Plan " feature focused on closing individual deals. Account plans typically involve broader account-level insights, not deal-specific closure steps, making this incorrect for UC’s requirement.

Option B: Find Similar Deals " Find Similar Deals " is not a documented feature in Agentforce for Sales. It might imply identifying past deals for reference, but it doesn’t involve generating plans with guidance and steps for closing current deals. This option is incorrect and not aligned with UC’s goal.

Option C: Create Close PlanThe " Create Close Plan " feature in Agentforce for Sales uses AI to generate a detailed plan with actionable steps and guidance tailored to closing a specific deal. Powered by the Atlas Reasoning Engine, it analyzes deal data (e.g., Opportunity records) and provides reps with a roadmap to meet quotas. This directly meets UC’s requirement for AI-generated plans focused on deal closure, making it the correct answer.

Why Option C is Correct:

" Create Close Plan " is a specific Agentforce for Sales capability designed to help reps close deals with AI-driven plans, aligning perfectly with UC’s needs as per Salesforce documentation.

Agent Inspection is the best fit because the requirement is to examine complete end-to-end agent interactions, not merely view aggregate performance trends or optimize unresolved sessions. The question specifically mentions tracing the interaction from the first user request through final resolution, which requires inspection-level visibility into what the agent interpreted, which subagent or action path it followed, and what response quality was produced. Agent Insights would imply summarized analytics, while Agent Optimization is more focused on identifying improvement opportunities after sessions are analyzed. Salesforce’s Agentforce Session Tracing guidance explains that detailed interaction data is captured to provide a full view of agent behavior, which is exactly what this scenario requires.

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.

Universal Containers (UC) has concerns about data privacy when using Salesforce ' s generative AI features, particularly around preventing third-party LLMs from accessing or retaining their data. The Zero-Data Retention Policy in the Einstein Trust Layer is designed to address these concerns by ensuring that:

No data is used for training or product improvements by third-party LLMs.

No data is retained outside of the customer ' s Salesforce organization.

The LLM provider cannot access any customer data.

This policy aligns perfectly with UC’s requirements for keeping their data safe while leveraging generative AI capabilities.

Prompt Defense and Data Masking are also security features, but they do not directly address the concerns related to third-party data access and retention.

Salesforce Einstein Trust Layer Documentation: https://help.salesforce.com/s/articleView?id=sf.einstein_trust_layer.htm

Comprehensive and Detailed Explanation From Exact Extract:

The documentation “Find Similar Opportunities” states: “Matched opportunities have a status of Closed Won, a close date within 12 months of today, and aren’t deleted.” This clearly aligns with option B. The other options (A or C) do not match the published criteria (status of Closed Won within 12 months). Therefore option B is correct.

When a custom Agent action is not being prioritized correctly by the planner service, the root cause is often missing or improperly defined action dependencies. The planner service determines the execution order of actions based on dependencies defined in the action instructions. To resolve this, the Agentforce Specialist must explicitly specify dependent actions using their API names in the custom action’s configuration. This ensures the planner understands the sequence in which actions must be executed to meet business logic requirements.

Salesforce documentation highlights that dependencies are critical for orchestrating workflows in Einstein Bots and Agentforce. For example, if Action B requires data from Action A, Action A’s API name must be listed as a dependency in Action B’s instructions. The Einstein Bot Developer Guide states that failing to define dependencies can lead to race conditions or incorrect execution order.

In contrast:

Profiles or custom permissions (B) control access to the action but do not influence execution order.

LLM model provider and version (C) determine the AI model used for processing but are unrelated to the planner’s sequencing logic.

Comprehensive and Detailed Explanation From Exact Extract:

The documentation for prompt template types states that Flex templates allow you to define your own inputs when standard templates do not cover your scenario, and that Flex templates support multiple inputs (up to five). For example: “Flex Templates: generate content for business purposes not covered by other prompt template types, allowing you to define your own resources. … Maximum number of inputs in a Flex template = 5.” (Prompt Template Types)

Since UC wants to use data from five unrelated objects (which doesn’t fit a single object context) directly in a prompt template, the correct approach is to use a Flex template and supply the inputs from those objects. The other options (B or C) add unnecessary complexity or don’t align with the templatedesign paradigm.

Thus option A is correct.

When troubleshooting a copilot custom action using flow as the reference action type, enabling dynamic debugging within Copilot Builder ' s Dynamic Panel is the most effective way to identify the root cause. By turning on dynamic debugging, the Agentforce Specialist can see detailed logs showing both the inputs and outputs of the flow, which helps identify where the action might be failing or not delivering the expected results.

Option B, confirming selected actions and observing the Input and Output sections, is useful for monitoring flow configuration but does not provide the deep diagnostic details available with dynamic debugging.

Option C, verifying the user utterance and reviewing session event logs, could provide helpful context, but dynamic debugging is the primary tool for identifying issues with inputs and outputs in real time.

Salesforce Agentforce Specialist References:

To explore more about dynamic debugging in Copilot Builder, see: https://help.salesforce.com/s/articleView?id=sf.copilot_custom_action_debugging.htm

Comprehensive and Detailed Explanation From Exact Extract:

The Prompt Builder documentation shows that prompt templates can be invoked from Flows using a Flow Action. It describes “Call a prompt template from Flow” and “Flow Core Action: Prompt Template Actions.” While Invocable Apex (option A) could technically trigger templates, the standard, declarative, recommended approach is a Flow Action (option C). “Einstein for Flow” (option B) is not the standard naming used in this context. So option C is correct.

The scenario involves a customer service representative needing to cancel flights due to a weather alert and review existing Knowledge articles for guidance on canceling and rebooking. Agentforce provides capabilities to streamline such tasks. The most suitable option is Option B, which allows the agent to " execute tasks based on available actions " (e.g., canceling flights via a predefined action) while " answering questions using information from accessible Knowledge articles. " This capability leverages Agentforce’s ability to integrate Knowledge articles into the agent’s responses, enabling the representative to ask questions (e.g., “How do I cancel a flight?”) and receive AI-generated answers grounded in approved Knowledge content. Simultaneously, the agent can trigger actions (e.g., a Flow to update the custom object) to perform the cancellations, meeting all requirements efficiently.

Option A: Invoking a Flow to call external data and create a Knowledge article is unnecessary. The representative needs to review existing articles, not create new ones, and there’s no indication external data is required for this task.

Option B: This is correct. It combines task execution (canceling flights) with Knowledge article retrieval, aligning with the representative’s need to act and seek guidance from existing content.

Option C: Generating a new Knowledge article based on prompts is not relevant. The representative needs to use existing articles, not author new ones, especially in a time-sensitive weather alert scenario.

Option B best supports the representative’s workflow in Agentforce.

Salesforce Agentforce Documentation: " Knowledge Replies and Actions " (Salesforce Help: https://help.salesforce.com/s/articleView?id=sf.agentforce_knowledge_replies.htm & type=5)

Trailhead: " Agentforce for Service " (https://trailhead.salesforce.com/content/learn/modules/agentforce-for-service)

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

The correct answer is A. MCP is an open standard for connecting AI applications and agents to external tools, services, and data sources through a common protocol. That directly matches UC’s need to avoid building separate custom integrations for every enterprise system or local development environment. Option B is wrong because MCP does not replace RAG or store external data inside the model’s weights; it provides a standardized interface for accessing context and tools. Option C describes Agent-to-Agent delegation more closely than MCP. MCP is about context and tool connectivity between AI systems and external resources, while A2A-style protocols focus on negotiation and task delegation between independent agents. Salesforce describes MCP as a way to reduce custom integration effort and securely connect AI apps to external systems.

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 A because least privilege means granting only the minimum access required for the agent to perform the task. Since Opportunity access is restricted by a Private organization-wide default, the agent user needs the correct object permissions and record-level access through sharing rules or an equivalent sharing model. Option B is too broad because running without sharing can bypass intended record access controls and expose data beyond the business requirement. Option C is also excessive because changing the organization-wide default to Public Read Only weakens security for every user and process, not just this agent action. Salesforce’s Agentforce security guidance specifically recommends reviewing OWD, agent user permissions, and sharing rules to ensure proper record access.

Record Snapshots in Salesforce Prompt Builder leverage the data visible on the user ' s page layout for an object to ground the prompt. This means that the fields and related lists that are configured on the page layout directly influence the data included in the snapshot.

The Field Generation prompt template type is specifically designed to enable generative AI within the context of a Salesforce record field. To expose this functionality to an end-user, the Agentforce Specialist must associate the template with the form field on the Lightning page (B). This is accomplished using the Lightning App Builder:

The Agentforce Specialist first creates a custom field (often a Long Text Area or Rich Text Area) on the desired object to store the AI-generated output.

In the Lightning App Builder for the object ' s Record Page, the Specialist selects the field component.

In the properties panel for that field component, there is a setting (often a dropdown) to select an active Field Generation Prompt Template.

Once associated, an Einstein icon (or " Generate " button) appears next to the field on the record page, allowing the user to click it to run the prompt, review the AI-generated content, and then decide to use it to populate the field.

Options A and C (using Flows) are methods for calling prompt templates to automate the generation of content or to ground the prompt with more complex data (like related list information). However, for the Field Generation prompt template to be exposed directly to the user for on-demand generation and manual review (the intended user experience for this template type), it must be bound to the field itself on the Lightning Record Page.

Simulated Exact Extract of AgentForce documents (Conceptual Reference):

" The Field Generation prompt template is surfaced to the user via the Lightning Record Page. After the prompt template is created and activated in Prompt Builder, the Agentforce Specialist must edit the Lightning Record Page in the Lightning App Builder. The key step is to select the target field component and, within its property panel, assign the Field Generation Prompt Template from the available dropdown menu. This action binds the generative AI capability directly to the field, displaying the ' Generate ' button to the user to trigger the AI-assisted content creation upon the record. "

Simulated Reference: AgentForce Study Guide, Chapter 3: Prompt Builder, Section 3.2: Field Generation Deployment, p. 55.

The correct answer is B because the requirement is structured extraction, not creative generation. To reliably extract a product model number and quantity, the prompt should give clear instructions that describe exactly what to identify, how to format the extracted values, and how to behave when information is missing. Few-shot examples improve consistency by showing the model representative input-and-output patterns. Option A is wrong because open-ended questions increase variability and are better for exploratory responses, not precise extraction. Option C is wrong because higher temperature increases creativity and randomness, which is the opposite of what UC needs. Salesforce Prompt Builder guidance emphasizes clear prompt instructions, CRM grounding, and managing prompt templates for trusted generative AI outputs.

Universal Containers (UC) is implementing Service AI Grounding to enhance its customer service operations. They aim to ensure that AI-generated responses are grounded in the most relevant data sources and need to configure the system to include all supported objects for grounding.

Supported Objects for Service AI Grounding:

Case

Knowledge

Case Object:

Role in Grounding: Provides contextual data about customer inquiries, including case details, status, and history.

Benefit: Grounding AI responses in case data ensures that the information provided is relevant to the specific customer issue being addressed.

Knowledge Object:

Role in Grounding: Contains articles and documentation that offer solutions and information related to common issues.

Benefit: Utilizing Knowledge articles helps the AI provide accurate and helpful responses based on verified information.

Exclusion of Other Objects:

Case Notes and Case Emails:

Not Supported for Grounding: While useful for internal reference, these objects are not included in the supported objects for Service AI Grounding.

Reason: They may contain sensitive or unstructured data that is not suitable for AI grounding purposes.

Why Options A and C are Incorrect:

Option A (Case, Knowledge, and Case Notes):

Case Notes Not Supported: Case Notes are not among the supported objects for grounding in Service AI.

Option C (Case, Case Emails, and Knowledge):

Case Emails Not Supported: Case Emails are also not included in the list of supported objects for grounding.

The correct answer is B because a Knowledge-based Agentforce Data Library is the correct managed source for approved service and compliance content. Salesforce Knowledge already handles the article lifecycle, including publication state and article governance, while Agentforce Data Library makes that content searchable for AI grounding. Filtering to published articles prevents draft, archived, or outdated content from being used in customer-facing responses. Option A adds unnecessary Flow-based retrieval and bypasses the native semantic retrieval pattern. Option C may work for custom indexed content, but it is less efficient when the authoritative source is already Salesforce Knowledge. The clean architecture is to connect the data library to Knowledge, restrict the indexed scope, and allow the agent to retrieve semantically relevant approved articles.

In the Einstein Trust Layer, the toxicity scoring system is used to evaluate the safety level of content generated by AI, particularly to ensure that it is non-toxic, inclusive, and appropriate for business contexts. A toxicity score of 1 indicates that the content is deemed safe.

The scoring system ranges from 0 (unsafe) to 1 (safe), with intermediate values indicating varying degrees of safety. In this case, a score of 1 means that the generated content is fully safe and meets the trust and compliance guidelines set by the Einstein Trust Layer.

For further reference, check Salesforce’s official Einstein Trust Layer documentation regarding toxicity scoring for AI-generated content.

The AgentForce for Service Implementation Guide confirms that when automating customer service and complaint resolution, the correct solution is a Service Agent. The documentation states:

“Service Agents handle customer inquiries, complaints, and issue resolution workflows. They can automate actions such as offering credits, applying upgrades, and escalating severe cases to human support.”

Flex prompt templates are recommended for these scenarios, as they allow contextual control and personalization based on the complaint details.

Option A (Sales Agent) focuses on sales-related tasks like lead nurturing.

Option B (Custom Agent) could work but lacks the pre-built integrations and actions designed for service workflows.

Thus, Option C aligns with Salesforce’s best-practice model for customer issue automation.

References (AgentForce Documents / Study Guide):

AgentForce for Service Guide: “Automating Complaint Resolution”

AgentForce Prompt Template Handbook: “Using Flex Templates in Service Workflows”

AgentForce Study Guide: “Deploying Service Agents for Escalation and Resolution Scenarios”

The correct answer is B. A custom retriever controls which indexed data is searched and what fields are returned to the prompt or agent. If UC needs a summary field returned, the correct action is to update the retriever configuration, save the revised retriever version, and activate that version so the prompt template uses it. Option A is excessive and technically wrong because retriever versioning supports controlled updates rather than forcing a complete rebuild and deletion. Option C is wrong because default retrievers do not automatically return every useful field in the exact structure a business requires. For grounded AI, returned fields must be intentionally configured so the model receives the right concise context without unnecessary noise. Salesforce documents retriever customization and activation of retriever versions.

SOMA is correct because the company operates in one Salesforce instance and needs centralized governance, shared user context, and routing across specialized agents. Salesforce’s architecture guidance defines SOMA as multiple agents collaborating within one Salesforce org using shared governance and data, with a Supervisor or primary agent acting as the front door that routes work to specialist agents. Salesforce’s multi-agent orchestration guidance also describes a primary agent that routes tasks to best-fit specialist agents while preserving context so users do not repeat themselves. MOMA is for cross-org collaboration, so it adds unnecessary complexity here. MCP connects agents or models to tools and data sources; it is not the best architectural answer for native single-org multi-agent orchestration.

The AgentForce Action Sequencing and Deterministic Flow Guide explains that to ensure actions are executed in a specific and predictable order, administrators must explicitly define the order of actions in the topic setup. The documentation states:

“To achieve deterministic control, sequence the topic’s actions in the desired order of execution. This ensures that dependent actions, such as data retrieval followed by record creation, execute consistently and predictably.”

Option A (specifying the LLM provider) affects model behavior but not execution sequence.

Option B (custom variables and filters) controls conditional logic, not the order of execution.

Therefore, Option C — specifying the action order — ensures full deterministic control.

References (AgentForce Documents / Study Guide):

AgentForce Builder Guide: “Defining and Ordering Actions in Topics”

AgentForce Deterministic Logic Handbook

AgentForce Study Guide: “Ensuring Predictable Action Sequences”

Context of the QUESTION 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 References & 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.

For no-code implementations, Prompt Builder allows Agentforce Specialists to create prompt templates that dynamically ground responses in Salesforce CRM data (e.g., past purchases) and Data Cloud insights (e.g., product interests) without custom coding. The standard foundation model (e.g., Einstein GPT) can synthesize this data into summaries, leveraging structured and unstructured sources (e.g., email/phone transcripts). Fine-tuning (B) or custom models (C) require code and are unnecessary here, as the use case does not involve unique data patterns requiring model retraining.

UC wants insights into product and competitor mentions during sales calls, leveraging Einstein Conversation Insights. Let’s evaluate the options.

Option A: Enable Einstein Conversation Insights, connect a recording provider, assign permission sets, and customize insights with up to 25 products.Einstein Conversation Insights analyzes call recordings to identify keywords like product and competitor names. Setup requires enabling the feature, connecting an external recording provider (e.g., Zoom, Gong), assigning permission sets (e.g., Einstein Conversation Insights User), and customizing insights by defining up to 25 products or competitors to track. Salesforce documentation confirms the 25-item limit for custom keywords, making this the correct, precise answer aligning with UC’s needs.

Option B: Enable Einstein Conversation Insights, assign permission sets, define recording managers, and customize insights with up to 50 competitor names.There’s no " recording managers " role in Einstein Conversation Insights setup—integration is with a provider, not a manager designation. The limit is 25 keywords (not 50), and the option omits the critical step of connecting a provider, making it incorrect.

Option C: Enable Einstein Conversation Insights, enable sales recording, assign permission sets, and customize insights with up to 50 products. " Enable sales recording " is vague—Conversation Insights relies on external providers, not a native Salesforce recording feature. The keyword limit is 25, not 50, making this incorrect despite being closer than B.

Why Option A is Correct:

Option A accurately reflects the setup process and limits for Einstein Conversation Insights, meeting UC’s requirement per Salesforce documentation.

For a sales rep who may miss key details during long sales calls, the Agentforce Specialist should recommend the Call Summary feature. Call Summary uses Einstein Generative AI to automatically generate a concise summary of important points discussed during the call, helping the rep quickly review the key information they might have missed.

Call Explorer is designed for manually searching through call data but doesn ' t summarize.

Sales Summary is focused more on summarizing overall sales activity, not call-specific content.

For more details, refer to Salesforce ' s Call Summary documentation on how AI-generated summaries can improve sales rep productivity.

An Agentforce wants to include data from the response of an external service invocation (REST API callout) into a prompt template. The goal is to incorporate dynamic data retrieved from an external API into the AI-generated content.

Solution:

Use External Service Record Merge Fields

External Service Integration:

Definition: External Services in Salesforce allow the integration of external REST APIs into Salesforce without custom code.

Registration: The external service must be registered in Salesforce, defining the API ' s schema and methods.

External Service Record Merge Fields:

Purpose: Enables the inclusion of data from external service responses directly into prompt templates using merge fields.

Functionality:

Dynamic Data Inclusion: Allows prompt templates to access and use data returned from REST API callouts.

Merge Fields Syntax: Use merge fields in the prompt template to reference specific data points from the API response.

Implementation Steps:

Register the External Service:

Use External Services to register the REST API in Salesforce.

Define the API ' s schema, including methods and data structures.

Create a Named Credential:

Configure authentication and endpoint details for the external API.

Use External Service in Flow:

Build a Flow that invokes the external service and captures the response.

Ensure the flow outputs the necessary data for use in the prompt template.

Configure the Prompt Template:

Use External Service Record merge fields in the prompt template to reference data from the flow ' s output.

Syntax Example: {{flowOutputVariable.fieldName}}

Why Other Options are Less Suitable:

Option A (Convert the JSON to an XML merge field):

Irrelevance: Converting JSON to XML merge fields is unnecessary and complicates the process.

Unsupported Method: Salesforce prompt templates do not support direct inclusion of XML merge fields from JSON conversion.

Option C (Use “Add Prompt Instructions” flow element):

Purpose of Add Prompt Instructions:

Allows adding instructions to the prompt within a flow but does not facilitate including external data.

Limitation: Does not directly help in incorporating external service responses into the prompt template.

To access externally-hosted models, such as a large language model (LLM) hosted on AWS, the Model Builder in Salesforce is the appropriate tool. Model Builder allows teams to integrate and deploy external AI models into the Salesforce platform, making it possible to leverage models hosted outside of Salesforce infrastructure while still benefiting from the platform ' s native AI capabilities.

Option B, App Builder, is primarily used to build and configure applications in Salesforce, not to integrate AI models.

Option C, Copilot Builder, focuses on building assistant-like tools rather than integrating external AI models.

Model Builder enables seamless integration with external systems and models, allowing Salesforce users to use external LLMs for generating AI-driven insights and automation.

Salesforce Agentforce Specialist References:

For more details, check the Model Builder guide here: https://help.salesforce.com/s/articleView?id=sf.model_builder_external_models.htm

Why is " Sales rep users are missing the Use SDR Agent permission set " the correct answer?

If sales reps are unable to find the Agentforce Sales Development Representative (SDR) Agent, the most likely cause is missing permissions. The " Use SDR Agent " permission set is required for users to access and interact with the SDR Agent in Agentforce.

Key Considerations for This Issue:

Permission Set Restriction

Users must have the " Use SDR Agent " permission set to access Agentforce SDR in their Salesforce environment.

If they lack this permission, the SDR Agent will not appear in their interface.

Agentforce Role-Based Access Control

Agentforce assigns specific permissions based on user roles.

Sales reps require explicit permission to access the SDR Agent.

Fixing the Issue

The Salesforce Admin should assign the " Use SDR Agent " permission set to all relevant sales reps.

This is done in Setup → Permission Sets → Assign to Users.

Why Not the Other Options?

❌ A. Sales rep users ' profiles are missing the Allow SDR Agent permission.

Incorrect because " Allow SDR Agent " is not a standard permission setting in Agentforce.

Permission is granted via permission sets, not profile-level settings.

❌ B. Sales rep users do not have access to the SDR Agent object.

Incorrect because there is no separate " SDR Agent object " in Salesforce.

SDR Agents are AI-driven features, not standard CRM objects that require object-level access.

Agentforce Specialist References

Salesforce AI Specialist Material confirms that users require specific permission sets to access Agentforce SDR Agents​.

Salesforce Instructions for Certification highlight the role of permission sets in controlling Agentforce access​.

The correct answer is C. In Agent Script, listing a tool in the reasoning.actions block exposes it to the reasoning engine as a callable tool. Salesforce documentation states that tools in reasoning.actions are executable functions the LLM can choose to call based on the tool description and current context. That is not deterministic enough for a mandatory eligibility check. By contrast, Salesforce’s Agent Script action reference states that to ensure an action runs every time a subagent runs, the specialist should use run @actions. <</b> action_name > in the reasoning block. Therefore, run is the correct mechanism for guaranteed execution, while reasoning.actions provides LLM-selectable tool availability.