Salesforce Salesforce-AI-Specialist Salesforce Certified AI Specialist Exam Exam Practice Test

Universal Containers is enhancing its customer service operations with Custom Copilot Actions. The development team needs to understand thecore componentsof a Custom Copilot Action to ensure proper configuration and functionality. One of these core components is theOutput Types.

Core Components of a Custom Copilot Action:

Instructions:

Defines what the action should accomplish.

Provides guidance to the AI assistant on how to execute the action.

Input Parameters:

The data inputs required for the action to perform its task.

Specifies the parameters that users or systems need to provide.

Output Types:

Definition:Specifies the type of data the action will output after execution.

Importance:Ensures that the Copilot and other components understand the format and structure of the action's results.

Examples:Text, JSON, records, or other data structures.

Action Reference:

Points to the underlying implementation, such as an Apex class or Flow.

Action Triggers:

Conditions or events that initiate the action.

Focus on Output Types:

Relevance in Configuration:

The development team must define the Output Types correctly to ensure that the action's results are properly processed and displayed by Copilot.

Incorrect or undefined Output Types can lead to misinterpretation of data and failures in functionality.

Why Output Types are a Core Component:

Integration with Copilot:

Copilot relies on the Output Types to understand how to handle the data returned by the action.

Data Consistency:

Defines the structure and format of the output, ensuring consistent communication between the action and Copilot.

User Experience:

Proper Output Types ensure that users receive the expected results in an understandable format.

Why Other Options are Less Suitable:

Option A (Instructions):

While Instructions are a core component, the question asks for what should be reviewed in the configuration to identifyone of the core components.

In this context, reviewingOutput Typesis more critical to ensuring proper configuration and functionality.

Option C (Action Triggers):

Action Triggers are important but are not always considered a core component within the configuration of a Custom Copilot Action.

Triggers often relate to when an action is initiated rather than the configuration of the action itself.

References:

Salesforce AI Specialist Documentation -Custom Copilot Actions:

Details the components and configuration of Custom Copilot Actions.

Salesforce Help -Defining Output Types in Custom Actions:

Explains the importance of Output Types and how to configure them.

Salesforce Trailhead -Building Custom Copilot Actions:

Provides a hands-on approach to creating and configuring Custom Copilot Actions, highlighting key components.

The key reason for implementingEinstein Copilotis its ability tostreamline workflowsandautomate 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:

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

Option Ais correct asEinstein Copilothelps generate real-time, personalized content based on comprehensive data about the customer.

Option Brefers more to Einstein Analytics or Marketing Cloud Intelligence, andOption Cdeals with automation, which isn't the primary focus ofEinstein Copilot.

References:

Salesforce Einstein Copilot Overview:

When usingEinstein Generative AIto create personalized emails, if placeholders appear in the draft email where data from a recipient'sContactrecord should be, the most likely reason is that theuser 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 Bis 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:

Universal Containers can achieve the request to explore similar opportunities by using thestandard Copilot action.Einstein Copilothas built-in actions to handle natural language queries, such as “Show me other opportunities like this one.” The standard action will process the query and return results based on predefined matching criteria like opportunity details and past Closed Won deals.

This approach avoids the need to create custom flows or Apex classes, leveraging out-of-the-box functionality.

For further details, refer toEinstein Copilot for Sales documentationregarding standard actions and natural language processing.

WhenUniversal Containerscreates 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 shouldmanually add the necessary hyperparametersto the new template.

Hyperparameters likeTemperature,Frequency Penalty, andPresence Penaltydirectly 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 toPrompt Builder documentationon configuring hyperparameters in custom templates.

After modifying masked fields inEinstein's Trust Layer, the next important step is totest and confirmthat the responses generated by prompts utilizing the newly masked data still meet quality standards. This ensures that masking sensitive information does not negatively impact the usefulness or accuracy of the AI-generated content. Thorough testing helps identify any issues in prompt performance that could arise due to masking, and adjustments can be made if needed.

Option Bis correct because testing the effects of masking on AI responses is a critical step in ensuring AI continues to function as expected.

Option A(turning off and on the Einstein Trust Layer) is unnecessary after changing the masked fields.

Option C(turning on Einstein Feedback) allows for user feedback but is not a direct step following field masking modifications.

References:

