Context of the Question

Universal Containers (UC) has a strict change management process that requires all possible configuration be completed in a sandbox and deployed to Production.

Einstein Generative AI is already enabled in Production, and the “Einstein Work Summaries” permission set is already available in Production.

The Agentforce Specialist needs to configure Work Summaries for Enhanced Messaging in the sandbox.

What Can Actually Be Deployed from Sandbox to Production?

Custom Fields: Metadata that is easily created in sandbox and then deployed.

Quick Actions: Also metadata-based and can be deployed from sandbox to production.

Layout Components: Page layout changes (such as adding the Wrap Up component) can be added to a change set or deployment package.

Why Option C is Correct

No Need to Turn on Einstein in Sandbox for Deployment: Einstein Generative AI is already enabled in Production; turning it on in the sandbox is typically a manual step if you want to test, but that step itself is not “deployable” in the sense of metadata.

Permission Set Assignments (as in Option A) are not deployable metadata. You can deploy the Permission Set itself but not the specific user assignments. Since the question specifically asks “Which other configuration steps should be taken in the sandbox that can be deployed to the production org?”, user assignment is not one of them.

Why Not Option A or B?

Option A: Mentions creating permission set assignments for agents. This cannot be directly deployed from sandbox to Production, as permission set assignments are user-specific and considered “data,” not metadata.

Option B: Mentions “Turn on Einstein.” But Einstein Generative AI is already enabled in Production. Additionally, “Turning on Einstein” is typically an org-level setting, not a deployable metadata item.

ConclusionThe main deployable items you can reliably create and test in a sandbox, and then migrate to Production, are:

Custom Fields (Issue, Resolution, Summary).

A Quick Action that updates those fields.

Page Layout Change to include the Wrap Up component.

Therefore, Option C is correct and focuses on actions that are truly deployable as metadata from a sandbox to Production.

Salesforce Agentforce Specialist References & Documents

Salesforce Trailhead: Work Summaries with Einstein GPTProvides an overview of how to configure Work Summaries, including the need for custom fields, quick actions, and UI components.

Salesforce Documentation: Deploying Metadata Between OrgsExplains what can and cannot be deployed via change sets (e.g., custom fields, page layouts, quick actions vs. user permission set assignments).

Salesforce Agentforce Specialist Study GuideOutlines which Einstein Generative AI and Work Summaries configurations are deployable as metadata.

To generate personalized emails using LLMs while reusing templates:

Sales Email Prompt Template Type (Option C): Designed specifically for generating dynamic email content by combining LLMs with structured templates. It allows admins to define placeholders (e.g., customer name, product details) and reuse templates across scenarios.

Option A: Standard email templates lack LLM integration and dynamic personalization.

Option B: " t field Generation " is not a valid Salesforce prompt template type.

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

Context of the QuestionUniversal Containers (UC) wants to automatically populate the Description field on the Account object. The AI-driven solution must generate textual data and write it directly into a field.

Field Generation Prompt Template

Primary Use Case: A Field Generation prompt template is specifically designed to create or fill in fields on a record with AI-generated text.

Auto-population: By configuring a Field Generation prompt template, admins can define the instructions, data inputs, and desired output for the AI. The resulting text then populates the specified field, such as the Account Description.

Why Not Flex or Sales Email Prompt Templates?

Flex Prompt Template: Used to combine or manipulate data across objects, merges, or references from multiple sources in more advanced, flexible prompts. Typically not the go-to for straightforward text generation on a single field.

Sales Email Prompt Template: Focused on drafting or summarizing emails for sales reps (like crafting outreach or follow-up messages). This template is not specifically built to populate a field on a record.

ConclusionFor automatically populating the Description field with AI-generated content, the Field Generation prompt template (Option A) is the correct choice.

Salesforce Agentforce Specialist References & Documents

Salesforce Documentation: Prompt Template TypesExplains various template types (Field Generation, Flex, Email, etc.) and their typical use cases.

Salesforce Agentforce Specialist Study GuideHighlights Field Generation prompt templates for populating or updating record fields with AI-generated text.

