To integrate inferences from an XGBoost model into Salesforce's Data Cloud as a stand-alone Data Model Object (DMO):

Create the Serving Endpoint in Databricks:

The serving endpoint is necessary to make the trained model available for real-time inference. Databricks provides tools to host and expose the model via an endpoint.

Configure the Model Using Model Builder:

After creating the endpoint, the Agentforce Specialist should configure it within Einstein Studio's Model Builder, which integrates external endpoints with Salesforce Data Cloud for processing and storing inferences as DMOs.

Option B: Serving endpoints are not created in Einstein Studio; they are set up in external platforms like Databricks before integration.

Option C: A Python SDK connector is not used to bring model inferences into Salesforce Data Cloud; Model Builder is the correct tool.

The Agentforce Data Library enhances AI accuracy by grounding responses in curated, indexed data. Let’s assess the scenarios.

Option A: When the AI agent must provide answers based on a curated set of policy documents that are stored, regularly updated, and indexed in the data library.The Data Library is designed to store and index structured content (e.g., Knowledge articles, policy documents) for semantic search and grounding. It excels when an agent needs accurate, up-to-date responses from a managed corpus, like policy documents, ensuring relevance and reducing hallucinations. This is a prime use case per Salesforce documentation, making it the correct answer.

Option B: When the AI agent needs to combine data from disparate sources based on mutually common data, such as Customer Id and Product Id for grounding.Combining disparate sources is more suited to Data Cloud’s ingestion and harmonization capabilities, not the Data Library, which focuses on indexed content retrieval. This scenario is less aligned, making it incorrect.

Option C: When data is being retrieved from Snowflake using zero-copy for vectorization and retrieval.Zero-copy integration with Snowflake is a Data Cloud feature, but the Data Library isn’t specifically tied to this process—it’s about indexed libraries, not direct external retrieval. This is a different context, making it incorrect.

Why Option A is Correct:

The Data Library shines in curated, indexed content scenarios like policy documents, improving agent accuracy, as per Salesforce guidelines.

To implement an AI-powered customer service agent that retrieves proprietary policy documents (stored as PDFs) and ensures responses are grounded in approved company data, UC must first establish a foundation for the AI to access and use this data. The Agentforce Data Library (Option A) is the correct starting point. A Data Library allows UC to upload PDFs containing policy documents, index them into Salesforce Data Cloud’s vector database, and make them available for AI retrieval. This setup ensures the agent can perform Retrieval-Augmented Generation (RAG), grounding its responses in the specific, approved content from the PDFs rather than relying on generic LLM knowledge, directly meeting UC’s requirements.

Option B: Expanding the AI agent’s scope to search all Salesforce records is too broad and unnecessary at this stage. The requirement focuses on PDFs with policy documents, not all Salesforce data (e.g., cases, accounts), making this premature and irrelevant as a first step.

Option C: "Add the files to the content, and then select the data library option" is vague and not a precise process in Agentforce. While uploading files is part of setting up a Data Library, the phrasing suggests adding files to Salesforce Content (e.g., ContentDocument) without indexing, which doesn’t enable AI retrieval. Setting up the Data Library (A) encompasses the full process correctly.

Option A: This is the foundational step—creating a Data Library ensures the PDFs are uploaded, indexed, and retrievable by the agent, fulfilling both retrieval and grounding needs.

Option A is the correct first step for UC to achieve its goals.

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: "Ground AI Responses with Data Cloud" (https://help.salesforce.com/s/articleView?id=sf.data_cloud_agentforce.htm &type=5)

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.

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

For improving sales operations efficiency, Einstein Studio is ideal for creating AI-powered models that can predict outcomes based on data. One of the most valuable use cases is predicting customer lifetime value, which helps sales teams focus on high-value accounts and make more informed decisions. Customer lifetime value (CLV) predictions can optimize strategies around customer retention, cross-selling, and long-term engagement.

Option B is the correct choice as predicting customer lifetime value is a well-established use case for AI in sales.

Option A (customer sentiment) is typically handled through NLP models, while Option C (product popularity) is more of a marketing analysis use case.

Salesforce Einstein Studio Use Case Overview: https://help.salesforce.com/s/articleView?id=sf.einstein_studio_overview

As outlined in the AgentForce External Services and Prompt Flow Integration Guide, when data is retrieved from a registered external service via REST API, the response payload is stored as External Service Records. These records can then be referenced dynamically within prompt templates through External Service Record merge fields.

This approach allows the large language model (LLM) to use the fetched data as contextual grounding during prompt execution, ensuring that generated responses are accurate and consistent with the latest API results.

Option B is incorrect because AgentForce does not use XML merge fields for API responses; JSON data is automatically mapped to object structures. Option C is also incorrect — the “Add Prompt Instructions” element modifies prompt context or tone but does not pass external data for merge use.

Therefore, the correct method is Option A – Use External Service Record merge fields, ensuring the external service data is directly available for prompt templates.

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 AgentForce Event and Logging Configuration Guide states that enabling “Enrich event logs with conversation data” allows administrators to capture session-level details, including both user inputs and agent responses. The documentation explains: “When this setting is enabled, conversation transcripts, user messages, and agent responses are appended to the event logs for improved visibility and troubleshooting.”

This provides a comprehensive record for analytics, training, and quality review. It does not, however, track user click paths (Option A) or generate aggregated historical reports across all time periods automatically (Option C).

Therefore, Option B is correct, as it directly reflects the documented functionality of the conversation data enrichment feature within AgentForce configuration.

References (AgentForce Documents / Study Guide):

AgentForce Configuration and Monitoring Guide: “Enrich Event Logs with Conversation Data”

AgentForce Data and Analytics Study Notes

AgentForce Implementation Handbook: “Session and Conversation Log Management”

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.