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

The AgentForce Inter-Agent Communication and Security Configuration Guide specifies that when sensitive identity data (like a verified customer ID) must be shared between agents, the correct approach is to use the 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.

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

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

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

Service AI Grounding retrieves data from Salesforce objects to ground AI-generated responses. Key considerations:

Field Types: Standard Service AI Grounding supports String and Text Area fields. Custom rich text fields (e.g., RichTextArea) are not supported, making Option B correct.

Objects: While Service AI Grounding primarily uses Case and Knowledge objects (Option A), the limitation here is the field type, not the object.

Visibility: Service AI Grounding respects user permissions and sharing settings unless overridden (Option C is incorrect).

When Universal Containers creates a new Sales Email prompt template using the " Save As " function, missing hyperparameters can result in different outputs. To ensure the new prompt produces comparable results to the standard Sales Email prompt, the Agentforce Specialist should manually add the necessary hyperparameters to the new template.

Hyperparameters like Temperature, Frequency Penalty, and Presence Penalty directly affect how the AI generates responses. Ensuring that these are consistent with the standard template will result in similar outputs.

Option A (Model Playground) is not necessary here, as it focuses on fine-tuning models, not adjusting templates directly.

Option C (Reverting to the standard template) does not solve the issue of customizing the prompt template.

For more information, refer to Prompt Builder documentation on configuring hyperparameters in custom templates.

To create a digest of account action plans using the generative API feature, Universal Containers should use the REST API. The REST API is ideal for integrating Salesforce with external systems and enabling interaction with Salesforce data, including generative capabilities like creating summaries or digests. It supports modern web standards and is suitable for flexible, lightweight interactions between Salesforce and legacy systems.

Metadata API is used for retrieving and deploying metadata, not for data operations like generating summaries.

SOAP API is an older API used for integration but is less flexible compared to REST for this specific use case.

For more details, refer to Salesforce REST API documentation regarding using REST for data integration and generating content.

The required agent type is the Service Agent (C). The core function described—answering questions from the knowledge base—is the primary task of a Service Agent, which is designed for self-service support and knowledge article retrieval. Although the requirement also includes the ability to submit a new Lead, Service Agent models are highly configurable to include custom actions, such as a " Create Lead " action, using Agentforce Builder. Furthermore, the Service Agent type is intended to be deployed to external-facing Experience Cloud sites to provide support to external authenticated users, such as partners. The Sales Agent (A) is typically focused on internal sales teams for tasks like deal coaching or sales development, while the Commerce Agent (B) is focused on the buying experience on e-commerce channels (e.g., product discovery, personalized shopping). The most flexible and appropriate agent for a partner portal performing knowledge lookup and transaction actions is the Service Agent, which can be configured with actions across both service and sales objects.

Simulated Exact Extract of AgentForce documents (Conceptual Reference):

" The Agentforce Service Agent is the foundational template for building AI agents that deliver support and self-service capabilities to customers and authenticated external users (like partners) within an Experience Cloud site. Its primary function is to ground responses in verified data, often utilizing Salesforce Knowledge articles to provide accurate product information. Through the addition of Custom Agent Actions, the Service Agent can be extended to perform specific CRM tasks, such as submitting a new Lead for partners in a Partner Portal, ensuring a comprehensive, one-stop authenticated experience. "

Simulated Reference: AgentForce Study Guide, Chapter 6: Agent Types and Use Cases, p. 112.

When refining Agent custom action instructions, it is considered best practice to provide examples of user messages that are expected to trigger the action. This helps ensure that the custom action understands a variety of user inputs and can effectively respond to the intent behind the messages.

Option B (consistent phrases) can improve clarity but does not directly refine the triggering logic.

Option C (specifying a persona) is not as crucial as giving examples that illustrate how users will interact with the custom action.

For more details, refer to Salesforce ' s Agent documentation on building and refining custom actions.

Universal Containers (UC) has deployed an Agentforce Service Agent on its website, but it’s failing to provide answers from Salesforce Knowledge articles. Let’s troubleshoot the issue.

Option A: The Agentforce Service Agent user is not assigned the correct Agent Type License.There’s no " Agent Type License " in Salesforce—agent functionality is tied to Agentforce licenses (e.g., Service Agent license) and permissions. Licensing affects feature access broadly, but the specific issue of not retrieving Knowledge suggests a permission problem, not a license type, making this incorrect.

Option B: The Agentforce Service Agent user needs to be created under the standard Agent Knowledge profile.No " standard Agent Knowledge profile " exists. The Agentforce Service Agent runs under a system user (e.g., " Agentforce Agent User " ) with a custom profile or permission sets. Profile creation isn’t the issue—access permissions are, making this incorrect.

Option C: The Agentforce Service Agent user was not given the Allow View Knowledge permission set.The Agentforce Service Agent user requires read access to Knowledge articles to ground responses. The " Allow View Knowledge " permission (typically via the " Salesforce Knowledge User " license or a permission set like " Agentforce Service Permissions " ) enables this. If missing, the agent can’t access Knowledge, even if articles are indexed, causing the reported failure. This is a common setup oversight and the likely issue, making it the correct answer.

Why Option C is Correct:

Lack of Knowledge access permissions for the Agentforce Service Agent user directly prevents retrieval of article content, aligning with the symptoms and Salesforce security requirements.

According to the official AgentForce Prompt Template Design Guide, when extracting specific data such as customer name, phone number, and case number from unstructured text, the best practice is to use well-defined output instructions and examples. The documentation specifies: “To ensure the LLM produces consistent and precise outputs, prompts must include explicit output formatting instructions and examples that demonstrate the desired structure.”

AgentForce guidance emphasizes structured output control to prevent the LLM from adding conversational or extraneous text. It states: “Always define your output schema clearly — for example, specify JSON or key-value pairs — and provide one or more examples of what the model should return. This ensures the model responds only with structured data and not natural language.”

Option A (“Ask the LLM to extract and only output important information”) is too vague and can still produce variable or verbose responses. Option C (“Ensure the LLM has been told to only use name value pairs”) is partially correct but incomplete without clear formatting and example output. Therefore, Option B is the correct choice as it aligns with AgentForce’s documented standards for prompt accuracy and reliability.

References (AgentForce Documents / Study Guide):

AgentForce Prompt Engineering Best Practices Guide

AgentForce Developer Study Guide: “Defining Structured Outputs in Prompt Templates”

AgentForce Technical Documentation: “Using Output Instructions and Examples for LLM Control”