Salesforce-AI-Specialist日本語試験問題集合格できるには更新された2025年03月テスト問題集 [Q22-Q36]

Customer churn predictionis the best use case forModel Builderin addressingUniversal Containers’ concerns about increasing customer contract cancellations. By implementing a model that predicts customer churn,UCcan 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 Bis correct becausecustomer churn predictionaligns withUC’sneed 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

The “Create Close Plan” feature is designed to help sales reps by providing AI-generated strategies and steps specifically focused on closing deals. This feature leverages AI to analyze the current state of opportunities and generate a plan that outlines the actions, timelines, and key steps required to move deals toward closure. It aligns directly with the sales team’s need to meet quotas by offering actionable insights and structured plans.
Find Similar Deals (Option A) helps sales reps discover opportunities similar to their current deals but doesn’t offer a plan for closing.
Create Account Plan (Option B) focuses on long-term strategies for managing accounts, which might include customer engagement and retention, but doesn’t focus on deal closure.
Salesforce AI Specialist Reference:
For more information on using AI for sales, visit: https://help.salesforce.com/s/articleView?id=sf.einstein_for_sales_overview.htm

For sales reps who need to draft personalized emails based on previous communications, the AI Specialist should recommend theEinstein 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 Opportunitiesis used for opportunity matching, not email drafting.
* Summarize Recordprovides a summary of customer data but does not directly help with drafting emails.
For more information, refer toSalesforce’s Einstein Copilot documentationon standard actions for sales teams.

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:https://help.salesforce.com/s/articleView?id=sf.
einstein_service_replies.htm

To generate an email about products that closely match a customer’s expressed interests, an AI Specialist should recommend using acustom sales email templatethat isgrounded with interest and product information. This ensures that the email content is personalized based on the customer’s preferences, increasing the relevance of the marketing message.
Using grounding ensures that the generative AI pulls the correct data related to customer interests and product matches, making the email more effective.
For more information, refer toSalesforce documentationon grounding AI-generated content and email personalization strategies.

Universal Containers needs to generate a sales proposal using data from multiple unrelated standard and custom objects within a prompt template. The most effective way to achieve this is by using a Flex template.
Flex templates in Salesforce allow AI specialists to create prompt templates that can accept inputs from multiple sources, including various standard and custom objects. This flexibility enables the direct use of data from unrelated objects without the need to create intermediary custom objects or complex flows.
Reference:
Salesforce AI Specialist Documentation – Flex Templates: Explains how Flex templates can be utilized to incorporate data from multiple sources, providing a flexible solution for complex data requirements in prompt templates.

To addresssecurity complianceconcerns and provide visibility into theprompt text sent to the LLM, how it ismasked, and themasked response, the AI Specialist should recommend enabling theaudit trail in the Einstein Trust Layer. This feature captures and logs the prompts sent to the large language model (LLM) along with the masking of sensitive information and the AI’s response. This audit trail ensures full transparency and compliance with security requirements.
* Option A (Einstein Shield Event logs)is focused on system events rather than specific AI prompt data.
* Option B (debug logs)would not provide the necessary insight into AI prompt masking or responses.
For further details, refer toSalesforce’s Einstein Trust Layer documentationabout auditing and security measures.

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 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.
Reference:
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.

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:https://help.salesforce.com/s/articleView?
id=einstein_copilot_overview.htm

When previewing aprompt templatein Salesforce, theResolutiontext provides theresponse from the LLM (Large Language Model) based on the data from a sample record. This output shows what the AI model generated in response to the prompt, giving the AI Specialist a chance to review and adjust the response before finalizing the template.
* Option Bis correct becauseResolutiondisplays the actual response generated by the LLM.
* Option Arefers to sending the text to theTrust Layer, but that’s not whatResolutionrepresents.
* Option Crelates to data masking, which is shown elsewhere, not underResolution.
References:
* Salesforce Prompt Builder Overview:https://help.salesforce.com/s/articleView?id=sf.
prompt_builder_overview.htm

Universal Containers aims to reduce overall agent handling time by minimizing the time agents spend typing routine answers for common questions during chats and by reducing post-chat analysis through suggesting values for case fields.
To achieve these objectives, the combination ofEinstein Reply RecommendationsandCase Classificationis the most appropriate solution.
1. Einstein Reply Recommendations:
* Purpose:Helps agents respond faster during live chats by suggesting the best responses based on historical chat data and common customer inquiries.
* Functionality:
* Real-Time Suggestions:Provides agents with a list of recommended replies during a chat session, allowing them to quickly select the most appropriate response without typing it out manually.
* Customization:Administrators can configure and train the model to ensure the recommendations are relevant and accurate.
* Benefit:Significantly reduces the time agents spend typing routine answers, thus improving efficiency and reducing handling time.
2. Case Classification:
* Purpose:Automatically suggests or populates values for case fields based on historical data and patterns identified by AI.
* Functionality:
* Field Predictions:Predicts values for picklist fields, checkbox fields, and more when a new case is created.
* Automation:Can be set to auto-populate fields or provide suggestions for agents to approve.
* Benefit:Reduces the time agents spend on post-chat analysis and data entry by automating the classification and field population process.
Why Options A and B are Less Suitable:
* Option A (Einstein Service Replies and Work Summaries):
* Einstein Service Replies:Similar to Reply Recommendations but typically used for email and not live chat.
* Work Summaries:Provides summaries of customer interactions but does not assist in field value suggestions.
* Option B (Einstein Reply Recommendations and Case Summaries):
* Case Summaries:Generates a summary of the case details but does not help in suggesting field values.
References:
* Salesforce AI Specialist Documentation -Einstein Reply Recommendations:
* Details how Reply Recommendations assist agents in providing quick responses during live chats.
* Salesforce AI Specialist Documentation -Einstein Case Classification:
* Explains how Case Classification predicts and suggests field values to streamline case management.
* Salesforce Trailhead -Optimize Service with AI:
* Provides an overview of AI features that enhance service efficiency.

TheEinstein Trust Layeris 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: Theaudit trailcaptures 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. TheData Cloudprovides the infrastructure for managing and accessing this audit data.
* Why not B?UsingPrompt Builderin 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 theSalesforce AI Trust Layerdocumentation, which outlines how organizations can manage and track generative AI interactions securely.

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.

In theEinstein Trust Layer, thetoxicity scoringsystem is used to evaluate the safety level of content generated by AI, particularly to ensure that it is non-toxic, inclusive, and appropriate for business contexts. A toxicity score of 1indicates that the content is deemedsafe.
The scoring system ranges from 0 (unsafe) to 1 (safe), with intermediate values indicating varying degrees of safety. In this case, a score of 1 means that the generated content is fully safe and meets the trust and compliance guidelines set by theEinstein Trust Layer.
For further reference, check Salesforce’s officialEinstein Trust Layer documentationregardingtoxicity scoringfor AI-generated content.