For Field Generation prompt templates to display the Sparkle icon (indicating AI-generated content), the target field must be explicitly associated with the prompt template on the Lightning page layout. Even if the prompt template is activated, failing to add the field to the page layout and link it to the template will result in the field behaving as a standard field. Salesforce documentation emphasizes that page layout configuration is mandatory to enable AI-driven field interactions.
* Reactivating the layout (A) is unnecessary unless the layout itself was modified after activation.
* Case objects are supported for Field Generation (B is incorrect).
Reference:
Salesforce Help Article: Configure Field Generation Prompt Templates ("Associating Fields with Page Layouts" section).
Einstein GPT Implementation Guide: "Enabling AI-Generated Fields in Lightning Pages."

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.

Comprehensive and Detailed In-Depth Explanation:
UC's issue is that theirfile upload-based Data Library(where PDFs or documents are uploaded and indexed into Data Cloud's vector database) is returning outdated training content in AI responses. To improve relevancy by ensuring only current documents are retrieved, the most effective solution is toconfigure a custom retriever with a filter(Option B). In Agentforce, a custom retriever allows UC to define specific conditions-such as a filter on a "Last Modified Date" or similar timestamp field-to limit retrieval to documents updated within a recent period (e.g., last 6 months). This ensures the AI grounds its responses in the most current content, directly addressing the problem of outdated documents without requiring a complete overhaul of the data source.
* Option A: Switching to aKnowledge-based Data Library(using Salesforce Knowledge articles) could work, as Knowledge articles have versioning and expiration features to manage recency. However, this assumes UC's training content is already in Knowledge articles (not PDFs) and requires migrating all uploaded files, which is a significant shift not justified by the question's context. File-based libraries are still viable with proper filtering.
* Option B: This is the best corrective action. A custom retriever with a date filter leverages the existing file-based library, refining retrieval without changing the data source, making it practical and targeted.
* Option C: Relying on periodic re-uploads with the default retriever is passive and inefficient. It doesn't guarantee recency (old files remain indexed until manually removed) and requires ongoing manual effort, failing to proactively solve the issue.
Option B provides a precise, scalable solution to ensure content relevancy in UC's AI-driven training system.
:
Salesforce Agentforce Documentation: "Custom Retrievers for Data Libraries" (Salesforce Help:https://help.
salesforce.com/s/articleView?id=sf.agentforce_custom_retrievers.htm&type=5) Salesforce Data Cloud Documentation: "Filter Retrieval for AI" (https://help.salesforce.com/s/articleView?
id=sf.data_cloud_retrieval_filters.htm&type=5)
Trailhead: "Manage Data Libraries in Agentforce" (https://trailhead.salesforce.com/content/learn/modules
/agentforce-data-libraries)

Comprehensive and Detailed In-Depth Explanation:
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: 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: Agent 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.
References:
Salesforce Agentforce Documentation: Prompt Builder > Embedding Prompts- Details placement on record pages.
Trailhead: Build Prompt Templates in Agentforce- Covers summaries from object data.
Salesforce Help: Customize Record Pages with AI- Confirms Prompt Builder integration.

Agentforce Sales Agent provides real-time insights and AI-powered recommendations, which are designed to streamline the sales processand help sales representatives focus on key tasks toincrease conversion rates. It offers features like lead scoring, opportunity prioritization, and proactive recommendations, ensuring that sales teams can interact with customers efficiently and close deals faster.
* Option A: While tracking customer interactions is beneficial, it is only part of the broader capabilities offered by Agentforce Sales Agent and is not the primary objective for improving real-time productivity.
* Option B: Agentforce Sales Agent does not automate the entire sales process but provides actionable recommendations to assist the sales team.
* Option C: This aligns with the tool's core purpose of enhancing productivity and driving sales success.
Reference:
"Einstein Next Best Action for Sales Teams | Salesforce Trailhead" .