Salesforce Salesforce Agentforce Specialist Practice Exams
Last updated on Oct 22,2026- Exam Code: Salesforce Agentforce Specialist
- Exam Name: Salesforce Agentforce Specialist
- Certification Provider: Salesforce
- Latest update: Oct 22,2026
Question #71
When a customer chat is initiated, which functionality in Salesforce provides generative AI replies or draft emails based on recommended Knowledge articles?
- A . Einstein Reply Recommendations
- B . Einstein Service Replies
- C . Einstein Grounding
Correct Answer: B
B
Explanation:
When a customer chat is initiated, Einstein Service Replies provides generative AI replies or draft emails based on recommended Knowledge articles. This feature uses the information from the Salesforce Knowledge base to generate responses that are relevant to the customer’s query, improving the efficiency and accuracy of customer support interactions.
Option B is correct because Einstein Service Replies is responsible for generating AI-driven responses based on knowledge articles.
Option A (Einstein Reply Recommendations) is focused on recommending replies but does not generate them.
Option C (Einstein Grounding) refers to grounding responses in data but is not directly related to drafting replies.
Reference: Einstein Service Replies Overview: https://help.salesforce.com/s/articleView?id=sf.einstein_service_replies.htm
B
Explanation:
When a customer chat is initiated, Einstein Service Replies provides generative AI replies or draft emails based on recommended Knowledge articles. This feature uses the information from the Salesforce Knowledge base to generate responses that are relevant to the customer’s query, improving the efficiency and accuracy of customer support interactions.
Option B is correct because Einstein Service Replies is responsible for generating AI-driven responses based on knowledge articles.
Option A (Einstein Reply Recommendations) is focused on recommending replies but does not generate them.
Option C (Einstein Grounding) refers to grounding responses in data but is not directly related to drafting replies.
Reference: Einstein Service Replies Overview: https://help.salesforce.com/s/articleView?id=sf.einstein_service_replies.htm
Question #72
Universal Containers (UC) has configured an Agentforce Data Library using Knowledge articles. When testing in Agent Builder and the Experience Cloud site, the agent is not responding with grounded Knowledge article information. However, when tested in Prompt Builder, the response returns correctly.
What should UC do to troubleshoot the issue?
- A . Create a new permission set that assigns "Manage Knowledge" and assign it to the Agentforce Service Agent User.
- B . Ensure the assigned User permission set includes access to the prompt template used to access the Knowledge articles.
- C . Ensure the Data Cloud User permission set has been assigned to the Agentforce Service Agent User.
Correct Answer: C
C
Explanation:
Comprehensive and Detailed In-Depth
UC has set up an Agentforce Data Library with Knowledge articles, and while Prompt Builder retrieves the data correctly, the agent fails to do so in Agent Builder and Experience Cloud. Let’s troubleshoot the issue.
Option A: Create a new permission set that assigns "Manage Knowledge" and assign it to the Agentforce Service Agent User.
The "Manage Knowledge" permission is for authoring and managing Knowledge articles, not for reading or retrieving them in an agent context. The Agentforce Service Agent User (a system user) needs read access to Knowledge, not management rights. This option is excessive and irrelevant to the grounding issue, making it incorrect.
Option B: Ensure the assigned User permission set includes access to the prompt template used to access the Knowledge articles.
Prompt templates in Prompt Builder don’t require specific permissions beyond general Einstein Generative AI access. Since the Prompt Builder test works, the template and its grounding are accessible to the testing user. The issue lies with the agent’s runtime access, not the template itself, making this incorrect.
Option C: Ensure the Data Cloud User permission set has been assigned to the Agentforce Service Agent User.
When Knowledge articles are grounded via an Agentforce Data Library, they are often ingested into Data Cloud for indexing and retrieval. The Agentforce Service Agent User, which runs the agent, needs the "Data Cloud User" permission set (or equivalent) to access Data Cloud resources, including the Data Library. If this permission is missing, the agent cannot retrieve Knowledge article data during runtime (e.g., in Agent Builder or Experience Cloud), even though Prompt Builder (running under a different user context) succeeds. This is a common setup oversight and aligns with the symptoms, making it the correct answer.
Why Option C is Correct:
The Agentforce Service Agent User’s lack of Data Cloud access explains the failure in agent-driven contexts while Prompt Builder (likely run by an admin with broader permissions) succeeds. Assigning the "Data Cloud User" permission set resolves this, per Salesforce documentation.
Reference: Salesforce Agentforce Documentation: Data Library Setup > Permissions C Requires Data Cloud access for agents.
Trailhead: Ground Your Agentforce Prompts C Notes Data Cloud User permission for Knowledge grounding.
Salesforce Help: Agentforce Security > Agent User Setup C Lists required permission sets.
C
Explanation:
Comprehensive and Detailed In-Depth
UC has set up an Agentforce Data Library with Knowledge articles, and while Prompt Builder retrieves the data correctly, the agent fails to do so in Agent Builder and Experience Cloud. Let’s troubleshoot the issue.
Option A: Create a new permission set that assigns "Manage Knowledge" and assign it to the Agentforce Service Agent User.
The "Manage Knowledge" permission is for authoring and managing Knowledge articles, not for reading or retrieving them in an agent context. The Agentforce Service Agent User (a system user) needs read access to Knowledge, not management rights. This option is excessive and irrelevant to the grounding issue, making it incorrect.
Option B: Ensure the assigned User permission set includes access to the prompt template used to access the Knowledge articles.
Prompt templates in Prompt Builder don’t require specific permissions beyond general Einstein Generative AI access. Since the Prompt Builder test works, the template and its grounding are accessible to the testing user. The issue lies with the agent’s runtime access, not the template itself, making this incorrect.
Option C: Ensure the Data Cloud User permission set has been assigned to the Agentforce Service Agent User.
When Knowledge articles are grounded via an Agentforce Data Library, they are often ingested into Data Cloud for indexing and retrieval. The Agentforce Service Agent User, which runs the agent, needs the "Data Cloud User" permission set (or equivalent) to access Data Cloud resources, including the Data Library. If this permission is missing, the agent cannot retrieve Knowledge article data during runtime (e.g., in Agent Builder or Experience Cloud), even though Prompt Builder (running under a different user context) succeeds. This is a common setup oversight and aligns with the symptoms, making it the correct answer.
Why Option C is Correct:
The Agentforce Service Agent User’s lack of Data Cloud access explains the failure in agent-driven contexts while Prompt Builder (likely run by an admin with broader permissions) succeeds. Assigning the "Data Cloud User" permission set resolves this, per Salesforce documentation.
Reference: Salesforce Agentforce Documentation: Data Library Setup > Permissions C Requires Data Cloud access for agents.
Trailhead: Ground Your Agentforce Prompts C Notes Data Cloud User permission for Knowledge grounding.
Salesforce Help: Agentforce Security > Agent User Setup C Lists required permission sets.
Question #73
Universal Containers has a strict change management process that requires all possible configuration to be completed in a sandbox which will be deployed to production. The Agentforce Specialist is tasked with setting up Work Summaries for Enhanced Messaging. Einstein Generative AI is already enabled in production, and the Einstein Work Summaries permission set is already available in production.
Which other configuration steps should the Agentforce Specialist take in the sandbox that can be deployed to the production org?
- A . create custom fields to store Issue, Resolution, and Summary; create a Quick Action that updates these fields: add the Wrap Up component to the Messaging Session record paae layout: and create Permission Set Assignments for the intended Agents.
- B . From the Epstein setup menu, select Turn on Einstein: create custom fields to store Issue, Resolution, and Summary: create a Quick Action that updates these fields: and add the wrap up componert to the Messaging session record page layout.
- C . Create custom fields to store issue, Resolution, and Summary; create a Quick Action that updates these fields: and ado the Wrap up component to the Messaging session record page lavcut.
Correct Answer: C
C
Explanation:
Context of the Question
Universal Containers (UC) has a strict change management process that requires all possible configuration be completed in a sandbox and deployed to Production.
Einstein Generative AI is already enabled in Production, and the “Einstein Work Summaries” permission set is already available in Production.
The Agentforce Specialist needs to configure Work Summaries for Enhanced Messaging in the sandbox.
What Can Actually Be Deployed from Sandbox to Production?
o Custom Fields: Metadata that is easily created in sandbox and then deployed.
o Quick Actions: Also metadata-based and can be deployed from sandbox to production.
Layout Components: Page layout changes (such as adding the Wrap Up component) can be added to a change set or deployment package.
Why Option C is Correct
No Need to Turn on Einstein in Sandbox for Deployment: Einstein Generative AI is already enabled in Production; turning it on in the sandbox is typically a manual step if you want to test, but that step itself is not “deployable” in the sense of metadata.
Permission Set Assignments (as in Option A) are not deployable metadata. You can deploy the Permission Set itself but not the specific user assignments. Since the question specifically asks
“Which other configuration steps should be taken in the sandbox that can be deployed to the production org?”, user assignment is not one of them.
Why Not Option A or B?
Option A: Mentions creating permission set assignments for agents. This cannot be directly deployed from sandbox to Production, as permission set assignments are user-specific and considered “data,” not metadata.
Option B: Mentions “Turn on Einstein.” But Einstein Generative AI is already enabled in Production. Additionally, “Turning on Einstein” is typically an org-level setting, not a deployable metadata item.
Conclusion
The main deployable items you can reliably create and test in a sandbox, and then migrate to
Production, are:
Custom Fields (Issue, Resolution, Summary).
o A Quick Action that updates those fields.
o Page Layout Change to include the Wrap Up component.
Therefore, Option C is correct and focuses on actions that are truly deployable as metadata from a sandbox to Production.
Salesforce Agentforce Specialist Reference & Documents
Salesforce Trailhead: Work Summaries with Einstein GPT
Provides an overview of how to configure Work Summaries, including the need for custom fields, quick actions, and UI components.
Salesforce Documentation: Deploying Metadata Between Orgs
Explains what can and cannot be deployed via change sets (e.g., custom fields, page layouts, quick actions vs. user permission set assignments).
Salesforce Agentforce Specialist Study Guide
Outlines which Einstein Generative AI and Work Summaries configurations are deployable as metadata.
C
Explanation:
Context of the Question
Universal Containers (UC) has a strict change management process that requires all possible configuration be completed in a sandbox and deployed to Production.
Einstein Generative AI is already enabled in Production, and the “Einstein Work Summaries” permission set is already available in Production.
The Agentforce Specialist needs to configure Work Summaries for Enhanced Messaging in the sandbox.
What Can Actually Be Deployed from Sandbox to Production?
o Custom Fields: Metadata that is easily created in sandbox and then deployed.
o Quick Actions: Also metadata-based and can be deployed from sandbox to production.
Layout Components: Page layout changes (such as adding the Wrap Up component) can be added to a change set or deployment package.
Why Option C is Correct
No Need to Turn on Einstein in Sandbox for Deployment: Einstein Generative AI is already enabled in Production; turning it on in the sandbox is typically a manual step if you want to test, but that step itself is not “deployable” in the sense of metadata.
Permission Set Assignments (as in Option A) are not deployable metadata. You can deploy the Permission Set itself but not the specific user assignments. Since the question specifically asks
“Which other configuration steps should be taken in the sandbox that can be deployed to the production org?”, user assignment is not one of them.
Why Not Option A or B?
Option A: Mentions creating permission set assignments for agents. This cannot be directly deployed from sandbox to Production, as permission set assignments are user-specific and considered “data,” not metadata.
Option B: Mentions “Turn on Einstein.” But Einstein Generative AI is already enabled in Production. Additionally, “Turning on Einstein” is typically an org-level setting, not a deployable metadata item.
Conclusion
The main deployable items you can reliably create and test in a sandbox, and then migrate to
Production, are:
Custom Fields (Issue, Resolution, Summary).
o A Quick Action that updates those fields.
o Page Layout Change to include the Wrap Up component.
Therefore, Option C is correct and focuses on actions that are truly deployable as metadata from a sandbox to Production.
Salesforce Agentforce Specialist Reference & Documents
Salesforce Trailhead: Work Summaries with Einstein GPT
Provides an overview of how to configure Work Summaries, including the need for custom fields, quick actions, and UI components.
Salesforce Documentation: Deploying Metadata Between Orgs
Explains what can and cannot be deployed via change sets (e.g., custom fields, page layouts, quick actions vs. user permission set assignments).
Salesforce Agentforce Specialist Study Guide
Outlines which Einstein Generative AI and Work Summaries configurations are deployable as metadata.
Question #74
An Agentforce needs to enable the use of Sales Email prompt templates for the sales team. The Agentforce Specialist has already created the templates in Prompt Builder.
According to best practices, which steps should the Agentforce Specialist take to ensure the sales team can use these templates?
- A . Assign the Prompt Template User permission set and enable Sales Emails in Setup.
- B . Assign the Prompt Template Manager permission set and enable Sales Emails in setup.
- C . Assign the Data Cloud Admin permission set and enable Sales Emails in Setup.
Correct Answer: A
A
Explanation:
To enable Sales Email prompt templates:
Permission Set: Assign the Prompt Template User permission set to the sales team to grant access to use pre-built templates.
Feature Activation: Enable Sales Emails in Salesforce Setup to activate the integration between prompt templates and email workflows.
Option B (Manager permission set): Required for creating/modifying templates, not for usage.
Option C (Data Cloud Admin): Unrelated to prompt template access.
Reference: Salesforce Help: Prompt Template Permissions
Specifies that "Prompt Template User" is required to leverage templates in workflows.
Sales Email Setup outlines enabling the feature in Setup.
A
Explanation:
To enable Sales Email prompt templates:
Permission Set: Assign the Prompt Template User permission set to the sales team to grant access to use pre-built templates.
Feature Activation: Enable Sales Emails in Salesforce Setup to activate the integration between prompt templates and email workflows.
Option B (Manager permission set): Required for creating/modifying templates, not for usage.
Option C (Data Cloud Admin): Unrelated to prompt template access.
Reference: Salesforce Help: Prompt Template Permissions
Specifies that "Prompt Template User" is required to leverage templates in workflows.
Sales Email Setup outlines enabling the feature in Setup.
Question #75
A sales manager needs to contact leads at scale with hyper-relevant solutions and customized communications in the most efficient manner possible.
Which Salesforce solution best suits this need?
- A . Einstein Sales Assistant
- B . Prompt Builder
- C . Einstein Lead follow-up
Correct Answer: B
B
Explanation:
Step 1: Define the Requirements
The question specifies a sales manager’s need to:
Contact leads at scale: Handle a large volume of leads simultaneously.
Hyper-relevant solutions: Deliver tailored solutions based on lead-specific data (e.g., CRM data, behavior).
Customized communications: Personalize outreach (e.g., emails, messages) for each lead.
Most efficient manner possible: Minimize manual effort and maximize automation.
This suggests a solution that leverages AI for personalization and automation for scale, ideally within the Salesforce ecosystem.
Step 2: Evaluate the Provided Options
B
Explanation:
Step 1: Define the Requirements
The question specifies a sales manager’s need to:
Contact leads at scale: Handle a large volume of leads simultaneously.
Hyper-relevant solutions: Deliver tailored solutions based on lead-specific data (e.g., CRM data, behavior).
Customized communications: Personalize outreach (e.g., emails, messages) for each lead.
Most efficient manner possible: Minimize manual effort and maximize automation.
This suggests a solution that leverages AI for personalization and automation for scale, ideally within the Salesforce ecosystem.
Step 2: Evaluate the Provided Options
Question #76
After a successful implementation of Agentforce Sates Agent with sales users. Universal Containers now aims to deploy it to the service team.
Which key consideration should the Agentforce Specialist keep in mind for this deployment?
- A . Assign the Agentforce for Service permission to the Service Cloud users.
- B . Assign the standard service actions to Agentforce Service Agent.
- C . Review and test standard and custom Agent topics and actions for Service Center use cases.
Correct Answer: C
C
Explanation:
When deploying Einstein Agent (formerly Agentforce) from Sales to Service Cloud:
Agent Topics and Actions are context-specific. Service Cloud use cases (e.g., case resolution, knowledge retrieval) require validation of existing topics/actions to ensure alignment with service workflows.
Option A: Permissions like "Agentforce for Service" are necessary but secondary to functional compatibility.
Option B: Standard service actions must be mapped to Agentforce, but testing ensures they function as intended.
Reference: Salesforce Help: Einstein Agent Setup
Emphasizes reviewing "topics and actions for different user groups (Sales vs. Service)."
C
Explanation:
When deploying Einstein Agent (formerly Agentforce) from Sales to Service Cloud:
Agent Topics and Actions are context-specific. Service Cloud use cases (e.g., case resolution, knowledge retrieval) require validation of existing topics/actions to ensure alignment with service workflows.
Option A: Permissions like "Agentforce for Service" are necessary but secondary to functional compatibility.
Option B: Standard service actions must be mapped to Agentforce, but testing ensures they function as intended.
Reference: Salesforce Help: Einstein Agent Setup
Emphasizes reviewing "topics and actions for different user groups (Sales vs. Service)."
Question #77
Universal Containers has grounded a prompt template with a related list. During user acceptance testing (UAT), users are not getting the correct responses.
What is causing this issue?
- A . The related list is Read Only.
- B . The related list prompt template option is not enabled.
- C . The related list is not on the parent object’s page layout.
Correct Answer: C
C
Explanation:
Comprehensive and Detailed In-Depth
UC has grounded a prompt template with a related list, but the responses are incorrect during UAT. Grounding with related lists in Agentforce allows the AI to access data from child records linked to a parent object. Let’s analyze the options.
Option A: The related list is Read Only.
Read-only status (e.g., via field-level security or sharing rules) might limit user edits, but it doesn’t inherently prevent the AI from accessing related list data for grounding, as long as the running user (or system context) has read access. This is unlikely to cause incorrect responses and is not a primary consideration, making it incorrect.
Option B: The related list prompt template option is not enabled.
There’s no specific "related list prompt template option" toggle in Prompt Builder. When grounding with a Record Snapshot or Flex template, related lists are included if properly configured (e.g., via object relationships). This option seems to be a misphrasing and doesn’t align with documented settings, making it incorrect.
Option C: The related list is not on the parent object’s page layout.
In Agentforce, grounding with related lists relies on the related list being defined and accessible in the parent object’s metadata, often tied to its presence on the page layout. If the related list isn’t on the layout, the AI might not recognize or retrieve its data correctly, leading to incomplete or incorrect responses. Salesforce documentation notes that related list data availability can depend on layout configuration, making this a plausible and common issue during UAT, and thus the correct answer.
Why Option C is Correct:
The absence of the related list from the parent object’s page layout can disrupt data retrieval for grounding, leading to incorrect AI responses. This is a known configuration consideration in Agentforce setup and testing, as per official guidance.
Reference: Salesforce Agentforce Documentation: Grounding with Related Lists C Notes dependency on page layout configuration.
Trailhead: Ground Your Agentforce Prompts C Highlights related list setup for accurate grounding.
Salesforce Help: Troubleshoot Prompt Responses C Lists layout issues as a common grounding problem.
C
Explanation:
Comprehensive and Detailed In-Depth
UC has grounded a prompt template with a related list, but the responses are incorrect during UAT. Grounding with related lists in Agentforce allows the AI to access data from child records linked to a parent object. Let’s analyze the options.
Option A: The related list is Read Only.
Read-only status (e.g., via field-level security or sharing rules) might limit user edits, but it doesn’t inherently prevent the AI from accessing related list data for grounding, as long as the running user (or system context) has read access. This is unlikely to cause incorrect responses and is not a primary consideration, making it incorrect.
Option B: The related list prompt template option is not enabled.
There’s no specific "related list prompt template option" toggle in Prompt Builder. When grounding with a Record Snapshot or Flex template, related lists are included if properly configured (e.g., via object relationships). This option seems to be a misphrasing and doesn’t align with documented settings, making it incorrect.
Option C: The related list is not on the parent object’s page layout.
In Agentforce, grounding with related lists relies on the related list being defined and accessible in the parent object’s metadata, often tied to its presence on the page layout. If the related list isn’t on the layout, the AI might not recognize or retrieve its data correctly, leading to incomplete or incorrect responses. Salesforce documentation notes that related list data availability can depend on layout configuration, making this a plausible and common issue during UAT, and thus the correct answer.
Why Option C is Correct:
The absence of the related list from the parent object’s page layout can disrupt data retrieval for grounding, leading to incorrect AI responses. This is a known configuration consideration in Agentforce setup and testing, as per official guidance.
Reference: Salesforce Agentforce Documentation: Grounding with Related Lists C Notes dependency on page layout configuration.
Trailhead: Ground Your Agentforce Prompts C Highlights related list setup for accurate grounding.
Salesforce Help: Troubleshoot Prompt Responses C Lists layout issues as a common grounding problem.
Question #78
Universal Containers (UC) currently tracks Leads with a custom object. UC is preparing to implement the Sales Development Representative (SDR) Agent.
Which consideration should UC keep in mind?
- A . Agentforce SDR only works with the standard Lead object.
- B . Agentforce SDR only works on Opportunities.
- C . Agentforce SDR only supports custom objects associated with Accounts.
Correct Answer: A
A
Explanation:
Comprehensive and Detailed In-Depth
Universal Containers (UC) uses a custom object for Leads and plans to implement the Agentforce Sales Development Representative (SDR) Agent. The SDR Agent is a prebuilt, configurable AI agent designed to assist sales teams by qualifying leads and scheduling meetings. Let’s evaluate the options based on its functionality and limitations.
Option A: Agentforce SDR only works with the standard Lead object.
Per Salesforce documentation, the Agentforce SDR Agent is specifically designed to interact with the standard Lead object in Salesforce. It includes preconfigured logic to qualify leads, update lead statuses, and schedule meetings, all of which rely on standard Lead fields (e.g., Lead Status, Email, Phone). Since UC tracks leads in a custom object, this is a critical consideration―they would need to migrate data to the standard Lead object or create a workaround (e.g., mapping custom object data to Leads) to leverage the SDR Agent effectively. This limitation is accurate and aligns with the SDR Agent’s out-of-the-box capabilities.
Option B: Agentforce SDR only works on Opportunities.
The SDR Agent’s primary focus is lead qualification and initial engagement, not opportunity management. Opportunities are handled by other roles (e.g., Account Executives) and potentially other Agentforce agents (e.g., Sales Agent), not the SDR Agent. This option is incorrect, as it misaligns with the SDR Agent’s purpose.
Option C: Agentforce SDR only supports custom objects associated with Accounts.
There’s no evidence in Salesforce documentation that the SDR Agent supports custom objects, even those related to Accounts. The SDR Agent is tightly coupled with the standard Lead object and does not natively extend to custom objects, regardless of their relationships. This option is incorrect.
Why Option A is Correct:
The Agentforce SDR Agent’s reliance on the standard Lead object is a documented constraint. UC must consider this when planning implementation, potentially requiring data migration or process adjustments to align their custom object with the SDR Agent’s capabilities. This ensures the agent can perform its intended functions, such as lead qualification and meeting scheduling.
Reference: Salesforce Agentforce Documentation: SDR Agent Setup C Specifies the SDR Agent’s dependency on the standard Lead object.
Trailhead: Explore Agentforce Sales Agents C Describes SDR Agent functionality tied to Leads.
Salesforce Help: Agentforce Prebuilt Agents C Confirms Lead object requirement for SDR Agent.
A
Explanation:
Comprehensive and Detailed In-Depth
Universal Containers (UC) uses a custom object for Leads and plans to implement the Agentforce Sales Development Representative (SDR) Agent. The SDR Agent is a prebuilt, configurable AI agent designed to assist sales teams by qualifying leads and scheduling meetings. Let’s evaluate the options based on its functionality and limitations.
Option A: Agentforce SDR only works with the standard Lead object.
Per Salesforce documentation, the Agentforce SDR Agent is specifically designed to interact with the standard Lead object in Salesforce. It includes preconfigured logic to qualify leads, update lead statuses, and schedule meetings, all of which rely on standard Lead fields (e.g., Lead Status, Email, Phone). Since UC tracks leads in a custom object, this is a critical consideration―they would need to migrate data to the standard Lead object or create a workaround (e.g., mapping custom object data to Leads) to leverage the SDR Agent effectively. This limitation is accurate and aligns with the SDR Agent’s out-of-the-box capabilities.
Option B: Agentforce SDR only works on Opportunities.
The SDR Agent’s primary focus is lead qualification and initial engagement, not opportunity management. Opportunities are handled by other roles (e.g., Account Executives) and potentially other Agentforce agents (e.g., Sales Agent), not the SDR Agent. This option is incorrect, as it misaligns with the SDR Agent’s purpose.
Option C: Agentforce SDR only supports custom objects associated with Accounts.
There’s no evidence in Salesforce documentation that the SDR Agent supports custom objects, even those related to Accounts. The SDR Agent is tightly coupled with the standard Lead object and does not natively extend to custom objects, regardless of their relationships. This option is incorrect.
Why Option A is Correct:
The Agentforce SDR Agent’s reliance on the standard Lead object is a documented constraint. UC must consider this when planning implementation, potentially requiring data migration or process adjustments to align their custom object with the SDR Agent’s capabilities. This ensures the agent can perform its intended functions, such as lead qualification and meeting scheduling.
Reference: Salesforce Agentforce Documentation: SDR Agent Setup C Specifies the SDR Agent’s dependency on the standard Lead object.
Trailhead: Explore Agentforce Sales Agents C Describes SDR Agent functionality tied to Leads.
Salesforce Help: Agentforce Prebuilt Agents C Confirms Lead object requirement for SDR Agent.
Question #79
Universal Containers (UC) users are complaining that agent answers are not satisfactory. The agent is using PDF files as a knowledge source.
How should UC troubleshoot this issue?
- A . Analyze the data mapping between source fields and Data Cloud object fields.
- B . Check that the agent has the PDF file field permission access for the data library.
- C . Verify the retriever’s filter criteria and data source connection.
Correct Answer: C
C
Explanation:
Why is "Verify the retriever’s filter criteria and data source connection" the correct answer?
If agent answers are not satisfactory when using PDF files as a knowledge source, the issue is likely caused by:
Retriever misconfiguration
If filters are too broad or too restrictive, AI may fail to find relevant information.
o Checking filter logic and retrieval scope helps improve accuracy.
Incorrect data source connection
If the retriever is not properly linked to the PDF storage location, it may fail to retrieve relevant information.
o Ensuring a stable connection between Salesforce Data Cloud and the retriever prevents
retrieval failures.
Parsing Issues with PDF Files
If PDFs are not properly indexed, AI may struggle to extract relevant content.
o Ensuring structured document formatting improves AI comprehension.
Why Not the Other Options?
C
Explanation:
Why is "Verify the retriever’s filter criteria and data source connection" the correct answer?
If agent answers are not satisfactory when using PDF files as a knowledge source, the issue is likely caused by:
Retriever misconfiguration
If filters are too broad or too restrictive, AI may fail to find relevant information.
o Checking filter logic and retrieval scope helps improve accuracy.
Incorrect data source connection
If the retriever is not properly linked to the PDF storage location, it may fail to retrieve relevant information.
o Ensuring a stable connection between Salesforce Data Cloud and the retriever prevents
retrieval failures.
Parsing Issues with PDF Files
If PDFs are not properly indexed, AI may struggle to extract relevant content.
o Ensuring structured document formatting improves AI comprehension.
Why Not the Other Options?
Question #80
Universal Containers wants to incorporate the current order fulfillment status into a prompt for a large language model (LLM). The order status is stored in the external enterprise resource planning (ERP) system.
Which data grounding technique should the Agentforce Specialist recommend?
- A . Eternal Object Record Merge Fields
- B . External Services Merge Fields
- C . Apex Merge Fields
Correct Answer: A
A
Explanation:
Context of the Requirement:
Universal Containers wants to pull in real-time order status data from an external ERP system into an LLM prompt.
Data Grounding in LLM Prompts:
Data grounding ensures the Large Language Model has access to the most current and relevant information. In Salesforce, one recommended approach is to use External Objects (via Salesforce Connect) when data resides outside of Salesforce.
Why External Object Record Merge Fields:
External Objects appear much like standard or custom objects but map to tables in external systems.
You can reference fields from these External Objects in merge fields, allowing real-time data retrieval from the external ERP system without storing that data natively in Salesforce.
This is a simpler “point-and-reference” approach compared to coding custom Apex or configuring external services for direct prompt embedding.
Why Not External Services Merge Fields or Apex Merge Fields:
External Services Merge Fields typically leverage flows or external service definitions. While feasible, it is more about orchestrating or invoking external services for automation (e.g., Flow). It’s not the standard approach for seamlessly referencing external record data in prompt merges.
Apex Merge Fields would imply custom Apex code controlling the prompt insertion. While possible, it’s less “clicks not code” friendly and is not the default method for referencing typical record data.
Reference and Study Resources:
o Salesforce Help & Training → Salesforce Connect and External Objects
o Salesforce Trailhead → “Integrate External Data with Salesforce Connect”
Salesforce Agentforce Specialist Study Resources (documentation regarding how to ground LLM prompts using External Objects)
A
Explanation:
Context of the Requirement:
Universal Containers wants to pull in real-time order status data from an external ERP system into an LLM prompt.
Data Grounding in LLM Prompts:
Data grounding ensures the Large Language Model has access to the most current and relevant information. In Salesforce, one recommended approach is to use External Objects (via Salesforce Connect) when data resides outside of Salesforce.
Why External Object Record Merge Fields:
External Objects appear much like standard or custom objects but map to tables in external systems.
You can reference fields from these External Objects in merge fields, allowing real-time data retrieval from the external ERP system without storing that data natively in Salesforce.
This is a simpler “point-and-reference” approach compared to coding custom Apex or configuring external services for direct prompt embedding.
Why Not External Services Merge Fields or Apex Merge Fields:
External Services Merge Fields typically leverage flows or external service definitions. While feasible, it is more about orchestrating or invoking external services for automation (e.g., Flow). It’s not the standard approach for seamlessly referencing external record data in prompt merges.
Apex Merge Fields would imply custom Apex code controlling the prompt insertion. While possible, it’s less “clicks not code” friendly and is not the default method for referencing typical record data.
Reference and Study Resources:
o Salesforce Help & Training → Salesforce Connect and External Objects
o Salesforce Trailhead → “Integrate External Data with Salesforce Connect”
Salesforce Agentforce Specialist Study Resources (documentation regarding how to ground LLM prompts using External Objects)