Salesforce Einstein Trust Layer Overview:

In Einstein Copilot, the role of the Large Language Model (LLM) is to analyze user inputs and identify the best matching actions that need to be executed. It uses natural language understanding to break down the user’s request and determine the correct sequence of actions that should be performed.

By doing so, the LLM ensures that the tasks and actions executed are contextually relevant and are performed in the proper order. This process provides a seamless, AI-enhanced experience for users by matching their requests to predefined Salesforce actions or flows.

The other options are incorrect because:

A mentions finding similar requests, which is not the primary role of the LLM in this context.

C focuses on access and sorting by priority, which is handled more by security models and governance than by the LLM.

References:

Salesforce Einstein Documentation on Einstein Copilot Actions

Salesforce AI Documentation on Large Language Models

Universal Containers is considering the use of the Einstein Trust Layer along with Einstein Generative AI Audit Data. The Einstein Trust Layer provides a secure and compliant way to use AI by offering features like data masking and toxicity assessment.

The audit data available through the Einstein Trust Layer includes information aboutmasked data—which ensures sensitive information is not exposed—and thetoxicity score, which evaluates the generated content for inappropriate or harmful language.

References:

Salesforce AI Specialist Documentation - Einstein Trust Layer:Details the auditing capabilities, including logging of masked data and evaluation of generated responses for toxicity to maintain compliance and trust.

Prompt Defenseis a feature in theEinstein Trust Layerthat helps minimize the risks ofjailbreakingandprompt injection attacks. These attacks occur when malicious users try to manipulate the AI model by providing unintended inputs.Prompt Defenseensures that the prompts are processed securely, protecting the system from such vulnerabilities.

Option A(Secure Data Retrieval and Grounding) relates to ensuring that data used by AI is securely retrieved but does not address prompt security.

Option B(Data Masking) focuses on protecting sensitive information but does not prevent injection attacks.

For more information, refer toSalesforce's Einstein Trust Layer documentationonPrompt Defenseand security features.

To provide the sales team with insights into product and competitor names mentioned during calls, Universal Containers should:

Enable Einstein Conversation Insights:Activates the feature that analyzes call recordings for valuable insights.

Enable Sales Recording:Allows calls to be recorded within Salesforce without needing an external recording provider.

Assign Permission Sets:Grants the necessary permissions to sales team members to access and utilize conversation insights.

Customize Insights:Configure the system to track mentions of up to50 productsand50 competitors, providing tailored insights relevant to the organization's needs.

OptionCaccurately reflects these steps. OptionAmentions defining recording managers but omits enabling sales recording within Salesforce. OptionBsuggests connecting a recording provider and limits customization to 25 products, which does not fully meet UC's requirements.

References:

Salesforce AI Specialist Documentation - Setting Up Einstein Conversation Insights:Provides instructions on enabling conversation insights and sales recording.

Salesforce Help - Customizing Conversation Insights:Details how to customize insights with up to 50 products and competitors.

Salesforce AI Specialist Exam Guide:Outlines best practices for implementing AI features like Einstein Conversation Insights in a sales context.

=========================

In order to access and create custom prompt templates inPrompt Builder, the AI Specialist must have thePrompt Template Managerpermission set assigned. Without this permission, they will not be able to accessPrompt Builderin the Setup menu, even thoughEinstein Generative AIis enabled.

Option Bis correct because thePrompt Template Managerpermission set is required to usePrompt Builder.

Option A(Prompt Template User permission set) is incorrect because this permission allows users to use prompts, but not create or manage them.

Option C(LLM configuration in Data Cloud) is unrelated to the ability to accessPrompt Builder.

References:

Salesforce Prompt Builder Permissions:

ForUniversal Containers (UC)to offer personalized service experiences and reduce agent handling time using AI-generated responses grounded in theKnowledge base, the best solution isEinstein Service Replies for Email. This capability leverages AI to automatically generate responses to service-related emails based on historical data and theKnowledge base, ensuring accuracy and relevance while saving time for service agents.

Einstein Email Replies(option A) is more suited for sales use cases.

Einstein Generative Service Replies for Email(option C) could be a future offering, but as of now,Einstein Service Replies for Emailis the correct choice for grounded, knowledge-based responses.

References:

