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

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.

Why is Outbound Omni-Channel Flow the Correct Answer?

In Agentforce, when a service agent ' s conversation needs to be escalated to a human agent queue, Outbound Omni-Channel Flow is the appropriate tool to facilitate this process.

Key Features of Outbound Omni-Channel Flow in Agentforce:

Automates Escalation to a Human Agent Queue

It ensures that service requests are dynamically routed to the most appropriate human agent, based on availability, skills, and predefined business logic.

Seamless Transition from AI to Human Agents

When Einstein Copilot or another AI-powered assistant identifies a case that requires human intervention, Omni-Channel Flow automatically routes the conversation.

Ensures Proper Prioritization & Load Balancing

By leveraging Omni-Channel routing rules, the system assigns conversations efficiently, avoiding delays in customer service.

Integration with Agentforce and Service Cloud

Works directly with Salesforce Service Cloud to route cases to the appropriate agent queue.

Why Not the Other Options?

❌ B. Screen Flow

Screen Flow is used for interactive guided processes where users manually enter data in predefined steps.

It does not support automated case routing to human agents in real time.

❌ C. Prompt Flow

Prompt Flow is designed to enhance AI-generated responses and workflows rather than routing service agent interactions to human agents.

It lacks Omni-Channel integration, which is necessary for real-time queue management.

Agentforce Specialist References

The importance of using Omni-Channel Flow for routing AI-generated interactions to human agents is supported in the Agentforce Specialist exam objectives and documentation:

Salesforce AI Specialist Material: Covers the importance of Omni-Channel routing for managing AI and human agent interactions​.

Salesforce Instructions for the Certification: Mentions routing AI-driven cases to human agents using automated flows​.

Agentforce Tools Documentation: Highlights Omni-Channel capabilities in Service AI​.

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.

Prompt Builder is designed to help organizations create and configure reusable prompts for large language models (LLMs). By integrating generative AI responses into workflows, Prompt Builder enables customization of AI prompts that interact with Salesforce data and automate complex processes. This tool is especially useful for creating tailored and consistent AI-generated content in various business contexts, including customer service and sales.

It is not a tool for Apex programming (as in option A).

It is also not limited to real-time suggestions as mentioned in option C. Instead, it provides a flexible way for companies to manage and customize how AI-driven responses are generated and used in their workflows.

Salesforce Prompt Builder Overview: https://help.salesforce.com/s/articleView?id=sf.prompt_builder.htm

In Salesforce Agentforce, a prompt template designed to populate a custom field (like " Latest Opportunities Summary " on the Account object) requires dynamic data to be fed into the template for AI to generate meaningful output. Here, the task is to gather data from the three most recently opened opportunities related to an account. The most robust and flexible way to achieve this is by using a Flow (Option B). Salesforce Flows allow the Agentforce Specialist to define logic to query the Opportunity object, filter for the three most recent opportunities (e.g., using a Get Records element with a sort by CreatedDate descending and a limit of 3), and pass this data as variables into the prompt template. This approach ensures precise control over the data retrieval process and can handle complex filtering or sorting requirements.

Option A: Selecting the " latest Opportunities related list as a merge field " is not a valid option in Agentforce prompt templates. Merge fields can pull basic field data (e.g., {!Account.Name}), but they don’t natively support querying or aggregating related list data like the three most recent opportunities.

Option C: There is no " Account Opportunity object " in Salesforce; this seems to be a misnomer (perhaps implying the Opportunity object or a junction object). Even if interpreted as selecting the Opportunity object as a resource, prompt templates don’t directly query related objects without additional logic (e.g., a Flow), making this incorrect.

Option B: Flows integrate seamlessly with prompt templates via dynamic inputs, allowing the Specialist to retrieve and structure the exact data needed (e.g., Opportunity Name, Amount, Close Date) for the AI to summarize.

Thus, Option B is the correct method to gather the necessary data efficiently and accurately.

