Salesforce Agentforce-Specialist - Salesforce Certified Agentforce Specialist (AI-201) Spring 26 Update

As documented in the AgentForce Prompt Template and BYOLLM (Bring-Your-Own-LLM) Deployment Guide, each prompt template references a specific LLM configuration by name and ID. When migrating components between environments (e.g., from sandbox to production), the referenced LLM must also exist in the target org with the exact same name and identifier.

If the LLM configuration is missing or named differently in production, the deployment fails, as the prompt template cannot resolve its model dependency.

Option A is incorrect because specifying a custom LLM type does not resolve the missing configuration issue. Option B is incorrect because BYOLLM is supported in production, provided it is correctly registered.

Therefore, the error occurs because the LLM name or configuration ID does not match between sandbox and production, making Option C the correct answer.

Comprehensive and Detailed Explanation From Exact Extract of AgentForce Documents:

According to the AgentForce Troubleshooting and Optimization Guide, hallucinations — instances where the agent fabricates details such as weblinks or data — often occur due to issues in prompt construction or retrieved content grounding. The recommended diagnostic process involves inspecting the prompt template instructions and reviewing the resolved prompt output, including the actual retrieved knowledge chunks.

By examining these areas, the AgentForce Specialist can determine whether the hallucinated content originates from ambiguous prompt phrasing, missing grounding variables, or irrelevant retrieval results. This approach ensures an evidence-based investigation directly linked to the agent’s reasoning and generation steps.

Option A is incorrect because hallucination guardrails are defined in prompts and actions, not topic names or classification descriptions. Option C is also incorrect since simply adding “ALWAYS” to instructions does not enforce factual grounding and is not a documented troubleshooting method.

Therefore, per AgentForce best practices, the correct process is Option B – Examine the prompt instructions and contents of the chunks in the resolved prompt output.

Why is " Salesforce Knowledge is not enabled " the correct answer?

If an administrator only sees the file upload option in Einstein Data Libraries and cannot configure a Salesforce Knowledge base, the most likely reason is that Salesforce Knowledge is not enabled in the organization.

Key Considerations for Einstein Data Libraries:

Salesforce Knowledge Integration is Optional

Einstein Data Libraries can pull knowledge data only if Salesforce Knowledge is enabled.

If Knowledge is not activated, the system will default to file uploads as the only available option.

How to Fix This Issue?

The administrator should enable Salesforce Knowledge in Setup → Knowledge Settings.

Once enabled, the option to configure Knowledge-based Data Libraries will become available.

Why Not the Other Options?

❌ A. The current Salesforce org lacks the necessary Einstein for Service permissions

Incorrect because even without certain permissions, the Knowledge option would still be visible but greyed out.

❌ C. The administrator is not using Lightning Experience

Incorrect because Einstein Data Libraries are accessible in both Classic and Lightning, and Lightning does not control Knowledge base visibility.

Agentforce Specialist References

Salesforce AI Specialist Material confirms that Salesforce Knowledge must be enabled for Data Libraries to use Knowledge as a data source​.

Salesforce Certification Guide explicitly states that file uploads are the default option if Knowledge is not available.

According to the AgentForce Data Governance and RAG Security Guidelines, when implementing retrieval-augmented generation (RAG) using Data Cloud search indexes, best practice is to ensure that personally identifiable information (PII) and other sensitive data are never indexed or embedded in the retrieval system.

The documented recommendation is to mask or exclude sensitive fields before creating embeddings or indexing content. This prevents the large language model (LLM) from accessing or generating responses that could inadvertently expose confidential information. Masking can include redacting names, IDs, contact details, or any regulated medical information.

Option A is incorrect because relying solely on prompt instructions does not prevent the retrieval layer from exposing sensitive content. Option B is also incorrect — encryption alone does not mitigate privacy risk since embeddings can still semantically reveal PII if indexed.

Therefore, the correct best practice is Option C – Mask sensitive fields and index only non-PII data, ensuring compliance with security and data privacy standards such as HIPAA and GDPR.

Before creating a Field Generation prompt template in Agentforce, the Specialist must ensure that the target field is available on a Dynamic Form-enabled Lightning page layout. Field Generation prompt templates work by embedding AI-generated suggestions directly into editable record fields on the Lightning record page. This functionality requires Dynamic Forms, which allow fields to be placed and managed as individual components on the Lightning page. Without Dynamic Forms enabled, the AI cannot surface suggestions directly into the field.Generation templates.

The correct answer is C because the company is not asking for a generic quality score; it needs evaluation against a proprietary de-escalation framework and empathy standard. Salesforce Testing Center supports LLM-judge style evaluations where a judge model compares the agent response against task criteria. For a custom rubric, the specialist should create a custom evaluation and provide a tailored prompt that defines the exact framework criteria. Option A is wrong because standard Coherence is not intended to be rewritten into a proprietary policy rubric. Option B is also too generic because default instruction adherence does not necessarily understand UC’s internal de-escalation model. Custom evaluation is the right mechanism for organization-specific qualitative standards.

The Einstein Trust Layer is designed to ensure transparency, compliance, and security for organizations leveraging Salesforce’s AI and generative AI capabilities. Specifically, for auditing, tracking, and viewing masked data, organizations can utilize:

Audit Trail in Data Cloud: The audit trail captures and stores all prompts submitted to large language models (LLMs), ensuring that sensitive or masked data interactions are logged. This allows organizations to monitor and audit all AI-generated outputs, ensuring that data handling complies with internal and regulatory guidelines. The Data Cloud provides the infrastructure for managing and accessing this audit data.

Why not B? Using Prompt Builder in Setup to send prompts to the LLM is for creating and managing prompts, not for auditing or tracking data. It does not interact directly with the audit trail functionality.

Why not C? Although the audit trail can be accessed in Setup, the user-generated prompts are primarily tracked in the Data Cloud for broader control, auditing, and analysis. Setup is not the primary tool for exporting or managing these audit logs.

More information on auditing AI interactions can be found in the Salesforce AI Trust Layer documentation, which outlines how organizations can manage and track generative AI interactions securely.

When refining Agent 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 Agent documentation on building and refining custom actions.

Comprehensive and Detailed Explanation From Exact Extract of AgentForce Documents:

According to the AgentForce Prompt Customization and Template Development Guide, when an organization wants to modify or enhance how structured data (like Salesforce records) is summarized or presented by an agent, the correct approach is to create a Record Summary custom prompt template.

Record Summary templates allow specialists to tailor how the agent interprets and communicates record information — such as opportunities, accounts, or sales summaries — ensuring the output aligns with company-specific terminology, tone, and data needs.

Option B, the Knowledge Answer template, is used when the agent must answer queries grounded in unstructured text sources (e.g., Knowledge articles), not structured CRM data. Option C, updating the standard record summary action, is not recommended because it may impact other agents or system actions globally, and Salesforce documentation advises customizing through new templates instead of overwriting defaults.

Therefore, the correct best practice is Option A – Create a Record Summary custom prompt template, providing tailored and controlled responses specific to Universal Containers’ sales summary requirements.