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.

When a flow is invoked via a custom Agent action, its data access depends on the flow’s  runtime configuration , not system mode by default. Salesforce flows can be configured to respect the running user’s permissions and sharing settings:

If the flow is set to  " Run as the User Who Launched the Flow "  (enabled in Flow Settings), it adheres to the user’s permissions, field-level security (FLS), and sharing rules.

Option C is incorrect  because flows do not always run in system mode unless explicitly configured to do so.

Option A is misleading  because " with sharing " is an Apex concept, not a flow setting. Flows use runtime settings like FLS and sharing enforcement.

References:

Salesforce Help:  Flow Runtime and Security Context

Flow Settings: " Run with User Permission and Field-Level Security " ensures data access aligns with the user’s permissions.

Customer churn prediction is the best use case for Model Builder in addressing Universal Containers ' concerns about increasing customer contract cancellations. By implementing a model that predicts customer churn, UC can proactively identify customers who are at risk of canceling and take action to retain them before they decide to terminate their contracts. This functionality allows the business to forecast churn probability based on historical data and initiate timely outreach programs.

Option B is correct because customer churn prediction aligns with UC ' s need to reduce cancellations through proactive measures.

Option A (product recommendation prediction) is unrelated to contract cancellations.

Option C (contract renewal date prediction) addresses timing but does not focus on predicting potential cancellations.

References :

Salesforce Model Builder Use Case Overview: https://help.salesforce.com/s/articleView?id=sf.model_builder_use_cases.htm

Bring Your Own Large Language Model (BYO-LLM) functionality in Einstein Studio allows organizations to integrate and use external large language models (LLMs) within the Salesforce ecosystem. Universal Containers can leverage this feature to connect and ground prompts with external LLMs, allowing for custom AI model use cases and seamless integration with Salesforce data.

Option B is the correct choice as Einstein Studio provides a built-in feature to work with external models.

Option A suggests using Apex, but BYO-LLM functionality offers a more streamlined solution.

Option C focuses on Flow and External Services , which is more about data integration and isn ' t ideal for working with LLMs.

References :

Salesforce Einstein Studio BYO-LLM Documentation: https://help.salesforce.com/s/articleView?id=sf.einstein_studio_llm.htm

The key reason for implementing Einstein Copilot is its ability to streamline workflows and automate repetitive tasks . By leveraging AI, Einstein Copilot can assist users in handling mundane, repetitive processes, such as automatically generating insights, completing actions, and guiding users through complex processes, all of which significantly improve operational efficiency.

Option A (Improving data entry and cleansing) is not the primary purpose of Einstein Copilot, as its focus is on guiding and assisting users through workflows.

Option B (Allowing AI to perform tasks without user interaction) does not accurately describe the role of Einstein Copilot, which operates interactively to assist users in real time.

Salesforce AI Specialist References: More details can be found in the Salesforce documentation: https://help.salesforce.com/s/articleView?id=sf.einstein_copilot_overview.htm

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

When creating a custom action for Einstein Bots in Salesforce (including Agentforce),  Action Instructions  are critical for defining how the bot processes and executes the action. These instructions guide the bot on the logic to follow, such as API calls, data transformations, or conditional steps. Testing and iterating on the instructions ensures the bot understands how to handle dynamic inputs, external integrations, and decision-making.

Salesforce documentation emphasizes that  Action Instructions  directly impact the bot’s ability to execute workflows accurately. For example, poorly defined instructions may lead to incorrect API payloads or failure to parse responses. The  Einstein Bot Developer Guide  highlights that refining instructions is essential for aligning the bot’s behavior with business requirements.

In contrast:

Action Name  (A) is a static identifier and does not affect functionality.

Action Input  (B) defines parameters passed to the action but does not dictate execution logic.

Thus, iterating on  Action Instructions  (C) ensures the action performs as expected.

Einstein Copilot is designed to enhance user interaction within Salesforce by leveraging Large Language Models (LLMs) to process and respond to user inquiries. When a user submits a request, Einstein Copilot analyzes the input using natural language processing techniques. It then utilizes LLM technology to generate an appropriate and contextually relevant response, which is displayed directly to the user within the Salesforce interface.

Option C accurately describes this process. Einstein Copilot does not necessarily trigger a flow (Option A) or perform an HTTP callout to an LLM provider (Option B) for each user request. Instead, it integrates LLM capabilities to provide immediate and intelligent responses, facilitating a broad range of user requests.

References:

Salesforce AI Specialist Documentation - Einstein Copilot Overview: Details how Einstein Copilot employs LLMs to interpret user inputs and generate responses within the Salesforce ecosystem.

Salesforce Help - How Einstein Copilot Works: Explains the underlying mechanisms of how Einstein Copilot processes user requests using AI technologies.

To understand multiple real-world user utterances and ensure the correct action is selected before activating a custom copilot action , the recommended tool is Copilot Builder . This tool allows AI Specialists to design and test conversational actions in response to user inputs, helping ensure the copilot can accurately handle different user queries and phrases. Copilot Builder provides the ability to test, refine, and improve actions based on real-world utterances.

Option C is correct as Copilot Builder is designed for configuring and testing conversational actions.

Option A (Model Playground) is used for testing models, not user utterances.

Option B (Einstein Copilot) refers to the conversational interface but isn ' t the right tool for designing and testing actions.

References :

Salesforce Copilot Builder Overview: https://help.salesforce.com/s/articleView?id=sf.einstein_copilot_builder.htm

Dynamic grounding with secure data retrieval is a key feature in Salesforce ' s Einstein Trust Layer , which provides enhanced data protection and ensures that AI-generated outputs are both accurate and securely sourced. This feature allows relevant Salesforce data to be merged into the AI-generated responses, ensuring that the AI outputs are contextually aware and aligned with real-time CRM data.

Dynamic grounding means that AI models are dynamically retrieving relevant information from Salesforce records (such as customer records, case data, or custom object data) in a secure manner. This ensures that any sensitive data is protected during AI processing and that the AI model’s outputs are trustworthy and reliable for business use.

The other options are less aligned with the requirement:

Data masking refers to obscuring sensitive data for privacy purposes and is not related to merging Salesforce records into prompts.

Zero-data retention policy ensures that AI processes do not store any user data after processing, but this does not address the need to merge Salesforce record information into a prompt.

References :

Salesforce Developer Documentation on Einstein Trust Layer

Salesforce Security Documentation for AI and Data Privacy