Salesforce Agentforce Documentation: " Integrate Flows with Prompt Templates " (Salesforce Help: https://help.salesforce.com/s/articleView?id=sf.agentforce_flow_prompt_integration.htm & type=5)

Trailhead: " Build Flows for Agentforce " (https://trailhead.salesforce.com/content/learn/modules/flows-for-agentforce)

The correct answer is A. Agent Script uses standard comparison operators, and Salesforce’s Agent Script operator reference identifies == as the “equal to” comparison operator. The available when clause is conditional visibility logic, so the expression should compare the variable value, such as available when @variables.IsActive == True. Option B is wrong because = and == are not interchangeable in Agent Script conditionals. Option C is wrong because = is used in assignment-style binding or setting contexts, while comparison logic must use ==. This distinction matters because available when determines whether the action is exposed to the reasoning engine. A wrong operator can either fail validation or create unsafe action visibility, which defeats the purpose of deterministic action gating.

The Prompt Builder Best Practices Guide emphasizes including a role instruction in prompts to set tone and communication style. The document explains: “Role-playing instructions (e.g., ‘You are an empathetic customer support agent’) are a best practice for ensuring the LLM adopts the desired persona, tone, and style in responses.”

Option A directly reflects this principle by instructing the LLM to role-play as a character, resulting in empathetic, customer-centric responses.

Option B (listing keywords) provides no tone or intent guidance.

Option C (including full interaction history) risks token overload and redundancy, which can degrade prompt performance.

Thus, Option A aligns with Salesforce’s prompt design best practices for tone and empathy.

References (AgentForce Documents / Study Guide):

Salesforce Prompt Builder Design Guide: “Using Role Instructions for Empathy and Tone”

AgentForce Prompt Engineering Handbook: “Persona and Context in Prompts”

AgentForce Study Guide: “Creating Effective Prompts for Customer-Facing Use Cases”

UC uses Agentforce for Sales to identify similar opportunities, aiding deal closure. Let’s determine a criterion used by the " Find Similar Opportunities " feature.

Option A: Matched opportunities have a status of Closed Won from the last 12 months.Agentforce for Sales analyzes historical data to find similar opportunities, prioritizing " Closed Won " deals as successful examples. Documentation specifies a 12-month lookback period for relevance, ensuring recent, applicable matches. This is a key criterion, making it the correct answer.

Option B: Matched opportunities are limited to the same account.While account context may factor in, Agentforce doesn’t restrict matches to the same account—it considers broader patterns across opportunities (e.g., industry, deal size). This is too narrow and incorrect.

Option C: Matched opportunities were created in the last 12 months.Creation date isn’t a primary criterion—status (e.g., Closed Won) and recency of closure matter more. This doesn’t align with documented behavior, making it incorrect.

Why Option A is Correct:

" Closed Won " status within 12 months is a documented criterion for Agentforce’s similarity matching, providing actionable insights for deal closure.

The correct answer is B. before_reasoning is a deterministic lifecycle block, but it must be understood in relation to the subagent parse/turn lifecycle. If configuration needed immediately after a transition is placed only in the target subagent’s before_reasoning block, the specialist must account for when that target subagent’s next processing cycle begins. Treating before_reasoning as a global setup block or assuming it has already run can leave required variables or context unavailable, which explains stalls or inconsistent behavior. Option A is wrong because before_reasoning is not a once-only immutable initializer. Option C is wrong because it is not limited to the first turn after the whole agent launches. The safer design is to initialize required state explicitly before transition or guard the target subagent’s setup logic carefully.

Context of the QuestionUniversal Containers (UC) uses Agentforce, a specialized AI-driven assistant for Salesforce. A user reports that an Agent is unable to delete recent activities.

Why Agentforce Cannot Delete Records

Agentforce’s Standard Actions: Agentforce typically has predefined or “standard” actions like Create, Update, or Summarize records. However, a standard Delete Record action is not part of the default set of Agentforce actions.

Implication: If Agentforce has no built-in delete functionality, it cannot remove activities—even if the user has permission to delete them in the Salesforce UI.

Why Other Options Are Incorrect

Option A – Permission to Delete the User’s Records: Standard Salesforce user permissions do not automatically extend to Agentforce’s capabilities. Even if the user can delete records, that doesn’t grant Agentforce a new action.

Option B – Agentforce Delete Record Action Permission: There is no separate “Delete Record Action permission” for Agentforce to be toggled. The relevant issue is that the standard Delete Record action does not exist within Agentforce out of the box.

ConclusionThe core reason for the issue is that Agentforce does not support a standard Delete Record action (Choice C).

Salesforce Agentforce Specialist References & Documents

Salesforce Official Documentation – Agentforce(Note: Agentforce may be a pilot or specialized feature; check pilot release notes or official docs for standard actions.)

Salesforce Agentforce Specialist Study GuideCovers the limitations of certain AI-enabled features regarding record operations.