Free Agentforce-Specialist Practice Test Questions 2026

Explanation

The root cause of users receiving incorrect sales summaries lies in non-unique action instructions (Option B). In Einstein Bots, custom actions are triggered based on how well user utterances align with the action instructions defined for each action. If the instructions for the three custom actions overlap or lack specificity, the bot’s natural language processing (NLP) cannot reliably distinguish between them, leading to mismatched responses.

Steps to Investigate:

Review Action Instructions: Ensure each custom action has distinct, context-specific instructions. For example:
Action 1: "Summarize quarterly sales by region."
Action 2: "Generate a product-wise sales breakdown for the current fiscal year."
Action 3: "Provide a comparison of sales performance between online and in-store channels."
Ambiguous or overlapping instructions (e.g., "Get sales summary") cause confusion.

Test Utterance Matching: Use Einstein Bot’s training tools to validate if user utterances map to the correct action. Overlap indicates instruction ambiguity.

Refine Instructions: Incorporate keywords or phrases unique to each sales summary type to improve intent detection.

Why Other Options Are Incorrect:

A. Assigning actions to an agent is irrelevant, as custom actions are automated bot components.

C. Input/output types relate to data formatting, not intent routing. While important for execution, they don’t resolve utterance mismatches.

Explanation

To integrate web activity data from Data Cloud into a prompt template, the correct approach is to enrich the Contact object with the activity records as a related list and use related list grounding (Option B).

Here’s why:

Data Cloud Integration:
Data Cloud unifies web activity data and associates it with the unified Contact record. By adding these activities as a related list to the Contact, the data becomes accessible to the prompt template.

Prompt Template Grounding:
Salesforce prompt templates support grounding on related records. When the Contact is passed to the prompt template, the template can reference the related web activity records (via the related list) to extract insights.

Structured Data Handling:
This method aligns with Salesforce best practices for grounding, ensuring the large language model (LLM) receives structured, context-rich data without overwhelming it with raw activity lists.

Why Other Options Are Incorrect:

A. Calling the prompt directly from Data Cloud: Prompt templates are invoked within Salesforce, not directly from Data Cloud. Grounding requires associating data with Salesforce objects, not ad-hoc web activity inclusion.

C. Passing a list of activity records as input: While technically possible, this bypasses Salesforce’s grounding framework, which relies on object relationships. It also risks exceeding LLM input limits and lacks scalability.

Explanation

When a customer chat is initiated Einstein Service Replies provides generative AI replies or draft emails based on recommended Knowledge articles. This feature uses the information from the Salesforce Knowledge base to generate responses that are relevant to the customer's query, improving the efficiency and accuracy of customer support interactions.

Option B is correct because Einstein Service Replies is responsible for generating AI-driven responses based on knowledge articles.

Option A (Einstein Reply Recommendations) is focused on recommending replies but does not generate them.

Option C (Einstein Grounding) refers to grounding responses in data but is not directly related to drafting replies.

Explanation

Context of the Question Universal Containers (UC) wants to automatically populate the Description field on the Account object. The AI-driven solution must generate textual data and write it directly into a field.

Field Generation Prompt Template

Primary Use Case: A Field Generation prompt template is specifically designed to create or fill in fields on a record with AI-generated text.

Auto-population: By configuring a Field Generation prompt template, admins can define the instructions, data inputs, and desired output for the AI. The resulting text then populates the specified field, such as the Account Description.

Why Not Flex or Sales Email Prompt Templates?

Flex Prompt Template: Used to combine or manipulate data across objects, merges, or references from multiple sources in more advanced, flexible prompts. Typically not the go-to for straightforward text generation on a single field.

Sales Email Prompt Template: Focused on drafting or summarizing emails for sales reps (like crafting outreach or follow-up messages). This template is not specifically built to populate a field on a record.

Conclusion For automatically populating the Description field with AI-generated content, the Field Generation prompt template (Option A) is the correct choice.

Salesforce Agentforce Specialist References & Documents

Salesforce Documentation: Prompt Template Types Explains various template types (Field Generation, Flex, Email, etc.) and their typical use cases.

Salesforce Agentforce Specialist Study Guide Highlights Field Generation prompt templates for populating or updating record fields with AI-generated text.

