The standard Einstein Copilot action that would be used in response to the user utterance, "Show me all the customers in New York," is Query Records. This action is responsible for retrieving a set of records from Salesforce based on a specified condition - in this case, filtering customers by location (New York).
Query Records is the action that fetches relevant data based on the criteria provided in the user's input.
Select Records is more about picking specific records from an already presented list.
Fetch Records is not a standard term used in this context for the action.
Refer to Einstein Copilot documentation on how Copilot actions work with natural language queries and data retrieval.

In this scenario, theEinstein Copilotcapability that best helps the agent is its ability toexecute tasks based on available actionsandanswer questionsusing data from Knowledge articles. Einstein Copilot can assist the service agent by providing relevant Knowledge articles on canceling and rebooking flights, ensuring that the agent has access to the correct steps and procedures directly within the workflow.
This feature leverages the agent's existing context (the travel itinerary) and provides actionable insights or next steps from the relevant Knowledge articles to help the agent quickly resolve the customer's needs.
The other options are incorrect:
* Brefers to invoking a flow to create a Knowledge article, which is unrelated to the task of retrieving existing Knowledge articles.
* Cfocuses on generating Knowledge articles, which is not the immediate need for this situation where the agent requires guidance on existing procedures.
References:
* Salesforce Documentation onEinstein Copilot
* Trailhead Module onEinstein for Service

ForUniversal Containers (UC), to reduce the time and ensure prompt consistency when using public generative AI models, the recommended feature isEinstein Prompt Builder and Prompt Templates. This feature allows teams to createreusable and consistent promptsfor generative AI tasks, ensuring that all users receive uniform responses without having to type in detailed prompts manually every time.
* Einstein Prompt Buildersimplifies the creation of prompts, andPrompt Templatesstandardize the inputs, saving time for sales and service reps.
* Option A (Einstein Recommendation Builder)is more focused on recommendations, not prompt standardization.
* Option B (Einstein Copilot Action: Query Records)is for querying records, not generating AI-driven prompts.
References:
* Salesforce Prompt Builder Overview:https://help.salesforce.com/s/articleView?id=sf.
prompt_builder_overview.htm

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.

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.