Free Salesforce Agentforce-Specialist Practice Exam with Questions & Answers | Set: 11

The scenario involves a customer service representative needing to cancel flights due to a weather alert and review existing Knowledge articles for guidance on canceling and rebooking. Agentforce provides capabilities to streamline such tasks. The most suitable option is Option B, which allows the agent to " execute tasks based on available actions " (e.g., canceling flights via a predefined action) while " answering questions using information from accessible Knowledge articles. " This capability leverages Agentforce’s ability to integrate Knowledge articles into the agent’s responses, enabling the representative to ask questions (e.g., “How do I cancel a flight?”) and receive AI-generated answers grounded in approved Knowledge content. Simultaneously, the agent can trigger actions (e.g., a Flow to update the custom object) to perform the cancellations, meeting all requirements efficiently.

Option A: Invoking a Flow to call external data and create a Knowledge article is unnecessary. The representative needs to review existing articles, not create new ones, and there’s no indication external data is required for this task.

Option B: This is correct. It combines task execution (canceling flights) with Knowledge article retrieval, aligning with the representative’s need to act and seek guidance from existing content.

Option C: Generating a new Knowledge article based on prompts is not relevant. The representative needs to use existing articles, not author new ones, especially in a time-sensitive weather alert scenario.

Option B best supports the representative’s workflow in Agentforce.

