In order to access and create custom prompt templates inPrompt Builder, the AI Specialist must have the Prompt Template Managerpermission set assigned. Without this permission, they will not be able to access Prompt 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:https://help.salesforce.com/s/articleView?id=sf.
prompt_builder_permissions.htm

In Salesforce, when creating a prompt template for the sales team, you can include data from related objects such as Opportunities that are linked to an Account. The best method to ground the AI model and provide relevant information from related records, like Opportunities, is by using merge fields.
Merge fields in Salesforce allow you to dynamically reference data from a record or related records, like Opportunities for a given Account. In this scenario, the AI Specialist needs to pull data from the default related list of Opportunities associated with the Account. This is achieved by using merge fields, which pull in data from the standard relationship Salesforce creates between Accounts and Opportunities.
Option A (referencing a custom related list) and Option C (using formula fields with Einstein-related lists) do not align with the standard, practical grounding method for this task. Custom lists would require additional configurations not typically necessary for a basic use case, and formula fields are typically not used to directly fetch related list data for prompt generation in templates. The standard and straightforward method is using merge fields tied to the default related list of opportunities.
Salesforce References:
* Merge Fields in Templates: https://help.salesforce.com/s/articleView?id=000387601&type=1
* Grounding Data in Prompts: https://developer.salesforce.com/docs/atlas.en-us.salesforce_ai.meta
/salesforce_ai/grounding_data_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).

Einstein Copilotimplementation would be most advantageous inSalesforce Service Cloudwhen the goal is to streamline customer support processes and improve response times. Einstein Copilot can assist agents by providing real-time suggestions, automating repetitive tasks, and generating contextual responses, thus enhancing service efficiency.
* Option B (data security)is not the primary focus of Einstein Copilot, which is more about improving operational efficiency.
* Option C (marketing campaigns)falls outside the scope of Service Cloud and Einstein Copilot's primary benefits, which are aimed at improving customer service and case management.
For further reading, refer toSalesforce documentation on Einstein Copilot for Service Cloudand how it improves support processes.