To ground a sales email on Opportunity Products, Events near the customer, and Tone and voice examples, the Agentforce Specialist should use a prompt-initiated flow. This flow can dynamically fetch the necessary data from related records in Salesforce and ground the generative AI output with contextually accurate information.

Option B (flex template) does not provide the ability to fetch dynamic data from Salesforce records automatically.

Option C (manual insertion) would not allow for the dynamic and automated grounding of data required for custom prompts.

Refer to Salesforce documentation on flows and grounding for more details on integrating data into custom prompt templates.

The correct answer is C because the agent must retrieve from more than one grounding source: company-specific PDFs and a comprehensive Knowledge base. An ensemble retriever is appropriate when multiple retrievers or multiple indexed sources must be combined into one retrieval strategy. That lets the Service Agent search across both unstructured document content and Knowledge content without forcing the specialist to choose only one source. An individual retriever is designed for a single retrieval target, so it is too narrow for this requirement. “Dynamic retriever” is not the best match for the stated need because the issue is not runtime source selection; it is combining multiple authoritative sources. Salesforce guidance describes custom retrievers as supporting more data source patterns, including ensemble retrievers, for Agentforce Data Library use cases.

The correct answer is B. Once unstructured content has been chunked, vectorized, and indexed in Data 360, the prompt template should use a retriever to search that indexed content and return the most relevant passages for grounding. A data lake object or data model object is part of the data architecture, but the prompt template does not directly use those objects as the retrieval mechanism for RAG. Salesforce documentation states that retrievers are used in prompt templates to search indexed Data 360 knowledge and return relevant information. Salesforce Trailhead also explains that the prompt template invokes the retriever, vectorizes the query, retrieves matching indexed content, and inserts that retrieved information into the prompt before it is sent to the LLM.

UC is deploying an Agentforce Service Agent with multiple topics and actions to production. Let’s assess deployment considerations.

Option A: Deploy agent components without a test run in staging, relying on production data for reliable results. Sandbox configuration alone ensures seamless production deployment.Skipping staging tests is risky and against best practices. Sandbox configuration doesn’t guarantee production success without validation, making this incorrect.

Option B: Ensure all dependencies are included, Apex classes meet 75% test coverage, and configuration settings are aligned with production. Plan for version management and post-deployment activation.This is a comprehensive approach: dependencies (e.g., flows, Apex) must be deployed, Apex requires 75% coverage, and production settings (e.g., permissions, channels) must align. Version management tracks changes, and post-deployment activation ensures controlled rollout. This aligns with Salesforce deployment best practices for Agentforce, making it the correct answer.

Option C: Deploy flows or Apex after agents, topics, and Agent Actions to avoid deployment failures and potential production agent issues requiring complete redeployment.Deploying components separately risks failures (e.g., actions needing flows failing). All components should deploy together for consistency, making this incorrect.

Why Option B is Correct:

Option B covers all critical deployment considerations for a robust Agentforce rollout, as per Salesforce guidelines.

The AgentForce Security and Deterministic Logic Guide specifies that sensitive actions must be gated through conditional filters linked to verification variables, not through natural language. It states: “For any process requiring secure, deterministic access, create a custom variable (e.g., IsCustomerVerified) that stores the verification status as a Boolean. Apply a filter expression to all protected actions (e.g., IsCustomerVerified = true). This ensures the LLM cannot bypass or alter access logic.”

This configuration ensures security and determinism because the execution of sensitive actions is programmatically enforced, not dependent on the LLM’s understanding.

Option A is incorrect because natural language-based checks are non-deterministic.

Option B relies solely on topic instructions, which can be ignored or misinterpreted by the LLM.

Therefore, Option C is the only solution that provides deterministic, system-enforced access control.

References (AgentForce Documents / Study Guide):

AgentForce Security Configuration Guide: “Using Conditional Filters for Deterministic Access”

AgentForce Implementation Handbook: “Verification Variables and Secure Action Flow”

AgentForce Study Guide: “Protecting Sensitive Data in AI Workflows”

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.