Einstein Service Replies Overview:

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 withtriple quotes ("""). This formatting ensures that the LLM adheres to the specific instructions while generating the email content.

The use oftriple quotesallows 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 toSalesforce Prompt Builder documentationfor detailed instructions on how to structure prompts for generative AI.

To improve the productivity of the service center, the AI Specialist should recommend theService RepliesandCase Summariesfeatures.

Service Replieshelps agents by automatically generating suggested responses to customer inquiries, reducing response time and improving efficiency.

Case Summariesprovide a quick overview of case details, allowing agents to get up to speed faster on customer issues.

Work Summariesare not as relevant for direct customer service operations, andSales Summariesare focused on sales processes, not service center productivity.

For more information, seeSalesforce's Einstein Service Cloud documentationon the use of generative AI to assist customer service teams.

To customize thecase summary responsefromEinstein Copilot, the AI Specialist should create acustom Record Summary prompt templatefor theCase 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 toSalesforce Prompt Builder documentationfor guidance on creating custom templates for record summaries.

To meetUniversal Containers'goal of improving efficiency and reducing agent handling time with AI-generated responses, the best approach is to enableService Replies,Service AI Grounding, andGrounding with Knowledge.

Service Repliesgenerates responses automatically.

Service AI Groundingensures that the AI is using relevant case data.

Grounding with Knowledgeensures that responses are backed by Salesforce Knowledge articles, allowing agents to identify whether a response is coming from theLLMorSalesforce Knowledge.

Option Cdoes not includeService Replies, which is necessary for generating AI responses.

Option Alacks theGrounding with Knowledge, which is essential for identifying response sources.

For more details, refer toSalesforce Service AI documentationon grounding and service replies.

When an active standard email prompt template doesn’t meet the business requirements, the best approach is toclone the existing templateand 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 versionis typically used for versioning changes in the same template, whileSave as New Templatecreates a brand-new template without linking to the existing one.Cloningprovides a balance, allowing modifications while retaining the original structure for future reference.

For more details, refer toSalesforce Prompt Builder documentationfor guidance on cloning and modifying templates.

To accessexternally-hosted models, such as a large language model (LLM) hosted on AWS, theModel Builderin Salesforce is the appropriate tool.Model Builderallows teams to integrate and deploy external AI models into the Salesforce platform, making it possible to leverage models hosted outside of Salesforce infrastructure while still benefiting from the platform's native AI capabilities.

Option B, App Builder, is primarily used to build and configure applications in Salesforce, not to integrate AI models.

Option C, Copilot Builder, focuses on building assistant-like tools rather than integrating external AI models.

Model Builder enables seamless integration with external systems and models, allowing Salesforce users to use external LLMs for generating AI-driven insights and automation.

Salesforce AI Specialist References:For more details, check the Model Builder guide here:

In this scenario,Universal Containerswants to bring data fromunified Data Cloud objectsinto prompt templates, and the best way to do that is through aData Cloud-triggered flow. This type of flow is specifically designed to trigger actions based on data changes within Salesforce Data Cloud objects.

Data Cloud-triggered flows can listen for changes in the unified data model and automatically bring relevant data into the system, making it available for prompt templates. This ensures that the data is both real-time and up-to-date when used in generative AI contexts.

For more detailed guidance, refer to Salesforce documentation onData Cloud-triggered flowsandData Cloud integrationswith generative AI solutions.

Prompt Builderis designed to help organizations create and configure reusable prompts for large language models (LLMs). By integratinggenerative AIresponses into workflows,Prompt Builderenables customization of AI prompts that interact with Salesforce data and automate complex processes. This tool is especially useful for creating tailored and consistent AI-generated content in various business contexts, including customer service and sales.

It is not a tool forApex programming(as in option A).

It is also not limited to real-time suggestions as mentioned in option C. Instead, it provides a flexible way for companies to manage and customize how AI-driven responses are generated and used in their workflows.

References:

Salesforce Prompt Builder Overview:

Salesforce Einstein Copilotis designed to provide a conversational AI interface that can be utilized by different types of Salesforce users, such as developers, sales agents, and retailers. It acts as anAI-powered assistantthat facilitates natural interactions with the system, enabling users to perform tasks and access data easily. This includes tasks like pulling reports, updating records, and generating personalized responses in real time.

Option Ais correct becauseEinstein Copilotbrings a conversational interface that caters to a wide range of users.

Option BandOption Care more focused on developing and training AI models, which are not the primary functions ofEinstein Copilot.

References:

Salesforce Einstein Copilot Overview:

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.

OptionCaccurately 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 ground a sales email onOpportunity Products, Events near the customer, and Tone and voice examples, the AI Specialist should use aprompt-initiated flow. This flow can dynamically fetch the necessary data from related records in Salesforce and ground the generative AI output with contextually accurate information.

Option B (flex template)does not provide the ability to fetch dynamic data from Salesforce records automatically.

Option C (manual insertion)would not allow for the dynamic and automated grounding of data required for custom prompts.

Refer toSalesforce documentation on flowsand grounding for more details on integrating data into custom prompt templates.

WhenUniversal Containers' AI data masking rulesdo not meet organizational privacy and security standards, the AI Specialist should configure thedata maskingrules within theEinstein Trust Layer. TheEinstein Trust Layerprovides a secure and compliant environment where sensitive data can be masked or anonymized to adhere to privacy policies and regulations.

Option A, enabling data masking for sandbox refreshes, is related to sandbox environments, which are separate from how AI interacts with production data.

Option C, adding masking rules in the LLM setup, is not appropriate because data masking is managed through theEinstein Trust Layer, not the LLM configuration.

The Einstein Trust Layer allows for more granular control over what data is exposed to the AI model and ensures compliance with privacy regulations.

Salesforce AI Specialist References:For more information, refer to:

An AI Specialist wants to include data from the response of an external service invocation (REST API callout) into a prompt template. The goal is to incorporate dynamic data retrieved from an external API into the AI-generated content.

Solution:

Use External Service Record Merge Fields

External Service Integration:

Definition:External Services in Salesforce allow the integration of external REST APIs into Salesforce without custom code.

Registration:The external service must be registered in Salesforce, defining the API's schema and methods.

External Service Record Merge Fields:

Purpose:Enables the inclusion of data from external service responses directly into prompt templates using merge fields.

Functionality:

Dynamic Data Inclusion:Allows prompt templates to access and use data returned from REST API callouts.

Merge Fields Syntax:Use merge fields in the prompt template to reference specific data points from the API response.

Implementation Steps:

Register the External Service:

UseExternal Servicesto register the REST API in Salesforce.

Define the API's schema, including methods and data structures.

Create a Named Credential:

Configure authentication and endpoint details for the external API.

Use External Service in Flow:

Build aFlowthat invokes the external service and captures the response.

Ensure the flow outputs the necessary data for use in the prompt template.

Configure the Prompt Template:

UseExternal Service Record merge fieldsin the prompt template to reference data from the flow's output.

Syntax Example: {{flowOutputVariable.fieldName}}

Why Other Options are Less Suitable:

Option A (Convert the JSON to an XML merge field):

Irrelevance:Converting JSON to XML merge fields is unnecessary and complicates the process.

Unsupported Method:Salesforce prompt templates do not support direct inclusion of XML merge fields from JSON conversion.

Option C (Use “Add Prompt Instructions” flow element):

Purpose of Add Prompt Instructions:

Allows adding instructions to the prompt within a flow but does not facilitate including external data.

Limitation:Does not directly help in incorporating external service responses into the prompt template.

References:

Salesforce AI Specialist Documentation -Integrating External Services with Prompt Templates:

Explains how to use External Services and merge fields in prompt templates.

Salesforce Help -Using Merge Fields with External Data:

Provides guidance on referencing external data in templates using merge fields.

Salesforce Trailhead -External Services and Flow:

Offers a practical understanding of integrating external APIs using External Services and Flow.

Conclusion:

By using External Service Record merge fields, the AI Specialist can effectively include data from external REST API responses into prompt templates, ensuring that the AI-generated content is enriched with up-to-date and relevant external data.

When usingPrompt Builderin a Salesforce org, the correct process involves several important steps:

Select the appropriate prompt template typebased on the use case.

Develop the promptwithin theprompt workspace, where the template is created and customized.

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

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

Test and validatethe generated responses to ensure accuracy and effectiveness.

Option Bis correct as it follows the proper steps for usingPrompt Builder.

Option AandOption Cdo not capture the full process correctly.

References:

Salesforce Prompt Builder Documentation: