Salesforce Certified Agentforce Specialist (AI-201)

Why is "Sales rep users are missing the Use SDR Agent permission set" the correct answer?
If sales reps are unable to find the Agentforce Sales Development Representative (SDR) Agent , the most likely cause is missing permissions. The "Use SDR Agent" permission set is required for users to access and interact with the SDR Agent in Agentforce.
Key Considerations for This Issue: Permission Set Restriction Users must have the "Use SDR Agent" permission set to access Agentforce SDR in their Salesforce environment.
If they lack this permission, the SDR Agent will not appear in their interface.
Agentforce Role-Based Access Control
Agentforce assigns specific permissions based on user roles.
Sales reps require explicit permission to access the SDR Agent.
Fixing the Issue

The Salesforce Admin should assign the "Use SDR Agent" permission set to all relevant sales reps.
This is done in Setup # Permission Sets # Assign to Users.

Why Not the Other Options?
# A. Sales rep users' profiles are missing the Allow SDR Agent permission.
Incorrect because "Allow SDR Agent" is not a standard permission setting in Agentforce.
Permission is granted via permission sets , not profile-level settings.

# B. Sales rep users do not have access to the SDR Agent object.

Incorrect because there is no separate "SDR Agent object" in Salesforce.
SDR Agents are AI-driven features , not standard CRM objects that require object-level access.
Agentforce Specialist References Salesforce AI Specialist Material confirms that users require specific permission sets to access Agentforce SDR Agents. Salesforce Instructions for Certification highlight the role of permission sets in controlling Agentforce access.

Comprehensive and Detailed In-Depth Explanation:UC's service team seeks to customize the standard case summary response provided by Agentforce. Let's assess the options for tailoring this output.
Option A: Create a custom Record Summary prompt template for the Case object.In Prompt Builder, the standard Record Summary prompt template generates summaries for objects like Case. To customize it, the Agentforce Specialist can create a new custom prompt template, specifying the Case object as the source, and adjust the instructions (e.g., tone, fields included) to meet UC's needs. This new template can then be invoked by an agent or flow, providing a tailored summary. This approach offers full control and aligns with Salesforce's customization process, making it the correct answer.
Option B: Summarize the Case with a standard Agent action.Standard Agent actions (e.g., "Answer Questions") don't specifically target case summarization--they're broader in scope. There's no out-of-the-box "Summarize Case" action that allows customization of the response format, making this insufficient and incorrect.
Option C: Customize the standard Record Summary template for the Case object.Standard prompt templates in Prompt Builder (e.g., Record Summary) are read-only and cannot be directly edited.
Customization requires cloning or creating a new template, not modifying the standard one, making this incorrect.
Why Option A is Correct:Creating a custom Record Summary prompt template allows full customization of the case summary, leveraging Prompt Builder's flexibility, as per Salesforce best practices.

References:
Salesforce Agentforce Documentation: Prompt Builder > Custom Templates ?Details creating custom
summaries.
Trailhead: Build Prompt Templates in Agentforce ?Explains customizing standard outputs.
Salesforce Help: Record Summaries with AI ?Recommends custom templates for tailored results.

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.
References:
AgentForce BYOLLM Configuration and Deployment Guide --"Managing Model References
Across Environments."

