Salesforce-AI-Specialist Salesforce Certified AI Specialist Exam Questions and Answers

Event Logs  in Salesforce capture detailed interaction data, including agent errors, triggered actions, and incomplete plans. These logs provide visibility into user-Agent interactions for troubleshooting performance issues. The  Einstein Bot Analytics  documentation highlights Event Logs as the primary source for auditing bot behavior and diagnosing issues like misconfigured actions or plan execution failures.

Plan Canvas  (B) is for designing workflows, not auditing.

Agent Settings  (C) control configuration but do not store interaction history.

When an active standard email prompt template doesn’t meet the business requirements, the best approach is to clone the existing template and modify it as needed. Cloning allows the AI Specialist to preserve the original template while making adjustments to fit specific business needs. This ensures that any customizations are applied without altering the original standard template.

Saving as a new version is typically used for versioning changes in the same template, while Save as New Template creates a brand-new template without linking to the existing one. Cloning provides a balance, allowing modifications while retaining the original structure for future reference.

For more details, refer to Salesforce Prompt Builder documentation for guidance on cloning and modifying templates.

To customize the case summary response from Einstein Copilot , the AI Specialist should create a custom Record Summary prompt template for the Case object . This allows Universal Containers to tailor the way case data is summarized, ensuring the output aligns with specific business requirements or user preferences.

Option A (customizing the standard Record Summary template) does not provide the flexibility required for deep customization.

Option B (standard Copilot action) won’t allow customization; it will only use default settings.

Refer to Salesforce Prompt Builder documentation for guidance on creating custom templates for record summaries.

Secure Data Retrieval  enforces Salesforce’s security model by dynamically grounding data access in the  permissions of the user executing the prompt . This ensures compliance with CRUD (Create, Read, Update, Delete) and FLS (Field-Level Security) settings, preventing unauthorized access to sensitive data. For example, if a user lacks access to a specific object or field, the AI model cannot retrieve it for dynamic grounding.

" Run As " user permissions  (A) would bypass user-specific security, posing a compliance risk.

Prompt template permissions  (C) are not a Salesforce security mechanism; access is always tied to the user’s profile and sharing settings.

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.

The Einstein Trust Layer is designed to ensure transparency, compliance, and security for organizations leveraging Salesforce’s AI and generative AI capabilities. Specifically, for auditing, tracking, and viewing masked data, organizations can utilize:

Audit Trail in Data Cloud : The audit trail captures and stores all prompts submitted to large language models (LLMs), ensuring that sensitive or masked data interactions are logged. This allows organizations to monitor and audit all AI-generated outputs, ensuring that data handling complies with internal and regulatory guidelines. The Data Cloud provides the infrastructure for managing and accessing this audit data.

Why not B? Using Prompt Builder in Setup to send prompts to the LLM is for creating and managing prompts, not for auditing or tracking data. It does not interact directly with the audit trail functionality.

Why not C? Although the audit trail can be accessed in Setup, the user-generated prompts are primarily tracked in the Data Cloud for broader control, auditing, and analysis. Setup is not the primary tool for exporting or managing these audit logs.

More information on auditing AI interactions can be found in the Salesforce AI Trust Layer documentation, which outlines how organizations can manage and track generative AI interactions securely.

For Einstein Sales Emails to generate personalized follow-up emails, it is crucial to ground the email content with the most up-to-date and accurate information. Grounding refers to connecting the AI model with real-time data. The most appropriate technique in this case is Ground with Record Merge Fields . This method ensures that the content in the emails pulls dynamic and accurate data directly from Salesforce records, such as lead or contact information, ensuring the follow-up is relevant and customized based on the specific record.

Record Merge Fields ensure the generated emails are highly personalized using data like lead name, company, or other Salesforce fields directly from the records.

Apex Merge Fields are typically more suited for advanced, custom logic-driven scenarios but are not the most straightforward for this use case.

Automatic grounding using Draft with Einstein is a different feature where Einstein automatically drafts the email, but it does not specifically ground the content with record-specific data like Record Merge Fields .

References :

Salesforce Einstein Sales Emails Documentation: https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein_sales_emails.htm

Agentforce Sales Agent  is designed to let sales teams perform tasks via  natural language commands , leveraging Salesforce data while adhering to policies. For example, agents can ask the AI to " update the opportunity stage to Closed Won " or " generate a quote, " with the system enforcing validations and data security. This use case aligns with Salesforce’s vision of conversational AI streamlining workflows without compromising compliance.

