Free Salesforce Certified Agentforce Specialist (AI-201) Exam Dumps September 2026

When the 'Enrich event logs with conversation data' setting is enabled in Agent, it allows An Agentforce or admin to view session data, including both the user input and copilot responses from interactions over the past 7 days. This data is crucial for monitoring how the copilot is being used, analyzing its performance, and improving future interactions based on past inputs.

This setting enriches the event logs with detailed conversational data for better insights into the interaction history, helping Agentforce Specialists track AI behavior and user engagement.

Option A, viewing the user click path, focuses on navigation but is not part of the conversation data enrichment functionality.

Option C, generating detailed reports over any time period, is incorrect because this specific feature is limited to data for the past 7 days.

Salesforce Agentforce Specialist Reference:

You can refer to this documentation for further insights: https://help.salesforce.com/s/articleView?id=sf.einstein_copilot_event_logging.htm

Universal Containers (UC) has a standard email prompt template (likely a prebuilt template provided by Salesforce) that isn't meeting their needs, and they want to customize it while retaining its original content as a starting point. Let's assess the options based on Agentforce prompt template management practices.

Option A: Save as New Template and edit as needed.In Agentforce Studio's Prompt Builder, there's no explicit 'Save as New Template' option for standard templates. This phrasing suggests creating a new template from scratch, but the question specifies using the content of the existing standard template. Without a direct 'save as' feature for standards, this option is imprecise and less applicable than cloning.

Option B: Clone the existing template and modify as needed.Salesforce documentation confirms that standard prompt templates (e.g., for email drafting or summarization) can be cloned in Prompt Builder. Cloning creates a custom copy of the standard template, preserving its original content and structure while allowing modifications. The Agentforce Specialist can then edit the cloned template---adjusting instructions, grounding, or output format---to meet UC's specific business requirements. This is the recommended approach for customizing standard templates without altering the original, making it the correct answer.

Option C: Save as New Version and edit as needed.Prompt Builder supports versioning for custom templates, allowing users to save new versions of an existing template to track changes. However, standard templates are typically read-only and cannot be versioned directly---versioning applies to custom templates after cloning. The question implies starting with the standard template's content, so cloning precedes versioning. This option is a secondary step, not the initial action, making it incorrect.

Why Option B is Correct:

Cloning is the documented method to repurpose a standard prompt template's content while enabling customization. After cloning, the specialist can modify the new custom template (e.g., tweak the email prompt's tone, structure, or grounding) to align with UC's requirements. This preserves the original standard template and follows Salesforce best practices.

Salesforce Agentforce Documentation: Prompt Builder > Managing Templates -- Details cloning standard templates for customization.

Trailhead: Build Prompt Templates in Agentforce -- Explains how to clone standard templates to create editable copies.

Salesforce Help: Customize Standard Prompt Templates -- Recommends cloning as the first step for modifying prebuilt templates.

In AgentForce documentation on Knowledge Indexing and Chunking Strategies, Salesforce emphasizes that when uploading large volumes of structured content such as HTML or documentation files, the system should use section-aware chunking. The guide states: ''Section-aware chunking preserves the logical boundaries of headings, paragraphs, and sub-sections in structured documents like HTML or PDF files, allowing the agent to retrieve contextually accurate and relevant responses quickly.''

This method ensures that the agent does not split content mid-section or lose contextual relationships between headings and body text. It enhances both retrieval speed and answer precision.

Option A, semantic-based passage extraction, is better suited for free-text knowledge bases, where meaning needs to be inferred. Option B, conversation-based chunking, applies only to chat logs or dialogue histories. For HTML documentation and structured articles, section-aware chunking ensures optimized retrieval and minimal latency in AgentForce responses.

Reference (AgentForce Documents / Study Guide):

AgentForce Knowledge Management Guide: ''Choosing the Right Chunking Strategy''

AgentForce Indexing and Retrieval Optimization Study Notes

AgentForce Developer Handbook: ''Implementing Section-Aware Chunking for Structured Files''

Universal Containers (UC) requires a solution with a custom UX for users to input a sales order number, followed by invoking a custom prompt template to generate and display a summary. Let's evaluate each option based on this requirement and Salesforce Agentforce capabilities.

Option A: Create an autolaunched flow and invoke the prompt template using the standard 'Prompt Template' flow action.

An autolaunched flow is a background process that runs without user interaction, triggered by events like record updates or platform events. While it can invoke a prompt template using the 'Prompt Template' flow action (available in Flow Builder to integrate Agentforce prompts), it lacks a user interface. Since UC explicitly needs a custom UX for users to enter a sales order number, an autolaunched flow cannot meet this requirement, as it doesn't provide a way for users to input data directly.

Option B: Create a template-triggered prompt flow and invoke the prompt template using the standard 'Prompt Template' flow action.

There's no such thing as a 'template-triggered prompt flow' in Salesforce terminology. This appears to be a misnomer or typo in the original question. Prompt templates in Agentforce are reusable configurations that define how an AI processes input data, but they are not a type of flow. Flows (like autolaunched or screen flows) can invoke prompt templates, but 'template-triggered' is not a recognized flow type in Salesforce documentation. This option is invalid due to its inaccurate framing.

Option C: Create a screen flow to collect the sales order number and invoke the prompt template using the standard 'Prompt Template' flow action.