Explanation:

As of current Salesforce capabilities:

Einstein Copilot does not support the "Delete Record" action.

This is a platform limitation by design — to maintain data integrity, compliance, and security when interacting with AI.

Even if users have delete permissions in Salesforce, Einstein Copilot:

1. Can create, read, and update records through flows and custom actions.
2. ❌ Cannot delete records directly, even with action configuration or permissions.

This explains why a user cannot use natural language (e.g., "Delete last week's activities") to delete records via Copilot — the capability is not available.

❌ Why the other options are incorrect:

A. Delete Record Action permission is not associated to the user
Misleading — there’s no such specific "Delete Record Action" for Copilot, because delete actions are not supported at all.

B. Einstein Copilot does not have the permission to delete the user's records
Technically true for platform reasons — but this is not the root cause.
Even if it had permission, Copilot simply does not support delete actions.

🔗 References

Salesforce Help — Einstein Copilot Limitations
Salesforce Release Notes — Supported Copilot Actions

Explanation

When refining Einstein Copilot custom action instructions, it is considered best practice to provide examples of user messages that are expected to trigger the action. This helps ensure that the custom action understands a variety of user inputs and can effectively respond to the intent behind the messages.

Option B (consistent phrases) can improve clarity but does not directly refine the triggering logic.

Option C (specifying a persona) is not as crucial as giving examples that illustrate how users will interact with the custom action.

For more details, refer to Salesforce's Einstein Copilot documentation on building and refining custom actions.

Explanation

The key reason for implementing Einstein Copilot is its ability to streamline workflows and automate repetitive tasks. By leveraging AI, Einstein Copilot can assist users in handling mundane, repetitive processes, such as automatically generating insights, completing actions, and guiding users through complex processes, all of which significantly improve operational efficiency.

Option A (Improving data entry and cleansing) is not the primary purpose of Einstein Copilot, as its focus is on guiding and assisting users through workflows.

Option B (Allowing AI to perform tasks without user interaction) does not accurately describe the role of Einstein Copilot, which operates interactively to assist users in real time.

Explanation:

In AgentForce, the Planner Service determines the execution order of multiple custom actions by analyzing their dependencies. Here’s how to configure it:

Dependency Specification

In the custom action’s configuration, explicitly reference the API names of dependent actions.
Example: If Action_B requires output from Action_A, specify Action_A as a dependency in Action_B’s setup.
This ensures the Planner Service sequences actions logically (e.g., Action_A → Action_B → Action_C).

Why Not the Other Options?

B. Profiles/Permissions:
Controls who can run actions, not when they run.

C. LLM Model Provider:
Defines the AI model used for processing, not action sequencing.

Key Benefit:
Avoids errors like race conditions or missing data by enforcing step-by-step execution.

Explanation:

The Einstein Trust Layer provides audit data focused on security and safety, including:

1. Masked Data
Shows how sensitive fields (e.g., emails, phone numbers) were replaced with placeholders (e.g., [EMAIL]) before being sent to the LLM.

2. Toxicity Score
Rates AI-generated content on a 1–5 scale for harmful language (1 = safe, 5 = highly toxic).

Why Not the Other Options?

A. "Response accuracy/offensiveness":
Accuracy isn’t audited by the Trust Layer—it’s measured via user feedback.

B. "Hallucination/bias scores":
These are not part of the Trust Layer’s audit logs.

Accessing Audit Data:
Go to Setup → Security → Einstein Generative AI Audit Data.

Reference:
Salesforce Help - Trust Layer Auditing

Explanation

When a flow is invoked via a custom Agent action, its data access depends on the flow’s runtime configuration, not system mode by default. Salesforce flows can be configured to respect the running user’s permissions and sharing settings:

If the flow is set to "Run as the User Who Launched the Flow" (enabled in Flow Settings), it adheres to the user’s permissions, field-level security (FLS), and sharing rules.

Option C is incorrect because flows do not always run in system mode unless explicitly configured to do so.

Option A is misleading because "with sharing" is an Apex concept, not a flow setting. Flows use runtime settings like FLS and sharing enforcement.

Explanation:

To help sales reps quickly draft personalized emails based on past successful communications, the standard Copilot action to use is:

"Draft or Revise Sales Email"

What it does:

1. Generates context-aware email drafts using:

. Past communications (e.g., emails, call notes).
. CRM data (e.g., {{Opportunity.Amount}}, {{Account.Industry}}).

2. Allows reps to refine tone/length (e.g., "Make it more formal").

Benefit: Saves hours of manual review and drafting.

Why Not the Other Options?

A. "Find Similar Opportunities":
Helps identify comparable deals but doesn’t draft emails.

C. "Summarize Record":
Creates summaries (e.g., of Accounts) but not outreach emails.

Implementation Tip:
Ground the action in Opportunity/Account fields for hyper-relevance.

Reference:
Salesforce Help - Copilot Sales Actions

Explanation

Comprehensive and Detailed In-Depth Explanation: Salesforce Agentforce leverages Prompt Builder, a powerful tool that allows administrators to create and manage prompt templates, which are reusable frameworks for generating AI-driven responses. These templates can be invoked by users to perform specific tasks, such as generating sales emails or summarizing records, based on predefined instructions and grounded data. In this scenario, Universal Containers wants its sales reps to have the ability to only execute these prompt templates, meaning they should be able to run them but not create, edit, or manage them.

Let’s break down the options and analyze why B. Prompt Template User permission set is the correct Answer:

Option A: Prompt Execute Template permission set

This option sounds plausible at first glance because it includes the phrase "Execute Template," which aligns with the requirement. However, there is no specific permission set named "Prompt Execute Template" in Salesforce’s official documentation for Prompt Builder or Agentforce. Salesforce typically uses more standardized naming conventions for permission sets, and this appears to be a distractor option that doesn’t correspond to an actual feature. Permissions in Salesforce are granular, but they are grouped logically under broader permission sets rather than hyper-specific ones like this.

Option B: Prompt Template User permission set

This is the correct answer. In Salesforce, the Prompt Builder feature, which is integral to Agentforce, includes permission sets designed to control access to prompt templates. The "Prompt Template User" permission set is an official Salesforce permission set that grants users the ability to execute(or invoke) prompt templates without giving them the ability to create or modify them. This aligns perfectly with the requirement that sales reps should only execute prompt templates, not manage them. The Prompt Template User permission set typically includes permissions like "Run Prompt Templates," which allows users to trigger templates from interfaces such as Lightning record pages or flows, while restricting access to the Prompt Builder setup area where templates are designed.

Option C: Prompt Template Manager permission set

This option is incorrect because the "Prompt Template Manager" permission set is designed for users who need full administrative control over prompt templates. This includes creating, editing, and deleting templates in Prompt Builder, in addition to executing them. Since Universal Containers only wants sales reps to execute templates and not manage them, this permission set provides more access than required, violating the principle of least privilege—a key security best practice in Salesforce.

How It Works in Salesforce

To implement this, an administrator would: Navigate to Setup > Permission Sets. Locate or create the "Prompt Template User" permission set (this is a standard permission set available with Prompt Builder-enabled orgs). Assign this permission set to the sales reps’ profiles or individual user records.

Ensure the prompt templates are configured and exposed (e.g., via Lightning components like the Einstein Summary component) on relevant pages, such as Opportunity or Account record pages, where sales reps can invoke them.

Why This Matters
By assigning the Prompt Template User permission set, Universal Containers ensures that sales reps can leverage AI-driven prompt templates to enhance productivity (e.g., drafting personalized emails or generating sales pitches) while maintaining governance over who can modify the templates. This separation of duties is critical in a secure Salesforce environment.

References to Official Salesforce Agentforce Specialist Documents
Salesforce Help: Prompt Builder Permissions The official Salesforce documentation outlines permission sets for Prompt Builder, including "Prompt Template User" for execution-only access and "Prompt Template Manager" for full control.

Trailhead: Configure Agentforce for Service This module discusses how permissions are assigned to control Agentforce features, including prompt-related capabilities .E Salesforce Ben: Why Prompt Builder Is Vital in an Agentforce World (November 25, 2024)This resource explains how Prompt Builder integrates with Agentforce and highlights the use of permission sets like Prompt Template User to enable end-user functionality.