Step-by-step guides  (B) are typically handled by tools like Dynamic Forms or Guided Selling, not Agentforce.

Logging messages/emails  (C) is managed by Email-to-Case or Service Cloud, not a sales-specific AI agent.

Service Replies : This generative AI feature automates and assists in generating accurate, contextual, and efficient replies for customer service agents. It uses past interactions, case data, and the context of the conversation to provide draft responses, thereby enhancing productivity and reducing response times.

Case Summaries : Summarizes case information but does not assist directly in replying to customer chats.

Case Escalation : Refers to moving cases to higher-level support teams but does not address the need to improve chat response productivity.

Thus, Service Replies is the best feature for this requirement as it directly aligns with improving agent efficiency in replying to chats.

Before creating a Field Generation prompt template , the AI Specialist must ensure that the Salesforce org is set to API version 59 or higher . This version of the API introduces support for advanced generative AI features, such as enabling fields for generative AI outputs. This is a critical technical requirement for the Field Generation prompt template to function correctly.

Option A (rich text field requirement) is not necessary for generative AI functionality.

Option C (Dynamic Forms) does not impact the ability of a field to be generative AI-enabled, although it might enhance the user interface.

For more information, refer to Salesforce documentation on API versioning and Field Generation templates .

Context of the Question

When an Agent (e.g., Agentforce or a similar generative AI assistant in Salesforce) cannot understand a user’s request or fails to locate the requested information, it should provide a coherent fallback.

Fallback / Error Handling in Agentforce

Preconfigured or “Fallback” Message : Typically, within the setup of any AI assistant, admins define a fallback or “failure” response. This message can be tailored to each action type or scenario (e.g., “No data found,” “Sorry, I didn’t get that—please try again,” etc.).

Why Not an Automatically Generated Error Message? (Option A) AI assistants rarely show raw system error messages; they generally display friendly, standardized messages.

Why Not a Purely Generic “Rephrase” Message? (Option B) Although an agent might prompt the user to rephrase, Salesforce best practices are to configure a fallback response or fallback action that aligns with the brand and the context. This is typically a “preconfigured message based on the action type.”

Conclusion Because the assistant uses a preconfigured fallback that is set up in the environment (for example, in the agent’s or domain’s settings), the correct choice is Option C .

Salesforce AI Specialist References & Documents

Salesforce Pilot / Agentforce Setup Documentation Explains how to configure a fallback or default message when the AI cannot fulfill a user’s request.

Salesforce AI Specialist Study Guide Details best practices for AI-driven assistants and how fallback scenarios are handled with preconfigured messages.

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.

References:

Salesforce Help:  Sales Email Prompt Templates

Describes using Sales Email prompt templates to " generate targeted emails using dynamic data and LLMs. "

Einstein Copilot is designed to assist in generating personalized, AI-driven content based on customer data such as behavior, preferences, and purchase history. For the marketing team at Universal Containers , this is the perfect solution to create dynamic and relevant email content. By leveraging Einstein Copilot , they can ensure that each customer receives tailored communications, improving engagement and conversion rates.

Option A is correct as Einstein Copilot helps generate real-time, personalized content based on comprehensive data about the customer.

Option B refers more to Einstein Analytics or Marketing Cloud Intelligence, and Option C deals with automation, which isn ' t the primary focus of Einstein Copilot .

References :

Salesforce Einstein Copilot Overview: https://help.salesforce.com/s/articleView?id=einstein_copilot_overview.htm

When Universal Containers creates a new Sales Email prompt template using the " Save As " function, missing hyperparameters can result in different outputs. To ensure the new prompt produces comparable results to the standard Sales Email prompt, the AI Specialist should manually add the necessary hyperparameters to the new template.

Hyperparameters like Temperature , Frequency Penalty , and Presence Penalty directly affect how the AI generates responses. Ensuring that these are consistent with the standard template will result in similar outputs.

Option A (Model Playground) is not necessary here, as it focuses on fine-tuning models, not adjusting templates directly.

Option C (Reverting to the standard template) does not solve the issue of customizing the prompt template.

For more information, refer to Prompt Builder documentation on configuring hyperparameters in custom templates.