A screen flow provides a customizable user interface within Salesforce, allowing users to input data (e.g., a sales order number) via input fields. The 'Prompt Template' flow action, available in Flow Builder, enables integration with Agentforce by passing user input (the sales order number) to a custom prompt template. The prompt template can then query related data (e.g., sales order header and details) and generate a summary, which can be displayed back to the user on a subsequent screen. This solution meets UC's need for a custom UX and seamless integration with Agentforce prompts, making it the best fit.

Why Option C is Correct:

Screen flows are ideal for scenarios requiring user interaction and custom interfaces, as outlined in Salesforce Flow documentation. The 'Prompt Template' flow action enables Agentforce's AI capabilities within the flow, allowing UC to collect the sales order number, process it via a prompt template, and display the result---all within a single, user-friendly solution. This aligns with Agentforce best practices for integrating AI-driven summaries into user workflows.

Salesforce Help: Flow Builder > Prompt Template Action -- Describes how to use the 'Prompt Template' action in flows to invoke Agentforce prompts.

Trailhead: Build Flows with Prompt Templates -- Highlights screen flows for user-driven AI interactions.

Agentforce Studio Documentation: Prompt Templates -- Explains how prompt templates process input data for summaries.

When a prompt template version is immutable, it means that once the version is activated, it cannot be edited or modified. This ensures consistency in production environments where changes could disrupt workflows.

Option A is incorrect: Any version (not just the latest) can be activated, depending on the use case.

Option D is incorrect: Modifications require manually creating a new version; automatic versioning is not enforced.

Option C is correct: Activation locks the version, enforcing immutability.

Salesforce Help: Prompt Template Versioning

States that 'activated prompt template versions are immutable and cannot be edited.'

In this scenario, the Einstein Copilot capability that best helps the agent is its ability to execute tasks based on available actions and answer questions using 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:

B refers to invoking a flow to create a Knowledge article, which is unrelated to the task of retrieving existing Knowledge articles.

C focuses on generating Knowledge articles, which is not the immediate need for this situation where the agent requires guidance on existing procedures.

Salesforce Documentation on Einstein Copilot

Trailhead Module on Einstein for Service

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.

Salesforce Einstein Documentation on Einstein Copilot Actions

Salesforce AI Documentation on Large Language Models

Comprehensive and Detailed In-Depth Explanation:

UC requires an Agentforce Service Agent to deliver accurate, up-to-date policy and compliance info with specific criteria. Let's evaluate.

* Option A: Enable the agent to search all internal records and past customer inquiries.

Searching all records and inquiries risks irrelevant or outdated responses, conflicting with the need for published Knowledge grounding and immediate updates. This lacks specificity, making it incorrect.

* Option B: Set up an Agentforce Data Library to store and index policy documents for AI retrieval.

The Agentforce Data Library integrates with Salesforce Knowledge, indexing HR policies, compliance guidelines, and procedures for semantic search. It ensures grounding in published Knowledge articles, and updates (e.g., new article versions) are reflected instantly without reconfiguration, as the library syncs with Knowledge automatically. This meets all UC requirements, making it the correct answer.

* Option C: Manually add policy responses into the AI model to prevent hallucinations.

Manually embedding responses into the model isn't feasible---Agentforce uses pretrained LLMs, not custom training. It also doesn't support real-time updates, making this incorrect.

Why Option B is Correct:

The Data Library meets all criteria---semantic search, Knowledge grounding, and instant updates---per Salesforce's recommended approach.

* Salesforce Agentforce Documentation: Data Library > Knowledge Integration -- Details indexing and updates.

* Trailhead: Build Agents with Agentforce -- Covers Data Library for accurate responses.

* Salesforce Help: Grounding with Knowledge -- Confirms real-time sync.

When creating a custom action for Einstein Bots in Salesforce (including Agentforce), Action Instructions are critical for defining how the bot processes and executes the action. These instructions guide the bot on the logic to follow, such as API calls, data transformations, or conditional steps. Testing and iterating on the instructions ensures the bot understands how to handle dynamic inputs, external integrations, and decision-making.

Salesforce documentation emphasizes that Action Instructions directly impact the bot's ability to execute workflows accurately. For example, poorly defined instructions may lead to incorrect API payloads or failure to parse responses. The Einstein Bot Developer Guide highlights that refining instructions is essential for aligning the bot's behavior with business requirements.

In contrast:

Action Name (A) is a static identifier and does not affect functionality.

Action Input (B) defines parameters passed to the action but does not dictate execution logic.

Thus, iterating on Action Instructions (C) ensures the action performs as expected.

Salesforce Help Article: Create Custom Actions for Einstein Bots

Einstein Bot Developer Guide: 'Custom Action Configuration Best Practices' (Section 4.3).

When the 'Enrich event logs with conversation data' setting is enabled in Einstein Copilot, it allows An Agentforce or admin to view session data, including both the user input and copilot responses from interactions over the past 7 days. This data is crucial for monitoring how the copilot is being used, analyzing its performance, and improving future interactions based on past inputs.

This setting enriches the event logs with detailed conversational data for better insights into the interaction history, helping Agentforce Specialists track AI behavior and user engagement.

Option A, viewing the user click path, focuses on navigation but is not part of the conversation data enrichment functionality.

Option C, generating detailed reports over any time period, is incorrect because this specific feature is limited to data for the past 7 days.

Salesforce Agentforce Specialist Reference:

You can refer to this documentation for further insights: https://help.salesforce.com/s/articleView?id=sf.einstein_copilot_event_logging.htm