Nail the AI-201: Agentforce Prep That’s Built for Real-World Implementation

When the preview button is greyed out in a Flex prompt template, it is often because the records related to the prompt have not been selected. Flex prompt templates pull data dynamically from Salesforce records, and if there are no records specified for the prompt, it can ' t be previewed since there is no content to generate based on the template.

Option B, not saving or activating the prompt, would not necessarily cause the preview button to be greyed out, but it could prevent proper functionality.

Option C, missing a merge field, would cause issues with the output but would not directly grey out the preview button.

Ensuring that the related records are correctly linked is crucial for testing and previewing how the prompt will function in real use cases.

Salesforce Agentforce Specialist References:

Refer to the documentation on troubleshooting Flex templates here: https://help.salesforce.com/s/articleView?id=sf.flex_prompt_builder_troubleshoot.htm

The correct answer is A. Entitlement data must be available before the reasoning engine decides which subagents or actions are eligible. Setting custom variables in before reasoning ensures the membership tier is hydrated early enough to drive deterministic filters, available when rules, and flow inputs. Option B is wrong because after reasoning occurs too late for initial action visibility and routing decisions in the current reasoning cycle. Option C is wrong because the Agent Router is for routing/classification logic, not the best place to establish reusable entitlement state for action filters and downstream flow logic. The key Agentforce design principle is to make access conditions deterministic before the LLM sees tools. That prevents the agent from offering bronze, silver, or gold actions outside the customer’s actual entitlement level.

The correct answer is B. When legal clauses are nested inside larger sections, overly small chunks can split the clause from surrounding definitions, exceptions, or conditions. That makes the retrieved passage technically relevant but contextually incomplete. A larger chunk size keeps more surrounding legal text together, improving the chance that the retriever returns the clause with its dependencies intact. Option A would usually make the problem worse because it increases fragmentation. Option C is not the best fix because keyword matching can find terms, but it does not preserve the legal structure around those terms. In Data 360 search indexes, chunking strategy and maximum token settings directly affect how much text is included in each retrievable chunk, so tuning chunk size is the right corrective lever.

According to the AgentForce Data Cloud Search Indexing Guide and RAG Optimization Framework, a hybrid search index combines both keyword-based (lexical) and vector-based (semantic) search capabilities. This dual-mode retrieval enables AgentForce to interpret user intent while still honoring exact keyword matches.

In many enterprise scenarios, queries contain a mixture of specific terms (e.g., “contract ID 54321”) and semantic intent (e.g., “renew my subscription”). A purely vector search might overlook exact keywords, while a keyword-only search might miss semantically relevant results. Hybrid indexing ensures that both types of retrieval are available simultaneously — providing the best balance of precision and contextual understanding.

Option A is incorrect because hybrid search still uses embeddings; it doesn’t eliminate them. Option B partially describes the hybrid search process but oversimplifies its purpose — the primary goal isn’t just prefiltering for performance, but combining semantic recall and exact matching for more relevant, balanced results.

Thus, per AgentForce documentation, hybrid search indexes are preferred when organizations need both literal keyword matching and semantic understanding for complex, natural-language queries.

According to the AgentForce for Slack Integration Guide, to connect an Employee Agent (or any internal AgentForce agent) with a Slack channel, the required setup step is to create a connection between Salesforce and the Slack workspace. The documentation specifies: “Before deploying an Employee Agent into Slack, you must establish a secure connection between your Salesforce org and the Slack workspace. This connection enables authentication, permission mapping, and message exchange between the Agent and Slack users.”

Once the connection is established, the administrator can configure the specific Slack channel where the agent will operate.

Option B, involving Omni-Channel flow, applies to Salesforce Service or Support routing, not Slack integration. Option C, Embedded Service Deployment, is used for web or mobile integrations, not Slack. Therefore, Option A accurately aligns with AgentForce’s official integration framework for Slack connectivity.

References (AgentForce Documents / Study Guide):

AgentForce for Slack Integration Guide: “Connecting Salesforce and Slack Workspaces”

AgentForce Employee Agent Setup Notes

Salesforce AgentForce Study Guide: “Deploying Agents into Collaboration Platforms”

The AgentForce Retrieval Configuration Guide outlines that when external data must be filtered by specific criteria—such as WarrantyStatus = Active—the correct approach is to use Hybrid Search with pre-filtering logic defined in a custom retriever. The documentation specifies: “Hybrid search allows combining keyword precision and semantic context. When used with a custom retriever, administrators can pre-filter data on metadata fields (e.g., WarrantyStatus) to ensure that only eligible records are returned.”

Option A (relying on instructions) introduces non-deterministic behavior because the LLM cannot enforce data constraints. Option B (custom variable filtering) applies post-retrieval filtering, which is less efficient and less secure than index-level filtering. Therefore, Option C aligns with Salesforce’s best practice for deterministic, metadata-based retrieval control.

References (AgentForce Documents / Study Guide):

AgentForce Data Cloud Retrieval Guide: “Building Custom Retrievers with Metadata Filters”

Einstein Studio for AgentForce: “Hybrid Search Pre-Filtering”

AgentForce Study Guide: “Filtering Warranty Data by Active Status”

To measure adoption and usability of Agents across the organization, Agentforce Analytics is the right tool. It provides dashboards and reports that track how Agents are being used, which actions are triggered most often, and overall performance trends. This data helps organizations drive adoption by identifying gaps, monitoring usage, and demonstrating business value.

Why is " The data source cannot be changed after it is selected " the correct answer?

When configuring an Agentforce Data Library, the data source selection is permanent. Once a data source is set, it cannot be modified or replaced. This design ensures data consistency, security, and reliability within Salesforce ' s AI-driven environment.

Key Considerations in Agentforce Data Library

Data Source Lock-In

The chosen data source remains fixed to maintain data integrity and avoid inconsistencies.

Any updates or modifications require creating a new Data Library instead of modifying the existing one.

Why Can ' t the Data Source Be Changed?

The data source defines the foundation of AI-driven workflows, and any modification would disrupt processing logic.

Agentforce tools rely on structured datasets to enable AI-powered recommendations, and changing data sources could lead to inconsistencies in grounding techniques.

Workarounds for Changing Data Sources

If an organization needs to use a different data source, a new Agentforce Data Library must be created and configured from scratch.

Old data can be manually migrated into the new data source for continuity.

Why Not the Other Options?

❌ A. The data source can be changed through the Data Cloud settings.

Incorrect because once the data source is linked to an Agentforce Data Library, it cannot be altered, even via Data Cloud settings.

❌ B. The Data Retriever can be reconfigured to use a different data source.

Incorrect as the Data Retriever works within the constraints of the selected data source and does not provide an option to swap data sources post-selection.

Agentforce Specialist References

The Salesforce AI Specialist Material and Salesforce Instructions for the Certification confirm that once a data source is set for an Agentforce Data Library, it cannot be changed​​.

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 setThis 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 setThis 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 setThis 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 PermissionsThe 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 ServiceThis module discusses how permissions are assigned to control Agentforce features, including prompt-related capabilities.

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.

The correct answer is C. In Agent Script, listing a tool in the reasoning.actions block exposes it to the reasoning engine as a callable tool. Salesforce documentation states that tools in reasoning.actions are executable functions the LLM can choose to call based on the tool description and current context. That is not deterministic enough for a mandatory eligibility check. By contrast, Salesforce’s Agent Script action reference states that to ensure an action runs every time a subagent runs, the specialist should use run @actions. < action_name > in the reasoning block. Therefore, run is the correct mechanism for guaranteed execution, while reasoning.actions provides LLM-selectable tool availability.