In Model Playground , an AI specialist working with a Salesforce-enabled foundational model has control over specific hyperparameters that can directly affect the behavior of the generative model:

Temperature : Controls the randomness of predictions. A higher temperature leads to more diverse outputs, while a lower temperature makes the model ' s responses more focused and deterministic.

Frequency Penalty : Reduces the likelihood of the model repeating the same phrases or outputs frequently.

Presence Penalty : Encourages the model to introduce new topics in its responses, rather than sticking with familiar, previously mentioned content.

These hyperparameters are adjustable to fine-tune the model’s responses, ensuring that it meets the desired behavior and use case requirements. Salesforce documentation confirms that these three are the key tunable hyperparameters in the Model Playground.

For more details, refer to Salesforce AI Model Playground guidance from Salesforce’s official documentation on foundational model adjustments.

Before enabling  Call Explorer , the Salesforce AI Specialist must ensure that the  Einstein Conversation Insights permission set  is assigned to users (Option C). Call Explorer is a feature within Einstein Conversation Insights (ECI) that analyzes meeting recordings to surface trends, keywords, and actionable insights.

Key Considerations :

Permission Set Requirement :

Users (including admins) need the  Einstein Conversation Insights  permission set to access and use Call Explorer. Without this, the feature remains inaccessible.

The permission set grants access to ECI tools, including call transcription, analysis, and dashboard visibility.

Why Other Options Are Incorrect :

A. Independence from Salesforce Knowledge : While Call Explorer does not rely on Salesforce Knowledge, this is irrelevant to the setup prerequisite. The critical dependency is the permission set, not Knowledge configuration.

B. Custom Actions : Call Explorer does not require custom actions to be built before configuration. It is a pre-built analytics tool that works once permissions and data sources (e.g., call recordings) are configured.

References :

Salesforce Einstein Conversation Insights Guide : Explicitly states that the Einstein Conversation Insights permission set is required to access Call Explorer.

Trailhead Module : " Einstein Conversation Insights Basics " outlines permission prerequisites for enabling call analytics.

Salesforce Help Documentation : Confirms that Call Explorer functionality is governed by ECI permissions.

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.

The Einstein Trust Layer ensures that sensitive data is protected while generating useful and meaningful responses by masking sensitive data before it is sent to the Large Language Model (LLM) and then de-masking it during the response journey.

How It Works:

Data Masking in the Request Journey:

Sensitive Data Identification: Before sending the prompt to the LLM, the Einstein Trust Layer scans the input for sensitive data, such as personally identifiable information (PII), confidential business information, or any other data deemed sensitive.

Masking Sensitive Data: Identified sensitive data is replaced with placeholders or masks. This ensures that the LLM does not receive any raw sensitive information, thereby protecting it from potential exposure.

Processing by the LLM:

Masked Input: The LLM processes the masked prompt and generates a response based on the masked data.

No Exposure of Sensitive Data: Since the LLM never receives the actual sensitive data, there is no risk of it inadvertently including that data in its output.

De-masking in the Response Journey:

Re-insertion of Sensitive Data: After the LLM generates a response, the Einstein Trust Layer replaces the placeholders in the response with the original sensitive data.

Providing Meaningful Responses: This de-masking process ensures that the final response is both meaningful and complete, including the necessary sensitive information where appropriate.

Maintaining Data Security: At no point is the sensitive data exposed to the LLM or any unintended recipients, maintaining data security and compliance.

Why Option A is Correct:

De-masking During Response Journey: The de-masking process occurs after the LLM has generated its response, ensuring that sensitive data is only reintroduced into the output at the final stage, securely and appropriately.

Balancing Security and Utility: This approach allows the system to generate useful and meaningful responses that include necessary sensitive information without compromising data security.

Why Options B and C are Incorrect:

Option B (Masked data will be de-masked during request journey):

Incorrect Process: De-masking during the request journey would expose sensitive data before it reaches the LLM, defeating the purpose of masking and compromising data security.

Option C (Responses that do not meet the relevance threshold will be automatically rejected):

Irrelevant to Data Protection: While the Einstein Trust Layer does enforce relevance thresholds to filter out inappropriate or irrelevant responses, this mechanism does not directly relate to the protection of sensitive data. It addresses response quality rather than data security.

References:

Salesforce AI Specialist Documentation - Einstein Trust Layer Overview :

