Salesforce Salesforce Agentforce Specialist Practice Exams
Last updated on Oct 21,2026- Exam Code: Salesforce Agentforce Specialist
- Exam Name: Salesforce Agentforce Specialist
- Certification Provider: Salesforce
- Latest update: Oct 21,2026
Question #31
Universal Containers implemented Agentforce for its users. One user complains that an Agent is not deleting activities from the past 7 days.
What is the reason for this issue?
- A . Agentforce does not have the permission to delete the user’s records.
- B . Agentforce Delete Record Action permission is not associated to the user.
- C . Agentforce does not have a standard Delete Record action.
Correct Answer: C
C
Explanation:
Context of the Question
Universal 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 C 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 C 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.
Conclusion
The core reason for the issue is that Agentforce does not support a standard Delete Record action (Choice C).
Salesforce Agentforce Specialist Reference & Documents
Salesforce Official Documentation C Agentforce
(Note: Agentforce may be a pilot or specialized feature; check pilot release notes or official docs for standard actions.)
Salesforce Agentforce Specialist Study Guide
Covers the limitations of certain AI-enabled features regarding record operations.
C
Explanation:
Context of the Question
Universal 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 C 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 C 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.
Conclusion
The core reason for the issue is that Agentforce does not support a standard Delete Record action (Choice C).
Salesforce Agentforce Specialist Reference & Documents
Salesforce Official Documentation C Agentforce
(Note: Agentforce may be a pilot or specialized feature; check pilot release notes or official docs for standard actions.)
Salesforce Agentforce Specialist Study Guide
Covers the limitations of certain AI-enabled features regarding record operations.
Question #32
Universal Containers is rolling out a new generative AI initiative.
Which Prompt Builder limitations should the Agentforce Specialist be aware of?
- A . Rich text area fields are only supported in Flex template types.
- B . Creations or updates to the prompt templates are not recorded in the Setup Audit Trail.
- C . Custom objects are supported only for Flex template types.
Correct Answer: C
C
Explanation:
The Prompt Builder in Salesforce has some specific limitations, one of which is that custom objects are supported only for Flex template types. This means that users must rely on Flex templates to integrate custom objects into their prompts.
Option A: While rich text area fields have certain restrictions, this does not pertain to the core limitation of integrating custom objects.
Option B: Updates and creations for prompt templates are indeed recorded in the Setup Audit Trail, so this statement is incorrect.
Option C: This is the correct answer as it reflects a documented limitation of the Prompt Builder.
Reference: "Prompt Builder Limitations | Salesforce Documentation" .
C
Explanation:
The Prompt Builder in Salesforce has some specific limitations, one of which is that custom objects are supported only for Flex template types. This means that users must rely on Flex templates to integrate custom objects into their prompts.
Option A: While rich text area fields have certain restrictions, this does not pertain to the core limitation of integrating custom objects.
Option B: Updates and creations for prompt templates are indeed recorded in the Setup Audit Trail, so this statement is incorrect.
Option C: This is the correct answer as it reflects a documented limitation of the Prompt Builder.
Reference: "Prompt Builder Limitations | Salesforce Documentation" .
Question #33
Universal Containers (UC) would like to implement the Sales Development Representative (SDR) Agent.
Which channel consideration should UC be aware of while implementing it?
- A . SDR Agent must be deployed in the Messaging channel.
- B . SDR Agent only works in the Email channel.
- C . SDR Agent must also be deployed on the company website.
Correct Answer: A
A
Explanation:
Comprehensive and Detailed In-Depth
Universal Containers (UC) is implementing the Agentforce Sales Development Representative (SDR) Agent, a prebuilt AI agent designed to qualify leads and schedule meetings. Channel considerations are critical for deployment. Let’s evaluate the options based on official Salesforce documentation.
Option A: SDR Agent must be deployed in the Messaging channel.
The Agentforce SDR Agent is designed to engage prospects in real-time conversations, primarily through the Messaging channel (e.g., Salesforce Messaging for in-app or web chat). This aligns with its purpose of qualifying leads interactively and scheduling meetings, as outlined in Agentforce for Sales documentation. While it may leverage email for follow-ups, its core deployment and interaction occur via Messaging, making this a key consideration UC must be aware of. This is the correct answer.
Option B: SDR Agent only works in the Email channel.
The SDR Agent is not limited to email. While it can send emails (e.g., follow-ups after lead qualification), its primary function―real-time lead engagement―relies on Messaging. Stating it "only works in the Email channel" is inaccurate and contradicts its documented capabilities, making this incorrect.
Option C: SDR Agent must also be deployed on the company website.
While the SDR Agent can be embedded on a company website via Messaging (e.g., as a chat widget), this is an implementation choice, not a mandatory requirement. The agent’s deployment is channel-specific (Messaging), and website integration is optional, not a "must." This option overstates the requirement, making it incorrect.
Why Option A is Correct:
The SDR Agent’s primary deployment in the Messaging channel is a documented consideration for its real-time lead qualification capabilities. UC must plan for this channel to ensure effective implementation, as per Salesforce guidelines.
Reference: Salesforce Agentforce Documentation: SDR Agent Setup > Channels C Specifies Messaging as the primary channel.
Trailhead: Explore Agentforce Sales Agents C Notes SDR Agent’s Messaging focus for lead engagement.
Salesforce Help: Agentforce for Sales > SDR Agent C Confirms Messaging deployment requirement.
A
Explanation:
Comprehensive and Detailed In-Depth
Universal Containers (UC) is implementing the Agentforce Sales Development Representative (SDR) Agent, a prebuilt AI agent designed to qualify leads and schedule meetings. Channel considerations are critical for deployment. Let’s evaluate the options based on official Salesforce documentation.
Option A: SDR Agent must be deployed in the Messaging channel.
The Agentforce SDR Agent is designed to engage prospects in real-time conversations, primarily through the Messaging channel (e.g., Salesforce Messaging for in-app or web chat). This aligns with its purpose of qualifying leads interactively and scheduling meetings, as outlined in Agentforce for Sales documentation. While it may leverage email for follow-ups, its core deployment and interaction occur via Messaging, making this a key consideration UC must be aware of. This is the correct answer.
Option B: SDR Agent only works in the Email channel.
The SDR Agent is not limited to email. While it can send emails (e.g., follow-ups after lead qualification), its primary function―real-time lead engagement―relies on Messaging. Stating it "only works in the Email channel" is inaccurate and contradicts its documented capabilities, making this incorrect.
Option C: SDR Agent must also be deployed on the company website.
While the SDR Agent can be embedded on a company website via Messaging (e.g., as a chat widget), this is an implementation choice, not a mandatory requirement. The agent’s deployment is channel-specific (Messaging), and website integration is optional, not a "must." This option overstates the requirement, making it incorrect.
Why Option A is Correct:
The SDR Agent’s primary deployment in the Messaging channel is a documented consideration for its real-time lead qualification capabilities. UC must plan for this channel to ensure effective implementation, as per Salesforce guidelines.
Reference: Salesforce Agentforce Documentation: SDR Agent Setup > Channels C Specifies Messaging as the primary channel.
Trailhead: Explore Agentforce Sales Agents C Notes SDR Agent’s Messaging focus for lead engagement.
Salesforce Help: Agentforce for Sales > SDR Agent C Confirms Messaging deployment requirement.
Question #34
Amid their busy schedules, sales reps at Universal Containers dedicate time to follow up with prospects and existing clients via email regarding renewals or new deals. They spend many hours throughout the week reviewing past communications and details about their customers before performing their outreach.
Which standard Agent action helps sales reps draft personalized emails to prospects by generating text based on previous successful communications?
- A . Agent Action: Summarize Record
- B . Agent Action: Find Similar Opportunities
- C . Agent Action: Draft or Revise Sales Email
Correct Answer: C
C
Explanation:
Comprehensive and Detailed In-Depth
UC’s sales reps need an AI action to draft personalized emails based on past successful communications, reducing manual review time. Let’s evaluate the standard Agent actions.
Option A: Agent Action: Summarize Record
"Summarize Record" generates a summary of a record (e.g., Opportunity, Contact), useful for overviews but not for drafting emails or leveraging past communications. This doesn’t meet the requirement, making it incorrect.
Option B: Agent Action: Find Similar Opportunities
"Find Similar Opportunities" identifies past deals to inform strategy, not to draft emails. It provides data, not text generation, making it incorrect.
Option C: Agent Action: Draft or Revise Sales Email
The "Draft or Revise Sales Email" action in Agentforce for Sales (sometimes styled as "Draft Sales Email") uses the Atlas Reasoning Engine to generate personalized email content. It can analyze past successful communications (e.g., via Opportunity or Contact history) to tailor emails for renewals or deals, saving reps time. This directly addresses UC’s need, making it the correct answer.
Why Option C is Correct:
"Draft or Revise Sales Email" is a standard action designed for personalized email generation based
on historical data, aligning with UC’s productivity goal per Salesforce documentation.
Reference: Salesforce Agentforce Documentation: Agentforce for Sales > Draft Sales Email C Details email generation.
Trailhead: Explore Agentforce Sales Agents C Covers email drafting with past data.
Salesforce Help: Sales Features in Agentforce C Confirms personalization capabilities.
C
Explanation:
Comprehensive and Detailed In-Depth
UC’s sales reps need an AI action to draft personalized emails based on past successful communications, reducing manual review time. Let’s evaluate the standard Agent actions.
Option A: Agent Action: Summarize Record
"Summarize Record" generates a summary of a record (e.g., Opportunity, Contact), useful for overviews but not for drafting emails or leveraging past communications. This doesn’t meet the requirement, making it incorrect.
Option B: Agent Action: Find Similar Opportunities
"Find Similar Opportunities" identifies past deals to inform strategy, not to draft emails. It provides data, not text generation, making it incorrect.
Option C: Agent Action: Draft or Revise Sales Email
The "Draft or Revise Sales Email" action in Agentforce for Sales (sometimes styled as "Draft Sales Email") uses the Atlas Reasoning Engine to generate personalized email content. It can analyze past successful communications (e.g., via Opportunity or Contact history) to tailor emails for renewals or deals, saving reps time. This directly addresses UC’s need, making it the correct answer.
Why Option C is Correct:
"Draft or Revise Sales Email" is a standard action designed for personalized email generation based
on historical data, aligning with UC’s productivity goal per Salesforce documentation.
Reference: Salesforce Agentforce Documentation: Agentforce for Sales > Draft Sales Email C Details email generation.
Trailhead: Explore Agentforce Sales Agents C Covers email drafting with past data.
Salesforce Help: Sales Features in Agentforce C Confirms personalization capabilities.
Question #35
An Agentforce Specialist needs to create a prompt template to fill a custom field named Latest Opportunities Summary on the Account object with information from the three most recently opened opportunities.
How should the Agentforce Specialist gather the necessary data for the prompt template?
- A . Select the latest Opportunities related list as a merge field.
- B . Create a flow to retrieve the opportunity information.
- C . Select the Account Opportunity object as a resource when creating the prompt template.
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
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.
Reference: 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)
B
Explanation:
Comprehensive and Detailed In-Depth
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.
Reference: 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)
Question #36
Universal Containers would like to route a service agent conversation to a human agent queue.
Which tool connects the service agent to the human agent queue for escalation?
- A . Outbound Omni-Channel Flow
- B . Screen Flow
- C . Prompt Flow
Correct Answer: A
A
Explanation:
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
o 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 Reference
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.
A
Explanation:
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
o 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 Reference
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.
Question #37
Universal Containers (UC) wants to improve the productivity of its sales team with generative AI
technology. However, UC is concerned that public AI virtual assistants lack adequate company data to general useful responses.
Which solution should UC consider?
- A . fine-tune the Einstein AI model with CBM data.
- B . Build Al model with Einstein discovery and deploy to sales users.
- C . Enable Agentforce and deploy to sales users.
Correct Answer: A
A
Explanation:
Context of the QUESTION N O: Universal Containers (UC) wants to harness generative AI to boost sales productivity. They are wary of public AI virtual assistants (like generic chatbots) that lack sufficient UC-specific data to generate useful business responses.
Why Fine-Tune an Einstein AI Model with CRM Data?
Company-Specific Relevance: By fine-tuning Einstein AI with UC’s CRM data (accounts, opportunities, products, and historical interactions), the model learns the enterprise-specific context. This ensures that the generative outputs are accurate and tailored to UC’s sales scenarios.
Security and Compliance: Using Salesforce Einstein within the Salesforce ecosystem keeps data under UC’s control, aligning with trust, security, and compliance requirements.
Better Predictions: Einstein AI can produce more relevant insights (e.g., recommended next steps, content suggestions, or AI-generated email responses) when it has been trained on real, high-quality internal data.
Why Not Build an AI Model with Einstein Discovery (Option B)?
Einstein Discovery Use Case: Einstein Discovery is best suited for predictive and prescriptive analytics (e.g., analyzing large data sets for patterns, scoring leads, or predicting churn). While it provides advanced analytics, it is not primarily designed for generative text-based interactions for end-user consumption in a conversational format.
Why Not Enable Agentforce (Option C)?
Agentforce Overview: “Agentforce” (sometimes referencing a pilot or non-mainstream name) typically focuses on interactive help or workforce collaboration. It does not inherently solve the
problem of large-scale generative AI using internal CRM data. Moreover, you still need a robust generative engine fine-tuned on company data.
Outcome: Fine-tuning the Einstein AI model with UC’s CRM data (Answer A) is the most direct, Salesforce-native solution to provide generative AI responses that are aligned with UC’s context, driving productivity gains and ensuring data privacy.
Salesforce Agentforce Specialist References & Documents Salesforce Official: Einstein GPT Overview
Discusses how Einstein GPT can be fine-tuned with specific CRM data to deliver contextually relevant, generative AI responses.
Salesforce Trailhead: Get Started with Salesforce Einstein
Explains the fundamentals of AI within the Salesforce platform, including training and optimizing Einstein models.
Salesforce Documentation: Einstein Discovery
Details how Einstein Discovery is primarily used for advanced analytics and predictions, not direct generative text solutions.
Salesforce Agentforce Specialist Study Guide
Provides the official outline of Einstein AI capabilities, referencing how to configure and fine-tune models for specialized enterprise use cases.
A
Explanation:
Context of the QUESTION N O: Universal Containers (UC) wants to harness generative AI to boost sales productivity. They are wary of public AI virtual assistants (like generic chatbots) that lack sufficient UC-specific data to generate useful business responses.
Why Fine-Tune an Einstein AI Model with CRM Data?
Company-Specific Relevance: By fine-tuning Einstein AI with UC’s CRM data (accounts, opportunities, products, and historical interactions), the model learns the enterprise-specific context. This ensures that the generative outputs are accurate and tailored to UC’s sales scenarios.
Security and Compliance: Using Salesforce Einstein within the Salesforce ecosystem keeps data under UC’s control, aligning with trust, security, and compliance requirements.
Better Predictions: Einstein AI can produce more relevant insights (e.g., recommended next steps, content suggestions, or AI-generated email responses) when it has been trained on real, high-quality internal data.
Why Not Build an AI Model with Einstein Discovery (Option B)?
Einstein Discovery Use Case: Einstein Discovery is best suited for predictive and prescriptive analytics (e.g., analyzing large data sets for patterns, scoring leads, or predicting churn). While it provides advanced analytics, it is not primarily designed for generative text-based interactions for end-user consumption in a conversational format.
Why Not Enable Agentforce (Option C)?
Agentforce Overview: “Agentforce” (sometimes referencing a pilot or non-mainstream name) typically focuses on interactive help or workforce collaboration. It does not inherently solve the
problem of large-scale generative AI using internal CRM data. Moreover, you still need a robust generative engine fine-tuned on company data.
Outcome: Fine-tuning the Einstein AI model with UC’s CRM data (Answer A) is the most direct, Salesforce-native solution to provide generative AI responses that are aligned with UC’s context, driving productivity gains and ensuring data privacy.
Salesforce Agentforce Specialist References & Documents Salesforce Official: Einstein GPT Overview
Discusses how Einstein GPT can be fine-tuned with specific CRM data to deliver contextually relevant, generative AI responses.
Salesforce Trailhead: Get Started with Salesforce Einstein
Explains the fundamentals of AI within the Salesforce platform, including training and optimizing Einstein models.
Salesforce Documentation: Einstein Discovery
Details how Einstein Discovery is primarily used for advanced analytics and predictions, not direct generative text solutions.
Salesforce Agentforce Specialist Study Guide
Provides the official outline of Einstein AI capabilities, referencing how to configure and fine-tune models for specialized enterprise use cases.
Question #38
A customer service representative is looking at a custom object that stores travel information. They recently received a weather alert and now need to cancel flights for the customers that are related to this Itinerary. The representative needs to review the Knowledge articles about canceling and rebooking the customer flights.
Which Agentforce capability helps the representative accomplish this?
- A . Invoke a flow which makes a call to external data to create a Knowledge article.
- B . Execute tasks based on available actions, answering questions using information from accessible Knowledge articles.
- C . Generate Knowledge article based off the prompts that the agent enters to create steps to cancel flights.
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
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.
Reference: 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)
B
Explanation:
Comprehensive and Detailed In-Depth
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.
Reference: 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)
Question #39
Universal Containers wants support agents to use Agentforce to ask questions about its product tutorials and product guides.
What should the Agentforce Specialist do to meet this requirement?
- A . Create a prompt template for product tutorials and guides.
- B . Add an Answer Questions custom field in the product object for tutorial instructions.
- C . Publish product tutorials and guides as Knowledge articles.
Correct Answer: C
C
Explanation:
Context of the Question
Universal Containers (UC) wants its support agents to use Agentforce to ask questions about product tutorials and product guides. Agentforce typically references knowledge sources to provide accurate and contextual responses.
Why Knowledge Articles?
Centralized Repository: Publishing product tutorials and guides as Knowledge articles in Salesforce ensures that the information is readily available and searchable by Agentforce.
AI Integration: Salesforce’s AI solutions, including Agentforce, can often be configured to pull content directly from Salesforce Knowledge articles, giving users on-demand answers without manual data duplication.
Maintenance & Updates: Storing content in Salesforce Knowledge simplifies content updates, versioning, and user permissions.
Why Not the Other Options?
Option A (Create a Prompt Template): Creating a prompt template alone does not solve how the underlying content (tutorials, guides) is stored or accessed by Agentforce. Prompt templates shape the queries/responses but do not provide the knowledge base.
Option B (Add an Answer Questions Custom Field): A single field on the product object is insufficient for the depth of information found in tutorials and guides. It also lacks the robust search and user-friendly interface that Knowledge articles provide.
Conclusion
To ensure Agentforce can effectively retrieve and deliver accurate information about products, publishing product tutorials and guides as Knowledge articles is the recommended approach.
Salesforce Agentforce Specialist Reference & Documents
Salesforce Documentation: Set Up Salesforce Knowledge Discusses how to publish articles for easy access
by AI-driven assistants and support teams.
Salesforce Agentforce Specialist Study Guide
Explains best practices for feeding knowledge sources to generative AI and Agentforce.
C
Explanation:
Context of the Question
Universal Containers (UC) wants its support agents to use Agentforce to ask questions about product tutorials and product guides. Agentforce typically references knowledge sources to provide accurate and contextual responses.
Why Knowledge Articles?
Centralized Repository: Publishing product tutorials and guides as Knowledge articles in Salesforce ensures that the information is readily available and searchable by Agentforce.
AI Integration: Salesforce’s AI solutions, including Agentforce, can often be configured to pull content directly from Salesforce Knowledge articles, giving users on-demand answers without manual data duplication.
Maintenance & Updates: Storing content in Salesforce Knowledge simplifies content updates, versioning, and user permissions.
Why Not the Other Options?
Option A (Create a Prompt Template): Creating a prompt template alone does not solve how the underlying content (tutorials, guides) is stored or accessed by Agentforce. Prompt templates shape the queries/responses but do not provide the knowledge base.
Option B (Add an Answer Questions Custom Field): A single field on the product object is insufficient for the depth of information found in tutorials and guides. It also lacks the robust search and user-friendly interface that Knowledge articles provide.
Conclusion
To ensure Agentforce can effectively retrieve and deliver accurate information about products, publishing product tutorials and guides as Knowledge articles is the recommended approach.
Salesforce Agentforce Specialist Reference & Documents
Salesforce Documentation: Set Up Salesforce Knowledge Discusses how to publish articles for easy access
by AI-driven assistants and support teams.
Salesforce Agentforce Specialist Study Guide
Explains best practices for feeding knowledge sources to generative AI and Agentforce.
Question #40
What should An Agentforce consider when using related list merge fields in a prompt template associated with an Account object in Prompt Builder?
- A . The Activities related list on the Account object is not supported because it is a polymorphic field.
- B . If person accounts have been enabled, merge fields will not be available for the Account object.
- C . Prompt generation will yield no response when there is no related list associated with an Account in runtime.
Correct Answer: A
A
Explanation:
When using related list merge fields in a prompt template associated with the Account object in Prompt Builder, the Activities related list is not supported due to it being a polymorphic field. Polymorphic fields can reference multiple different types of objects, which makes them incompatible with some merge field operations in prompt generation.
Option B is incorrect because person accounts do not limit the availability of merge fields for the Account object.
Option C is irrelevant since even if no related lists are available at runtime, the prompt can still generate based on other available data fields.
For more information, refer to Salesforce documentation on supported fields and limitations in Prompt Builder.
A
Explanation:
When using related list merge fields in a prompt template associated with the Account object in Prompt Builder, the Activities related list is not supported due to it being a polymorphic field. Polymorphic fields can reference multiple different types of objects, which makes them incompatible with some merge field operations in prompt generation.
Option B is incorrect because person accounts do not limit the availability of merge fields for the Account object.
Option C is irrelevant since even if no related lists are available at runtime, the prompt can still generate based on other available data fields.
For more information, refer to Salesforce documentation on supported fields and limitations in Prompt Builder.