Salesforce Agent is designed to provide a conversational AI interface that can be utilized by different types of Salesforce users, such as developers, sales agents, and retailers. It acts as an AI-powered assistant that facilitates natural interactions with the system, enabling users to perform tasks and access data easily.
This includes tasks like pulling reports, updating records, and generating personalized responses in real time.
Option A is correct because Agent brings a conversational interface that caters to a wide range of users.
Option B and Option C are more focused on developing and training AI models, which are not the primary functions of Agent.
References:
Salesforce Agent Overview: (https://help.salesforce.com/s/articleView?id=einstein_copilot_overview.htm)

Comprehensive and Detailed In-Depth Explanation:In Salesforce Agentforce, prompt templates are used to generate dynamic responses or field values by leveraging an LLM, often with grounding data from Salesforce records or external sources. The scenario describes a Field Generation prompt template that fails intermittently with token limit errors, indicating that the issue is tied to exceeding the LLM's token capacity (e.g., input + output tokens). The random nature of these failures suggests variability in the token count across different records, which is directly addressed by Option B. Prompt templates in Agentforce can be dynamic, meaning they pull in record-specific data (e.g., customer names, descriptions, or other fields) to generate output. Since the data varies by record--some records might have short text fields while others have lengthy ones--the total number of tokens (words, characters, or subword units processed by the LLM) fluctuates. When the token count exceeds the LLM's limit (e.g., 4,096 tokens for some models), the process fails, but this only happens for records with higher token-generating data, explaining the randomness.
Option A: Switching to a "Flex" template type might sound plausible, but Salesforce documentation does not define "Flex" as a specific template type for handling token variability in this context (there are Flow-based templates, but they're unrelated to token limits). This option is a distractor and not a verified solution.
Option C: The LLM's token processing capacity is fixed per model (e.g., a set limit like 128,000 tokens for advanced models) and does not vary with user demand. Demand might affect performance or availability, but not the token limit itself.
Option B is the correct answer because it accurately identifies the dynamic nature of the prompt template as the root cause of variable token counts leading to random failures.

References:
Salesforce Agentforce Documentation: "Prompt Templates" (Salesforce Help: (https://help.salesforce.com/s/articleView?id=sf.agentforce_prompt_templates.htm&type=5)
Trailhead: "Build Prompt Templates for Agentforce" (https:// trailhead.salesforce.com/content/learn/modules/build-prompt-templates-for-agentforce)

Comprehensive and Detailed In-Depth Explanation:UC is using an Einstein Generative AI feature (likely Einstein Sales Emails) to draft personalized emails, but placeholders (e.g., {!Contact.FirstName}) appear instead of actual data from the contact record. Let's analyze the options.
Option A: The user does not have permission to access the fields.Einstein Sales Emails, built on Prompt Builder, pulls data from contact records to populate email drafts. If the user lacks field-level security (FLS) or object-level permissions to access relevant fields (e.g., FirstName, Email), the system cannot retrieve the data, leaving placeholders unresolved. This is a common issue in Salesforce when permissions restrict data access, making it the most likely explanation and the correct answer.
Option B: The user's locale language is not supported by Prompt Builder.Prompt Builder and Einstein Sales Emails support multiple languages, and locale mismatches typically affect formatting or translation, not data retrieval. Placeholders appearing instead of data isn't a documented symptom of language support issues, making this unlikely and incorrect.
Option C: The user does not have Einstein Sales Emails permission assigned.The Einstein Sales Emails permission (part of the Einstein Generative AI license) enables the feature itself. If missing, users couldn't generate drafts at all--not just see placeholders. Since drafts are being created, this permission is likely assigned, making this incorrect.
Why Option A is Correct:Permission restrictions are a frequent cause of unresolved placeholders in Salesforce AI features, as the system respects FLS and sharing rules. This is well-documented in troubleshooting guides for Einstein Generative AI.

References:
Salesforce Help: Einstein Sales Emails > Troubleshooting ?Lists permissions as a cause of data issues.
Trailhead: Set Up Einstein Generative AI ?Emphasizes field access for personalization.

Comprehensive and Detailed 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.
References:
AgentForce Implementation Guide --"Customizing Record Summaries with Prompt Templates."

Einstein Trust Layer's Toxicity Scoring categorizes content on a scale of 0 to 1 , where 1 indicates the highest level of toxicity (e.g., harmful, biased, or inappropriate language). This scoring helps organizations filter unsafe AI-generated content. A score of 1 triggers mitigation actions, such as blocking the response or alerting administrators.
A score of 0 would indicate no toxicity (B is incorrect).

The scoring system does not use "least toxic" as a category (A is misleading).

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.

References:
Salesforce Help Article: Create Custom Actions for Einstein Bots Einstein Bot Developer Guide: "Custom Action Configuration Best Practices" (Section 4.3).

In Salesforce, Generative AI capabilities are controlled by specific permission sets. To use features such as generating summaries with AI, users need to have the correct permission sets that allow access to these functionalities. Generative AI User Permission Set: This is a key permission set required to enable the generative AI capabilities for a user. In this case, the missing Generative AI User permission set prevents the user from seeing the generative AI-enabled field icon.
Without this permission, the generative AI feature in the Competitor Analysis custom object won't be accessible.
Why not A? The Prompt Template User permission set relates specifically to users who need access to prompt templates for interacting with Einstein GPT, but it's not directly related to the visibility of AI-enabled field icons. Why not B? While a prompt template might need to be activated, this is not the primary issue here. The question states that other users with the same profile can see the icon, so the problem is more likely to be permissions-based for this particular user.
For more detailed information, you can review Salesforce documentation on permission sets related to AI capabilities at Salesforce AI Documentation and Einstein GPT permissioning guidelines.