Explains how the Trust Layer masks sensitive data in prompts and re-inserts it after LLM processing to protect data privacy.

Salesforce Help - Data Masking and De-masking Process :

Details the masking of sensitive data before sending to the LLM and the de-masking process during the response journey.

Salesforce AI Specialist Exam Guide - Security and Compliance in AI :

Outlines the importance of data protection mechanisms like the Einstein Trust Layer in AI implementations.

Conclusion:

The Einstein Trust Layer ensures sensitive data is protected by masking it before sending any prompts to the LLM and then de-masking it during the response journey. This process allows Salesforce to generate useful and meaningful responses that include necessary sensitive information without exposing that data during the AI processing, thereby maintaining data security and compliance.

For sales reps who need to draft personalized emails based on previous communications, the AI Specialist should recommend the Einstein Copilot Action: Draft or Revise Sales Email . This action uses AI to generate or revise email content, leveraging past successful communications to create personalized and relevant outreach to prospects or clients.

Find Similar Opportunities is used for opportunity matching, not email drafting.

Summarize Record provides a summary of customer data but does not directly help with drafting emails.

For more information, refer to Salesforce ' s Einstein Copilot documentation on standard actions for sales teams.

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.

References :

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

To enable Sales Email prompt templates:

Permission Set : Assign the  Prompt Template User  permission set to the sales team to grant access to  use  pre-built templates.

Feature Activation : Enable  Sales Emails  in Salesforce Setup to activate the integration between prompt templates and email workflows.

Option B (Manager permission set) : Required for creating/modifying templates, not for usage.

Option C (Data Cloud Admin) : Unrelated to prompt template access.

References:

Salesforce Help:  Prompt Template Permissions

Specifies that " Prompt Template User " is required to leverage templates in workflows.

Sales Email Setup  outlines enabling the feature in Setup.

Universal Containers (UC) has concerns about data privacy when using Salesforce ' s generative AI features, particularly around preventing third-party LLMs from accessing or retaining their data. The Zero-Data Retention Policy in the Einstein Trust Layer is designed to address these concerns by ensuring that:

No data is used for training or product improvements by third-party LLMs.

No data is retained outside of the customer ' s Salesforce organization.

The LLM provider cannot access any customer data .

This policy aligns perfectly with UC’s requirements for keeping their data safe while leveraging generative AI capabilities.

Prompt Defense and Data Masking are also security features, but they do not directly address the concerns related to third-party data access and retention.

References :

Salesforce Einstein Trust Layer Documentation: https://help.salesforce.com/s/articleView?id=sf.einstein_trust_layer.htm

To gather the necessary data for populating the Latest Opportunities Summary custom field on the Account object with information from the three most recently opened opportunities, the AI Specialist should create a flow . A flow can be configured to query and retrieve the required opportunity records based on criteria such as their open date. Once the flow has gathered the necessary data, it can be used in a prompt template or other automation processes to populate the custom field on the Account record.

Option A is correct because creating a flow allows for dynamic data retrieval and control over the logic for selecting the most recent opportunities.

Option B and Option C do not provide sufficient control or data retrieval capabilities needed for this scenario.

References :

Salesforce Flow Documentation: https://help.salesforce.com/s/articleView?id=sf.flow.htm

When using Prompt Builder in a Salesforce org, the correct process involves several important steps:

Select the appropriate prompt template type based on the use case.

Develop the prompt within the prompt workspace , where the template is created and customized.

Select CRM-derived grounding data to be dynamically inserted into the prompt, ensuring that the AI-generated responses are based on accurate and relevant data.

Pick the model to use for generating responses, either using Salesforce ' s built-in models or custom ones.

Test and validate the generated responses to ensure accuracy and effectiveness.

Option B is correct as it follows the proper steps for using Prompt Builder .

Option A and Option C do not capture the full process correctly.

References :

Salesforce Prompt Builder Documentation: https://help.salesforce.com/s/articleView?id=sf.prompt_builder_overview.htm

Knowledge Replies  is the Einstein Generative AI capability that generates recommended responses for service agents by grounding responses in the organization’s  Knowledge articles . This reduces handling time by providing contextually accurate suggestions sourced directly from approved content. Salesforce documentation states that Knowledge Replies leverage natural language processing (NLP) to match customer inquiries with relevant articles and draft replies, ensuring consistency and compliance.

Case Replies  (A) focus on generating responses based on case data (e.g., case fields, history) but do not explicitly ground responses in Knowledge articles.

Service Replies  (C) is not a standard Einstein capability tied to Knowledge-driven responses.

When using Einstein Generative AI to create personalized emails, if placeholders appear in the draft email where data from a recipient ' s Contact record should be, the most likely reason is that the user lacks permission to access the necessary fields . Salesforce ' s field-level security may prevent users from viewing or utilizing certain data fields, resulting in placeholders being shown instead of the actual values.

Option B is correct because missing field permissions will cause placeholders in email drafts.

Option A (missing Einstein Sales Emails permission) is unlikely, as this would prevent email generation altogether, not just placeholders.

Option C (locale language issues) would more likely affect language-specific issues, not field placeholders.

References :

Salesforce Email Template and Permissions Documentation: https://help.salesforce.com/s/articleView?id=sf.email_templates_field_permissions.htm

Salesforce has restrictions on which objects and related lists can be used for grounding prompt templates. This is likely due to security and privacy concerns related to user data.

While it might seem intuitive to use the User related list to provide context to the LLM, Salesforce prevents this to ensure that sensitive user information is not inadvertently exposed or misused.

Therefore, the AI Specialist needs to explore alternative ways to incorporate the necessary user information into the prompt template, perhaps by using other related objects or fields that are supported.

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

Conclusion The 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 AI Specialist References & Documents

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

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

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

When a prompt template version is  immutable , it means that once the version is  activated , it cannot be edited or modified. This ensures consistency in production environments where changes could disrupt workflows.

Option A is incorrect : Any version (not just the latest) can be activated, depending on the use case.

Option D is incorrect : Modifications require manually creating a new version; automatic versioning is not enforced.

Option C is correct : Activation locks the version, enforcing immutability.

References:

Salesforce Help:  Prompt Template Versioning

States that " activated prompt template versions are immutable and cannot be edited. "

Since security and data privacy are critical, the best option for the AI Specialist is to integrate the fine-tuned LLM (Large Language Model) into Salesforce by adding it to Einstein Studio Model Builder . Einstein Studio allows organizations to bring their own AI models (BYOM), ensuring the model is securely managed within Salesforce’s environment, adhering to data privacy standards.

Option A (embedding via iFrame) is less secure and doesn’t integrate deeply with Salesforce ' s data and security models.

Option C (making callouts to OpenAI) raises concerns about data privacy, as sensitive Salesforce data would be sent to an external system.

Einstein Studio provides the most secure and seamless way to integrate custom AI models while maintaining control over data privacy and compliance. More details can be found in Salesforce ' s Einstein Studio documentation on integrating external models.

Context of the Question

Universal Containers (UC) wants to build a Flex prompt template that uses data returned by a Flow.

“Flex Prompt Templates” allow admins and AI Specialists to incorporate external or dynamic data into generative AI prompts.

Why “Add Flow Instructions” Is Needed

Passing Flow Data into Prompt Templates : When configuring the prompt, you must specify how data from the running Flow is passed into the Flex template. The designated element for that is typically “Flow Instructions,” which map the Flow outputs to the prompt.

Other Options :

Add Flex Instructions : Typically controls how the AI responds or structures the output, not how to bring Flow data into the template.

Add Prompt Instructions : Usually for static or manual instructions that shape the AI’s response, rather than referencing dynamic data from the Flow.

Outcome

“Add Flow Instructions” ensures the prompt can dynamically use the data that the Flow returns—making Option C correct.

Salesforce AI Specialist References & Documents

Salesforce Help & Training: Using Prompt Templates with Flow Explains how to pass Flow variables into a prompt template via a specialized step (e.g., “Flow Instructions”).

Salesforce AI Specialist Study Guide Outlines how to configure generative AI prompts that reference real-time Flow data.

When refining Einstein Copilot custom action instructions , it is considered best practice to provide examples of user messages that are expected to trigger the action. This helps ensure that the custom action understands a variety of user inputs and can effectively respond to the intent behind the messages.

Option B (consistent phrases) can improve clarity but does not directly refine the triggering logic.

Option C (specifying a persona) is not as crucial as giving examples that illustrate how users will interact with the custom action.

For more details, refer to Salesforce ' s Einstein Copilot documentation on building and refining custom actions.

