nerdexam
Salesforce

AI-201 · Question #176

Universal Containers has a strict change management process that requires all possible configuration to be completed in a sandbox which will be deployed to production. The Agentforce Specialist is tas

The correct answer is C. Create custom fields to store issue, Resolution, and Summary; create a Quick Action that updates. The metadata-deployable components for Work Summaries are the custom fields (Issue, Resolution, Summary) and the Quick Action that updates those fields on the record - these can be built in sandbox and deployed to production via change set or metadata API. Einstein Generative AI

AI Features for Service (e.g., Einstein Bots, Next Best Action)

Question

Universal Containers has a strict change management process that requires all possible configuration to be completed in a sandbox which will be deployed to production. The Agentforce Specialist is tasked with setting up Work Summaries for Enhanced Messaging. Einstein Generative AI is already enabled in production, and the Einstein Work Summaries permission set is already available in production. Which other configuration steps should the Agentforce Specialist take in the sandbox that can be deployed to the production org?

Options

  • ACreate custom fields to store issue, Resolution, and Summary; create a Quick Action that updates
  • BFrom the Epstein setup menu, select Turn on Einstein: create custom fields to store Issue,
  • CCreate custom fields to store issue, Resolution, and Summary; create a Quick Action that updates

How the community answered

(27 responses)
  • A
    7% (2)
  • B
    19% (5)
  • C
    74% (20)

Explanation

The metadata-deployable components for Work Summaries are the custom fields (Issue, Resolution, Summary) and the Quick Action that updates those fields on the record - these can be built in sandbox and deployed to production via change set or metadata API. Einstein Generative AI enablement and the Einstein Work Summaries permission set assignment are org-level activation steps that must be performed directly in production and cannot be included in a sandbox deployment package. Option A describes similar steps but may include non-deployable Einstein toggle configuration. Option B is incorrect because toggling Einstein settings from the setup menu is a production-only activation step and is not sandbox-deployable.

Topics

#Einstein Work Summaries#Generative AI#Custom Fields#Quick Actions

Community Discussion

No community discussion yet for this question.

Full AI-201 Practice