Explanation:

Prompt Builder offers two primary supported methods for a business stakeholder to bring Data Cloud data into a prompt template for grounding:

Data Cloud related lists — When a Data Cloud object is related to the primary object used in the prompt template (e.g., related to a Case, Account, or Contact record), you can pull in fields via related list merge fields directly in the template.

Prompt-initiated Flows — A Flow can be invoked from within the prompt template to query Data Cloud (e.g., using a Data Cloud query or DMO lookup within the flow), and the retrieved data is passed back into the prompt as grounding context.

These two methods represent the standard, supported approaches for a business stakeholder (a less technical persona) working within Prompt Builder to access Data Cloud data without needing deep technical setup like retrievers or vector search indexes (which are more relevant to unstructured/semantic search scenarios, typically handled by more technical roles like Agentforce Specialists).

Why the other options are incorrect:

A: While Flex templates can reference DMOs directly, this is a more advanced/technical capability typically used by an Agentforce Specialist or technical builder setting up structured grounding — not necessarily the primary method being described for a general business stakeholder. Including it here makes the option overly broad relative to what the question is testing (the standard, stakeholder-accessible methods).

C: External APIs are not the mechanism for accessing Data Cloud data within Prompt Builder — Data Cloud data is natively accessible within the Salesforce/Data Cloud ecosystem via related lists, DMOs, and flows. There's no need (or supported pattern) to import Data Cloud data via external APIs for this purpose.

Reference:
Salesforce Prompt Builder documentation — "Ground Prompts with Data Cloud" (related lists and flow-based grounding for Data Cloud objects).

Explanation:

When grounding a prompt template using related lists in Salesforce Prompt Builder, not all related lists are supported. Specifically:

The User related list is not supported for grounding in prompt templates.
This is due to security model constraints and data structure limitations in how user data is accessed and exposed to AI models via the Einstein Trust Layer.

❌ Why the other options are incorrect:

A. The User related list should have View All access
Even if full access is granted, this related list still isn't supported for grounding in prompt templates. So this access setting has no effect.

B. The User related list needs to be included on the record page
Including a related list on the record page is often necessary for visibility, but it has no impact on grounding availability. And again, the User related list is unsupported, so its presence on the layout doesn’t matter.

🔗 Reference:
Salesforce Help — Prompt Builder Related List Grounding
Prompt Template Limitations — Salesforce Docs

Explanation:

Einstein Lead Follow-Up is designed specifically to help sales teams engage with leads at scale using AI-generated, personalized emails based on:

Lead data
Past interactions
CRM context

It’s tailored to automate and streamline outreach with hyper-relevant messaging, making it the best solution for a sales manager who needs to contact many leads efficiently and effectively.

A. Einstein Sales Assistant
❌ Incorrect – This feature helps sales reps prioritize work, get reminders, and receive insights, but it doesn't generate communications at scale or handle personalized follow-up automatically.

B. Prompt Builder
❌ Incorrect – Prompt Builder is a tool for creating custom AI prompts, mainly for developers or admins building AI use cases. It’s not a ready-to-use lead follow-up solution for sales managers.

Explanation:

Universal Containers has two distinct requirements: first, to limit the data library's knowledge source to only public articles for grounding; and second, to provide source transparency by showing which articles the AI used for its response. These are two separate but common configuration settings within the Einstein Agent setup for data management and user trust.

✅ Correct Option: A

A. In the data library setting window, under Knowledge Settings, enable Use Public Knowledge Article and select Show sources:
This is the correct combination. The "Use Public Knowledge Article" setting explicitly restricts the grounding of the agent's responses to articles with a Public knowledge status. The "Show sources" setting, when enabled, instructs the agent to cite the specific knowledge articles it used to formulate its answer in the conversation thread.

❌ Incorrect Options:

B. In the data library setting window, under Knowledge Settings, enable Use Public Knowledge Article. It is not possible to display articles that the LLM grounded its response in:
This is incorrect because the first part is right, but the second part is false. Agentforce does have a built-in "Show sources" feature designed specifically for this purpose, making source citation a standard and configurable capability.

C. Use Data Categories to categorize publicly available articles to index. Sources are automatically displayed when knowledge articles are categorized as Public:
This is misleading. While Data Categories can be used for filtering, the "Public" filter for indexing is controlled by the Knowledge Status (e.g., Draft, Online, Archived, Public), not by a data category. Furthermore, source display is not automatic; it must be explicitly enabled via the "Show sources" setting.

Reference:
Salesforce Help: Configure a Data Library for Grounding

Explanation:

Summary:
Cloud Kicks needs to connect its custom-built website chat interface directly to an Einstein Agent. This is a classic custom integration scenario where an external application (the website) must be able to send messages to and receive responses from the agent's backend services. A secure, programmatic interface is required for this real-time communication.

✅ Correct Option: C

C. Agent API:
This is the correct framework for this task. The Agent API provides a set of REST endpoints that allow any external custom application (like a website, mobile app, or third-party system) to initiate and manage conversations with an Einstein Agent. It is the standard way to build a custom chat interface.

❌ Incorrect Options:

A. Agent-to-Agent (A2A):
This protocol is used for communication between two different Einstein Agents, allowing them to collaborate or transfer conversations. It is not designed for connecting a custom customer-facing website to a single agent.

B. Model Context Protocol (MCP):
MCP is a standard for connecting LLMs to external data sources and tools (like APIs and databases). It is used to enhance an agent's capabilities with real-time data, not as the primary communication channel between a website and the agent service itself.

Reference:
Salesforce Help: Agent API