Context of the Question Universal Containers (UC) wants to include details from a related list on the Account object in a prompt template. This is typically done via Prompt Builder in Salesforce’s generative AI setup.

Prompt Builder Behavior

Selecting a Related List : Within Prompt Builder, you can navigate to the object (Account) and choose which related list (e.g., Contacts, Opportunities) you want to reference.

Field Picker : Once a related list is chosen, Prompt Builder provides a field picker interface, allowing you to select specific fields from that related list. These fields then become available for merge fields or dynamic insertion within your prompt.

Why Option A is Correct

Direct Alignment with the Standard Process : The recommended approach in Salesforce’s documentation is to select a related list and then use the field picker to add the necessary fields into your AI prompt. This ensures the prompt has exactly the data you need from that related list.

Why Not Option B (JSON Formatting)

No Mandatory JSON Requirement : Although you can structure data as JSON if you desire advanced formatting, Prompt Builder does not require you to manually assign the fields from the related list in JSON. The platform automatically handles how the data is passed along in the background.

Why Not Option C (Default Page Layout)

Independent of Page Layout : Prompt Builder does not rely strictly on the default page layout for fields. You can configure the fields you want from the related list, independent of how the user’s page layout is set up in the UI.

Conclusion Since the official Salesforce approach involves selecting a related list and then using the field picker to insert merge fields, Option A is the correct and verified answer.

Salesforce AI Specialist References & Documents

Salesforce Official Documentation: Prompt Builder Basics Explains how to reference objects and related lists when building AI prompts.

Salesforce Trailhead: Get Started with Prompt Builder Provides hands-on exercises demonstrating how to pick fields from related objects or lists.

Salesforce AI Specialist Study Guide Outlines best practices for referencing related records and fields in generative AI prompts.

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

Context of the Question Universal Containers (UC) wants its support agents to use Agentforce to ask questions about product tutorials and product guides. Agentforce typically references knowledge sources to provide accurate and contextual responses.

Why Knowledge Articles?

Centralized Repository : Publishing product tutorials and guides as Knowledge articles in Salesforce ensures that the information is readily available and searchable by Agentforce.

AI Integration : Salesforce’s AI solutions, including Agentforce, can often be configured to pull content directly from Salesforce Knowledge articles, giving users on-demand answers without manual data duplication.

Maintenance & Updates : Storing content in Salesforce Knowledge simplifies content updates, versioning, and user permissions.

Why Not the Other Options?

Option A (Create a Prompt Template) : Creating a prompt template alone does not solve how the underlying content (tutorials, guides) is stored or accessed by Agentforce. Prompt templates shape the queries/responses but do not provide the knowledge base.

Option B (Add an Answer Questions Custom Field) : A single field on the product object is insufficient for the depth of information found in tutorials and guides. It also lacks the robust search and user-friendly interface that Knowledge articles provide.

Conclusion To ensure Agentforce can effectively retrieve and deliver accurate information about products, publishing product tutorials and guides as Knowledge articles is the recommended approach.

Salesforce AI Specialist References & Documents

Salesforce Documentation: Set Up Salesforce Knowledge Discusses how to publish articles for easy access by AI-driven assistants and support teams.

Salesforce AI Specialist Study Guide Explains best practices for feeding knowledge sources to generative AI and Agentforce.

Context of the Question

Universal Container (UC) has used prompt templates to update summary fields on record pages.

Now, the admin wants to incorporate similar generative AI functionality within a Flow for automation purposes.

How to Call a Prompt Template Within a Flow

Flow Action : Salesforce provides a standard way to invoke generative AI templates or prompts within a Flow step. From the Flow Builder, you can add an “Action” that references the prompt template you created in Prompt Builder.

Other Options :

Invocable Apex : Possible fallback if there’s no out-of-the-box Flow Action available. However, Salesforce is releasing native Flow integration for AI prompts, making custom Apex less necessary.

Einstein for Flow : A broad label for Salesforce’s generative AI features within Flow. Under the hood, you typically use a “Flow Action” that points to your prompt.

Conclusion

The easiest out-of-the-box solution is to use a Flow Action referencing the prompt template. Hence, Option B is correct.

Salesforce AI Specialist References & Documents

Salesforce Trailhead: Use Prompt Templates in Flow Demonstrates how to add an Action in Flow that calls a prompt template.

Salesforce Documentation: Einstein GPT for Flow Explains standard flow actions to invoke and handle generative AI responses.

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.