Salesforce Agentforce Documentation: " Knowledge Replies and Actions " (Salesforce Help: https://help.salesforce.com/s/articleView?id=sf.agentforce_knowledge_replies.htm & type=5)

Trailhead: " Agentforce for Service " (https://trailhead.salesforce.com/content/learn/modules/agentforce-for-service)

The correct answer is C because approved model governance must be enforced at the platform configuration layer, not left to prompt wording. Einstein Setup includes model provider configuration, where administrators manage which model providers and models are available for generative AI use. If only approved models are enabled there, builders and developers are restricted to the organization’s permitted model set. Option A is wrong because the Einstein Trust Layer provides trust, grounding, masking, and safety services, but it is not the primary place to approve or disable model providers. Option B is not enforceable because system instructions can guide model behavior but cannot restrict platform-level model availability. Salesforce documentation states that model provider access is configured from Einstein Setup under Configure Model Providers.

The correct answer is B because Agent Script is built for hybrid reasoning: flexible LLM-driven conversation plus deterministic procedural control. Declarative prompt text gives the model guidance and conversational flexibility, but it does not guarantee that steps happen in an exact order. Procedural instructions are used when business-critical logic must execute reliably, such as identity verification before a credit check. Salesforce’s Agent Script fundamentals describe the - > arrow as the signal for procedural logic and explain that conditionals, running actions, and setting variables belong in that deterministic logic path. The same guidance distinguishes procedural logic from prompt text assembled for the LLM. Option A is wrong because procedural instructions can run actions that connect to Flows, Apex, or APIs. Option C is a tooling distraction, not a reasoning-pattern distinction.

Action Assertion is the correct metric because the failure is not subagent routing; the agent already selected the correct subagent. The failure is at the tool/action selection layer inside that subagent. Salesforce Testing Center evaluations include subagent assertion and action assertion as separate checks. Subagent Assertion validates whether the utterance was routed to the expected subagent. Action Assertion validates whether the correct required actions were selected or used. Response Evaluation is broader and focuses on the quality of the final answer, such as relevance or accuracy, but it does not specifically isolate missing tool selection. In this scenario, the specialist needs to identify that the agent reached the right area but failed to invoke all required actions, so Action Assertion is the precise metric.

Prompt Builder is explicitly required to create AI-generated summary fields via prompt templates. These fields use natural language instructions to extract or synthesize information (e.g., summarizing contract terms). Time-to-close estimations (A) and lead scores (C) are typically handled by predictive AI (e.g., Einstein Opportunity Scoring) or analytics tools, which do not require Prompt Builder.

1.Context of the Question

oUniversal Container (UC) has used prompt templates to update summary fields on record pages.

oNow, the admin wants to incorporate similar generative AI functionality within a Flow for automation purposes.

2.How to Call a Prompt Template Within a Flow

oFlow Action: Salesforce provides a standard way to invoke generative AI templates or prompts within a Flow step. From the Flow Builder, you can add an “Action” that references the prompt template you created in Prompt Builder.

oOther Options:

Invocable Apex: Possible fallback if there’s no out-of-the-box Flow Action available. However, Salesforce is releasing native Flow integration for AI prompts, making custom Apex less necessary.

Einstein for Flow: A broad label for Salesforce’s generative AI features within Flow. Under the hood, you typically use a “Flow Action” that points to your prompt.

3.Conclusion

oThe easiest out-of-the-box solution is to use a Flow Action referencing the prompt template. Hence, Option B is correct.

Salesforce Agentforce Specialist References & Documents

•Salesforce Trailhead: Use Prompt Templates in Flow

Demonstrates how to add an Action in Flow that calls a prompt template.

•Salesforce Documentation: Einstein GPT for Flow

The Field Generation prompt template type is specifically designed to enable generative AI within the context of a Salesforce record field. To expose this functionality to an end-user, the Agentforce Specialist must associate the template with the form field on the Lightning page (B). This is accomplished using the Lightning App Builder:

The Agentforce Specialist first creates a custom field (often a Long Text Area or Rich Text Area) on the desired object to store the AI-generated output.

In the Lightning App Builder for the object ' s Record Page, the Specialist selects the field component.

In the properties panel for that field component, there is a setting (often a dropdown) to select an active Field Generation Prompt Template.

Once associated, an Einstein icon (or " Generate " button) appears next to the field on the record page, allowing the user to click it to run the prompt, review the AI-generated content, and then decide to use it to populate the field.

Options A and C (using Flows) are methods for calling prompt templates to automate the generation of content or to ground the prompt with more complex data (like related list information). However, for the Field Generation prompt template to be exposed directly to the user for on-demand generation and manual review (the intended user experience for this template type), it must be bound to the field itself on the Lightning Record Page.

Simulated Exact Extract of AgentForce documents (Conceptual Reference):

" The Field Generation prompt template is surfaced to the user via the Lightning Record Page. After the prompt template is created and activated in Prompt Builder, the Agentforce Specialist must edit the Lightning Record Page in the Lightning App Builder. The key step is to select the target field component and, within its property panel, assign the Field Generation Prompt Template from the available dropdown menu. This action binds the generative AI capability directly to the field, displaying the ' Generate ' button to the user to trigger the AI-assisted content creation upon the record. "

Simulated Reference: AgentForce Study Guide, Chapter 3: Prompt Builder, Section 3.2: Field Generation Deployment, p. 55.

When creating a custom action in Agent, one of the available options is to use Flows. Flows are a powerful automation tool in Salesforce, allowing the Agentforce Specialist to define custom logic and actions within the Copilot system. This makes it easy to extend Copilot ' s functionality without needing custom code.

While Apex triggers and SOQL are important Salesforce tools, Flows are the recommended method for creating custom actions within Agent because they are declarative and highly adaptable.

For further guidance, refer to Salesforce Flow documentation and Agent customization resources.

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.

UC has created a custom flow for processing returns and linked it to a new Agent Action for the Agentforce Service Agent, an AI-driven agent for customer service tasks. The agent must have the ability to execute this flow. Let’s assess the options.

Option A: Recreate the flow using the Agentforce agent user.Flows are authored by admins or developers, not " recreated " by specific users like the Agentforce agent user (a system user for agent operations). The issue isn’t the flow’s creation context but its execution permissions. This option is impractical and incorrect.

Option B: Assign the Manage Users permission to the Agentforce Agent user.The " Manage Users " permission allows user management (e.g., creating or editing users), which is unrelated to running flows. This permission is excessive and irrelevant for the Service Agent’s needs, making it incorrect.

Option C: Assign the Run Flows permission to the Agentforce Agent user.The Agentforce Service Agent operates under a dedicated system user (e.g., " Agentforce Agent User " ) with a specific profile or permission set. To execute a flow as part of an Agent Action, this user must have the " Run Flows " permission, either via its profile or a permission set (e.g., Agentforce Service Permissions). This ensures the agent can invoke the custom flow for processing returns, aligning with Salesforce’s security model and Agentforce setup requirements. This is the correct answer.

Why Option C is Correct:

Granting the " Run Flows " permission to the Agentforce Agent user is the standard, documented step to enable flow execution in Agent Actions, ensuring the Service Agent can process returns as intended.