References:

Salesforce AI Specialist Documentation - Service AI Grounding Configuration : Details the objects supported for grounding AI responses in Service Cloud.

Salesforce Help - Implementing Service AI Grounding : Provides guidance on setting up grounding with Case and Knowledge objects.

Salesforce Trailhead - Enhance Service with AI Grounding : Offers an interactive learning path on using AI grounding in service scenarios.

To effectively manage and use prompt templates, two distinct permission sets are required:

Prompt Template Manager : This permission set allows users to create prompt templates. It provides the necessary access to define templates, which can be shared and utilized across the organization.

Prompt Template User : This permission set is designed for users who need to execute the templates. It provides the ability to interact with pre-designed prompts and generate outcomes based on these templates.

The Data Cloud Admin permission set is not directly relevant to creating or executing prompt templates but is more focused on managing the Data Cloud.

When using related list merge fields in a prompt template associated with the Account object in Prompt Builder , the Activities related list is not supported due to it being a polymorphic field . Polymorphic fields can reference multiple different types of objects, which makes them incompatible with some merge field operations in prompt generation.

Option B is incorrect because person accounts do not limit the availability of merge fields for the Account object.

Option C is irrelevant since even if no related lists are available at runtime, the prompt can still generate based on other available data fields.

For more information, refer to Salesforce documentation on supported fields and limitations in Prompt Builder .

To monitor Einstein Copilot ' s usability and the assignment of actions, the AI Specialist should run Einstein Copilot Analytics . This feature provides insights into how often Copilot is used, the types of actions it is handling, and overall user engagement with the system. It’s the most effective way to track Copilot ' s performance and usage patterns.

Platform Debug Logs are not relevant for tracking user behavior or the assignment of Copilot actions.

Querying the Copilot log data via the Metadata API would not provide the necessary insights in a structured manner.

For more details, refer to Salesforce ' s Copilot Analytics documentation for tracking AI-driven interactions.

Instructions: This is a core component of Custom Copilot Actions. Instructions tell the AI model what the action should do and how it should be executed. Clear and concise instructions are crucial for the action to function correctly and provide the expected outcome.

Let ' s look at why the other options are not the primary core component:

Output Types: While important for defining the kind of data the action produces, it ' s not the core defining element of the action itself.

Action Triggers: These determine when the action is initiated, but they don ' t define the core functionality of the action.

To enable personalized product recommendations using generative AI, the foundational step for Universal Containers (UC) is  collecting and analyzing browsing data  (Option C). Personalized recommendations depend on understanding user behavior, which requires structured data about their browsing history. Without this data, the AI model lacks the context needed to generate relevant suggestions.

Data Collection : UC must first aggregate browsing data (e.g., pages visited, products viewed, session duration) to build a dataset that reflects user preferences.

Data Analysis : Analyzing this data identifies patterns (e.g., frequently viewed categories) that inform how prompts should be structured to retrieve relevant recommendations.

Grounding in Data : Salesforce’s Prompt Templates rely on grounding data to generate accurate outputs. Without analyzing browsing data, the prompt template cannot reference meaningful insights for personalization.

Options A and D are incorrect because:

Universal recommendations (A)  ignore personalization, which is the core requirement.

Writing a response script (D)  addresses chatbot interaction design, not the accuracy of recommendations.

References :

Salesforce AI Specialist Certification Guide : Highlights the importance of grounding prompts in relevant data sources to ensure accuracy.

Trailhead Module : " Einstein for Developers " emphasizes data preparation as a prerequisite for effective AI-driven personalization.

Salesforce Help Documentation : Recommends analyzing user behavior data to tailor generative AI outputs in commerce use cases.

Universal Containers should use a Predictive model to decide which of the three emails to send based on the customer ' s lifetime value score and market segment . Predictive models analyze data to forecast outcomes, and in this case, it would predict the most appropriate email to send based on customer attributes. Additionally, predictive models can provide explainability to show why a certain email was chosen, which is crucial for UC’s requirement to explain the decision-making process.

Generative models are typically used for content creation, not decision-making, and thus wouldn ' t be suitable for this requirement.

Predictive models offer the ability to explain why a particular decision was made, which aligns with UC’s needs.

Refer to Salesforce’s Predictive AI model documentation for more insights on how predictive models are used for segmentation and decision making.