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 #151
Universal Containers wants to leverage the Record Snapshots grounding feature in a prompt template.
What preparations are required?
- A . Configure page layout of the master record type.
- B . Create a field set for all the fields to be grounded.
- C . Enable and configure dynamic form for the object.
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
Universal Containers (UC) aims to use Record Snapshots grounding in a prompt template to provide context from a specific record. Let’s evaluate the preparation steps.
Option A: Configure page layout of the master record type.
While page layouts define field visibility for users, Record Snapshots grounding relies on field accessibility at the object level, not the layout. The AI accesses data based on permissions and configuration, not layout alone, making this insufficient and incorrect.
Option B: Create a field set for all the fields to be grounded.
Record Snapshots in Prompt Builder allow grounding with fields from a record, but you must specify which fields to include. Creating a field set is a recommended preparation step―it groups the fields (e.g., from the object) to be passed to the prompt template, ensuring the AI has the right data. This is a documented best practice for controlling snapshot scope, making it the correct answer.
Option C: Enable and configure dynamic form for the object.
Dynamic Forms enhance UI flexibility but aren’t required for Record Snapshots grounding. The feature pulls data directly from the object, not the form configuration, making this irrelevant and incorrect.
Why Option B is Correct:
Creating a field set ensures the prompt template uses the intended fields for grounding, a key preparation step per Salesforce documentation.
Reference: Salesforce Agentforce Documentation: Prompt Builder > Record Snapshots C Recommends field sets for grounding.
Trailhead: Ground Your Agentforce Prompts C Details field set preparation.
Salesforce Help: Set Up Record Snapshots C Confirms field set usage.
B
Explanation:
Comprehensive and Detailed In-Depth
Universal Containers (UC) aims to use Record Snapshots grounding in a prompt template to provide context from a specific record. Let’s evaluate the preparation steps.
Option A: Configure page layout of the master record type.
While page layouts define field visibility for users, Record Snapshots grounding relies on field accessibility at the object level, not the layout. The AI accesses data based on permissions and configuration, not layout alone, making this insufficient and incorrect.
Option B: Create a field set for all the fields to be grounded.
Record Snapshots in Prompt Builder allow grounding with fields from a record, but you must specify which fields to include. Creating a field set is a recommended preparation step―it groups the fields (e.g., from the object) to be passed to the prompt template, ensuring the AI has the right data. This is a documented best practice for controlling snapshot scope, making it the correct answer.
Option C: Enable and configure dynamic form for the object.
Dynamic Forms enhance UI flexibility but aren’t required for Record Snapshots grounding. The feature pulls data directly from the object, not the form configuration, making this irrelevant and incorrect.
Why Option B is Correct:
Creating a field set ensures the prompt template uses the intended fields for grounding, a key preparation step per Salesforce documentation.
Reference: Salesforce Agentforce Documentation: Prompt Builder > Record Snapshots C Recommends field sets for grounding.
Trailhead: Ground Your Agentforce Prompts C Details field set preparation.
Salesforce Help: Set Up Record Snapshots C Confirms field set usage.
Question #152
Universal Containers, dealing with a high volume of chat inquiries, implements Einstein Work Summaries to boost productivity.
After an agent-customer conversation, which additional information does Einstein generate and fill, apart from the "summary"’
- A . Sentiment Analysis and Emotion Detection
- B . Draft Survey Request Email
- C . Issue and Revolution
Correct Answer: C
C
Explanation:
Einstein Work Summaries automatically generate concise summaries of customer interactions (e.g., chat transcripts). Beyond the "summary" field, it extracts and populates Issue (key problem
discussed) and Resolution (action taken to resolve the issue). These fields help agents and supervisors quickly grasp the conversation’s context without reviewing the full transcript.
Sentiment Analysis and Emotion Detection (Option A): While Einstein Conversation Insights provides sentiment scores and emotion detection, these are separate from Work Summaries. Work Summaries focus on factual summaries, not sentiment.
Draft Survey Request Email (Option B): Not part of Work Summaries. This would require automation tools like Flow or Email Studio.
Issue and Resolution (Option C): Directly referenced in Salesforce documentation as fields populated by Einstein Work Summaries.
Reference: Salesforce Help Article: Einstein Work Summaries
Einstein Work Summaries focus on "key details like Issue and Resolution" alongside summaries.
Contrast with Einstein Conversation Insights for sentiment/emotion analysis.
C
Explanation:
Einstein Work Summaries automatically generate concise summaries of customer interactions (e.g., chat transcripts). Beyond the "summary" field, it extracts and populates Issue (key problem
discussed) and Resolution (action taken to resolve the issue). These fields help agents and supervisors quickly grasp the conversation’s context without reviewing the full transcript.
Sentiment Analysis and Emotion Detection (Option A): While Einstein Conversation Insights provides sentiment scores and emotion detection, these are separate from Work Summaries. Work Summaries focus on factual summaries, not sentiment.
Draft Survey Request Email (Option B): Not part of Work Summaries. This would require automation tools like Flow or Email Studio.
Issue and Resolution (Option C): Directly referenced in Salesforce documentation as fields populated by Einstein Work Summaries.
Reference: Salesforce Help Article: Einstein Work Summaries
Einstein Work Summaries focus on "key details like Issue and Resolution" alongside summaries.
Contrast with Einstein Conversation Insights for sentiment/emotion analysis.
Question #153
Universal Containers (UC) recently rolled out Einstein Generative AI capabilities and has created a custom prompt to summarize case records. Users have reported that the case summaries generated are not returning the appropriate information.
What is a possible explanation for the poor prompt performance?
- A . The prompt template version is incompatible with the chosen LLM.
- B . The data being used for grounding is incorrect or incomplete.
- C . The Einstein Trust Layer is incorrectly configured.
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
UC’s custom prompt for summarizing case records is underperforming, and we need to identify a likely cause. Let’s evaluate the options based on Agentforce and Einstein Generative AI mechanics.
Option A: The prompt template version is incompatible with the chosen LLM.
Prompt templates in Agentforce are designed to work with the Atlas Reasoning Engine, which abstracts the underlying large language model (LLM). Salesforce manages compatibility between prompt templates and LLMs, and there’s no user-facing versioning that directly ties to LLM compatibility. This option is unlikely and not a common issue per documentation.
Option B: The data being used for grounding is incorrect or incomplete.
Grounding is the process of providing context (e.g., case record data) to the AI via prompt templates. If the grounding data―sourced from Record Snapshots, Data Cloud, or other integrations―is incorrect (e.g., wrong fields mapped) or incomplete (e.g., missing key case details), the summaries will be inaccurate. For example, if the prompt relies on Case.Subject but the field is empty or not included, the output will miss critical information. This is a frequent cause of poor performance in generative AI and aligns with Salesforce troubleshooting guidance, making it the correct answer.
Option C: The Einstein Trust Layer is incorrectly configured.
The Einstein Trust Layer enforces guardrails (e.g., toxicity filtering, data masking) to ensure safe and compliant AI outputs. Misconfiguration might block content or alter tone, but it’s unlikely to cause summaries to lack appropriate information unless specific fields are masked unnecessarily. This is less probable than grounding issues and not a primary explanation here.
Why Option B is Correct:
Incorrect or incomplete grounding data is a well-documented reason for subpar AI outputs in Agentforce. It directly affects the quality of case summaries, and specialists are advised to verify grounding sources (e.g., field mappings, Data Cloud queries) when troubleshooting, as per official guidelines.
Reference: Salesforce Agentforce Documentation: Prompt Templates > Grounding C Links poor outputs to grounding issues.
Trailhead: Troubleshoot Agentforce Prompts C Lists incomplete data as a common problem.
Salesforce Help: Einstein Generative AI > Debugging Prompts C Recommends checking grounding data first.
B
Explanation:
Comprehensive and Detailed In-Depth
UC’s custom prompt for summarizing case records is underperforming, and we need to identify a likely cause. Let’s evaluate the options based on Agentforce and Einstein Generative AI mechanics.
Option A: The prompt template version is incompatible with the chosen LLM.
Prompt templates in Agentforce are designed to work with the Atlas Reasoning Engine, which abstracts the underlying large language model (LLM). Salesforce manages compatibility between prompt templates and LLMs, and there’s no user-facing versioning that directly ties to LLM compatibility. This option is unlikely and not a common issue per documentation.
Option B: The data being used for grounding is incorrect or incomplete.
Grounding is the process of providing context (e.g., case record data) to the AI via prompt templates. If the grounding data―sourced from Record Snapshots, Data Cloud, or other integrations―is incorrect (e.g., wrong fields mapped) or incomplete (e.g., missing key case details), the summaries will be inaccurate. For example, if the prompt relies on Case.Subject but the field is empty or not included, the output will miss critical information. This is a frequent cause of poor performance in generative AI and aligns with Salesforce troubleshooting guidance, making it the correct answer.
Option C: The Einstein Trust Layer is incorrectly configured.
The Einstein Trust Layer enforces guardrails (e.g., toxicity filtering, data masking) to ensure safe and compliant AI outputs. Misconfiguration might block content or alter tone, but it’s unlikely to cause summaries to lack appropriate information unless specific fields are masked unnecessarily. This is less probable than grounding issues and not a primary explanation here.
Why Option B is Correct:
Incorrect or incomplete grounding data is a well-documented reason for subpar AI outputs in Agentforce. It directly affects the quality of case summaries, and specialists are advised to verify grounding sources (e.g., field mappings, Data Cloud queries) when troubleshooting, as per official guidelines.
Reference: Salesforce Agentforce Documentation: Prompt Templates > Grounding C Links poor outputs to grounding issues.
Trailhead: Troubleshoot Agentforce Prompts C Lists incomplete data as a common problem.
Salesforce Help: Einstein Generative AI > Debugging Prompts C Recommends checking grounding data first.
Question #154
Universal Containers (UC) is experimenting with using public Generative AI models and is familiar with the language required to get the information it needs. However, it can be time-consuming for both UC’s sales and service reps to type in the prompt to get the information they need, and ensure prompt consistency.
Which Salesforce feature should the company use to address these concerns?
- A . Agent Builder and Action: Query Records.
- B . Einstein Prompt Builder and Prompt Templates.
- C . Einstein Recommendation Builder.
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
UC wants to streamline the use of Generative AI by reducing the time reps spend typing prompts and ensuring consistency, leveraging their existing prompt knowledge. Let’s evaluate the options.
Option A: Agent Builder and Action: Query Records.
Agent Builder in Agentforce Studio creates autonomous AI agents with actions like "Query Records" to fetch data. While this could retrieve information, it’s designed for agent-driven workflows, not for simplifying manual prompt entry or ensuring consistency across user inputs. This doesn’t directly address UC’s concerns and is incorrect.
Option B: Einstein Prompt Builder and Prompt Templates.
Einstein Prompt Builder, part of Agentforce Studio, allows users to create reusable prompt templates that encapsulate specific instructions and grounding for Generative AI (e.g., using public models via the Atlas Reasoning Engine). UC can predefine prompts based on their known language, saving time for reps by eliminating repetitive typing and ensuring consistency across sales and service teams.
Templates can be embedded in flows, Lightning pages, or agent interactions, perfectly addressing UC’s needs. This is the correct answer.
Option C: Einstein Recommendation Builder.
Einstein Recommendation Builder generates personalized recommendations (e.g., products, next best actions) using predictive AI, not Generative AI for freeform prompts. It doesn’t support custom prompt creation or address time/consistency issues for reps, making it incorrect.
Why Option B is Correct:
Einstein Prompt Builder’s prompt templates directly tackle UC’s challenges by standardizing prompts and reducing manual effort, leveraging their familiarity with Generative AI language. This is a core
feature for such use cases, as per Salesforce documentation.
Reference: Salesforce Agentforce Documentation: Einstein Prompt Builder C Details prompt templates for consistency and efficiency.
Trailhead: Build Prompt Templates in Agentforce C Explains time-saving benefits of templates.
Salesforce Help: Generative AI with Prompt Builder C Confirms use for streamlining rep interactions.
B
Explanation:
Comprehensive and Detailed In-Depth
UC wants to streamline the use of Generative AI by reducing the time reps spend typing prompts and ensuring consistency, leveraging their existing prompt knowledge. Let’s evaluate the options.
Option A: Agent Builder and Action: Query Records.
Agent Builder in Agentforce Studio creates autonomous AI agents with actions like "Query Records" to fetch data. While this could retrieve information, it’s designed for agent-driven workflows, not for simplifying manual prompt entry or ensuring consistency across user inputs. This doesn’t directly address UC’s concerns and is incorrect.
Option B: Einstein Prompt Builder and Prompt Templates.
Einstein Prompt Builder, part of Agentforce Studio, allows users to create reusable prompt templates that encapsulate specific instructions and grounding for Generative AI (e.g., using public models via the Atlas Reasoning Engine). UC can predefine prompts based on their known language, saving time for reps by eliminating repetitive typing and ensuring consistency across sales and service teams.
Templates can be embedded in flows, Lightning pages, or agent interactions, perfectly addressing UC’s needs. This is the correct answer.
Option C: Einstein Recommendation Builder.
Einstein Recommendation Builder generates personalized recommendations (e.g., products, next best actions) using predictive AI, not Generative AI for freeform prompts. It doesn’t support custom prompt creation or address time/consistency issues for reps, making it incorrect.
Why Option B is Correct:
Einstein Prompt Builder’s prompt templates directly tackle UC’s challenges by standardizing prompts and reducing manual effort, leveraging their familiarity with Generative AI language. This is a core
feature for such use cases, as per Salesforce documentation.
Reference: Salesforce Agentforce Documentation: Einstein Prompt Builder C Details prompt templates for consistency and efficiency.
Trailhead: Build Prompt Templates in Agentforce C Explains time-saving benefits of templates.
Salesforce Help: Generative AI with Prompt Builder C Confirms use for streamlining rep interactions.
Question #155
Universal Containers wants to reduce overall customer support handling time by minimizing the time spent typing routine answers for common questions in-chat, and reducing the post-chat analysis by suggesting values for case fields.
Which combination of Agentforce for Service features enables this effort?
- A . Einstein Reply Recommendations and Case Classification
- B . Einstein Reply Recommendations and Case Summaries
- C . Einstein Service Replies and Work Summaries
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
Universal Containers (UC) aims to streamline customer support by addressing two goals: reducing in-chat typing time for routine answers and minimizing post-chat analysis by auto-suggesting case field values. In Salesforce Agentforce for Service, Einstein Reply Recommendations and Case Classification (Option A) are the ideal combination to achieve this.
Einstein Reply Recommendations: This feature uses AI to suggest pre-formulated responses based on chat context, historical data, and Knowledge articles. By providing agents with ready-to-use replies for common questions, it significantly reduces the time spent typing routine answers, directly addressing UC’s first goal.
Case Classification: This capability leverages AI to analyze case details (e.g., chat transcripts) and suggest values for case fields (e.g., Subject, Priority, Resolution) during or after the interaction. By automating field population, it reduces post-chat analysis time, fulfilling UC’s second goal.
Option B: While "Einstein Reply Recommendations" is correct for the first part, "Case Summaries" generates a summary of the case rather than suggesting specific field values. Summaries are useful for documentation but don’t directly reduce post-chat field entry time.
Option C: "Einstein Service Replies" is not a distinct, documented feature in Agentforce (possibly a distractor for Reply Recommendations), and "Work Summaries" applies more to summarizing work orders or broader tasks, not case field suggestions in a chat context.
Option A: This combination precisely targets both in-chat efficiency (Reply Recommendations) and post-chat automation (Case Classification).
Thus, Option A is the correct answer for UC’s needs.
Reference: Salesforce Agentforce Documentation: "Einstein Reply Recommendations" (Salesforce Help: https://help.salesforce.com/s/articleView?id=sf.einstein_reply_recommendations.htm&type=5)
Salesforce Agentforce Documentation: "Case Classification" (Salesforce Help: https://help.salesforce.com/s/articleView?id=sf.case_classification.htm&type=5)
Trailhead: "Agentforce for Service" (https://trailhead.salesforce.com/content/learn/modules/agentforce-for-service)
B
Explanation:
Comprehensive and Detailed In-Depth
Universal Containers (UC) aims to streamline customer support by addressing two goals: reducing in-chat typing time for routine answers and minimizing post-chat analysis by auto-suggesting case field values. In Salesforce Agentforce for Service, Einstein Reply Recommendations and Case Classification (Option A) are the ideal combination to achieve this.
Einstein Reply Recommendations: This feature uses AI to suggest pre-formulated responses based on chat context, historical data, and Knowledge articles. By providing agents with ready-to-use replies for common questions, it significantly reduces the time spent typing routine answers, directly addressing UC’s first goal.
Case Classification: This capability leverages AI to analyze case details (e.g., chat transcripts) and suggest values for case fields (e.g., Subject, Priority, Resolution) during or after the interaction. By automating field population, it reduces post-chat analysis time, fulfilling UC’s second goal.
Option B: While "Einstein Reply Recommendations" is correct for the first part, "Case Summaries" generates a summary of the case rather than suggesting specific field values. Summaries are useful for documentation but don’t directly reduce post-chat field entry time.
Option C: "Einstein Service Replies" is not a distinct, documented feature in Agentforce (possibly a distractor for Reply Recommendations), and "Work Summaries" applies more to summarizing work orders or broader tasks, not case field suggestions in a chat context.
Option A: This combination precisely targets both in-chat efficiency (Reply Recommendations) and post-chat automation (Case Classification).
Thus, Option A is the correct answer for UC’s needs.
Reference: Salesforce Agentforce Documentation: "Einstein Reply Recommendations" (Salesforce Help: https://help.salesforce.com/s/articleView?id=sf.einstein_reply_recommendations.htm&type=5)
Salesforce Agentforce Documentation: "Case Classification" (Salesforce Help: https://help.salesforce.com/s/articleView?id=sf.case_classification.htm&type=5)
Trailhead: "Agentforce for Service" (https://trailhead.salesforce.com/content/learn/modules/agentforce-for-service)
Question #156
Universal Containers (UC) is using Einstein Generative AI to generate an account summary. UC aims to ensure the content is safe and inclusive, utilizing the Einstein Trust Layer’s toxicity scoring to assess the content’s safety level.
In the score of 1 indicate?
- A . The response is the least toxic Einstein Generative AI Toxicity Scoring system, what does a toxicity category.
- B . The response is not toxic.
- C . The response is the most toxic.
Correct Answer: C
C
Explanation:
Einstein Trust Layer’s Toxicity Scoring categorizes content on a scale of 0 to 1, where 1 indicates the highest level of toxicity (e.g., harmful, biased, or inappropriate language). This scoring helps organizations filter unsafe AI-generated content. A score of 1 triggers mitigation actions, such as blocking the response or alerting administrators.
A score of 0 would indicate no toxicity (B is incorrect).
The scoring system does not use "least toxic" as a category (A is misleading).
Reference: Salesforce Help Article: Einstein Trust Layer C Toxicity Scoring ("Interpreting Toxicity Scores" section).
Einstein GPT Safety Overview: "Mitigating Harmful Content with Toxicity Detection."
C
Explanation:
Einstein Trust Layer’s Toxicity Scoring categorizes content on a scale of 0 to 1, where 1 indicates the highest level of toxicity (e.g., harmful, biased, or inappropriate language). This scoring helps organizations filter unsafe AI-generated content. A score of 1 triggers mitigation actions, such as blocking the response or alerting administrators.
A score of 0 would indicate no toxicity (B is incorrect).
The scoring system does not use "least toxic" as a category (A is misleading).
Reference: Salesforce Help Article: Einstein Trust Layer C Toxicity Scoring ("Interpreting Toxicity Scores" section).
Einstein GPT Safety Overview: "Mitigating Harmful Content with Toxicity Detection."
Question #157
What is true of Agentforce Testing Center?
- A . Running tests risks modifying CRM data in a production environment.
- B . Running tests does not consume Einstein Requests.
- C . Agentforce Testing Center can only be used in a production environment.
Correct Answer: B
B
Explanation:
Comprehensive and Detailed In-Depth
The Agentforce Testing Center is a tool in Agentforce Studio for validating agent performance. Let’s evaluate the statements.
Option A: Running tests risks modifying CRM data in a production environment.
Agentforce Testing Center runs synthetic interactions in a controlled environment (e.g., sandbox or isolated test space) and doesn’t modify live CRM data. It’s designed for safe pre-deployment testing, making this incorrect.
Option B: Running tests does not consume Einstein Requests.
Einstein Requests are part of the usage quota for Einstein Generative AI features (e.g., prompt executions in production). Testing Center uses synthetic data to simulate interactions without invoking live AI calls that count against this quota. Salesforce documentation confirms tests don’t consume requests, making this the correct answer.
Option C: Agentforce Testing Center can only be used in a production environment.
Testing Center is available in both sandbox and production orgs, but it’s primarily used pre-deployment (e.g., in sandboxes) to validate agents safely. This restriction is false, making it incorrect.
Why Option B is Correct:
Not consuming Einstein Requests is a key feature of Testing Center, allowing extensive testing without impacting quotas, as per Salesforce documentation.
Reference: Salesforce Agentforce Documentation: Testing Center > Overview C Confirms no request consumption.
Trailhead: Test Your Agentforce Agents C Notes quota-free testing.
Salesforce Help: Agentforce Testing C Details safe, isolated testing.
B
Explanation:
Comprehensive and Detailed In-Depth
The Agentforce Testing Center is a tool in Agentforce Studio for validating agent performance. Let’s evaluate the statements.
Option A: Running tests risks modifying CRM data in a production environment.
Agentforce Testing Center runs synthetic interactions in a controlled environment (e.g., sandbox or isolated test space) and doesn’t modify live CRM data. It’s designed for safe pre-deployment testing, making this incorrect.
Option B: Running tests does not consume Einstein Requests.
Einstein Requests are part of the usage quota for Einstein Generative AI features (e.g., prompt executions in production). Testing Center uses synthetic data to simulate interactions without invoking live AI calls that count against this quota. Salesforce documentation confirms tests don’t consume requests, making this the correct answer.
Option C: Agentforce Testing Center can only be used in a production environment.
Testing Center is available in both sandbox and production orgs, but it’s primarily used pre-deployment (e.g., in sandboxes) to validate agents safely. This restriction is false, making it incorrect.
Why Option B is Correct:
Not consuming Einstein Requests is a key feature of Testing Center, allowing extensive testing without impacting quotas, as per Salesforce documentation.
Reference: Salesforce Agentforce Documentation: Testing Center > Overview C Confirms no request consumption.
Trailhead: Test Your Agentforce Agents C Notes quota-free testing.
Salesforce Help: Agentforce Testing C Details safe, isolated testing.
Question #158
Universal Containers wants to allow its service agents to query the current fulfillment status of an order with natural language. There is an existing auto launched flow to query the Information from Oracle ERP, which is the system of record for the order fulfillment process.
How should an Agentforce Specialist apply the power of conversational AI to this use case?
- A . Create a custom Agent action which calls a flow.
- B . Configure the Integration Flow Standard Action in Agent Builder.
- C . Create a Flex prompt template in Prompt Builder.
Correct Answer: A
A
Explanation:
Why is "Create a custom Agent action which calls a flow" the correct answer?
In Agentforce, the best way to allow service agents to query order fulfillment status from an external system (Oracle ERP) using natural language is to create a custom Agent action that invokes an existing autolaunched flow.
Key Considerations for This Approach:
Custom Agent Action Triggers the Flow
A custom Agent action is designed to call Salesforce flows, enabling external system integration.
The flow retrieves real-time fulfillment data from Oracle ERP and returns results to the
agent.
Enables AI-Powered Query Execution
o The Agent can understand natural language and map user utterances to the correct Agent action.
o This ensures that agents receive accurate order fulfillment updates quickly.
No Need for Manual Data Entry
Instead of manually searching Oracle ERP, agents can query fulfillment status using AI-powered Agentforce workflows.
Why Not the Other Options?
B. Configure the Integration Flow Standard Action in Agent Builder
Incorrect because Integration Flow Standard Actions are for predefined use cases, not custom ERP integrations.
They do not provide the flexibility needed to connect with Oracle ERP dynamically.
C. Create a Flex Prompt Template in Prompt Builder
Incorrect because Flex prompts are used for structuring AI-generated responses, not executing queries on external systems.
This approach does not enable the AI to retrieve live fulfillment status from Oracle ERP.
Agentforce Specialist Reference
Salesforce AI Specialist Material confirms that custom Agent actions allow integration with external systems through Salesforce flows.
Salesforce Instructions for Certification mention that Agentforce supports custom Agent actions for external data retrieval.
A
Explanation:
Why is "Create a custom Agent action which calls a flow" the correct answer?
In Agentforce, the best way to allow service agents to query order fulfillment status from an external system (Oracle ERP) using natural language is to create a custom Agent action that invokes an existing autolaunched flow.
Key Considerations for This Approach:
Custom Agent Action Triggers the Flow
A custom Agent action is designed to call Salesforce flows, enabling external system integration.
The flow retrieves real-time fulfillment data from Oracle ERP and returns results to the
agent.
Enables AI-Powered Query Execution
o The Agent can understand natural language and map user utterances to the correct Agent action.
o This ensures that agents receive accurate order fulfillment updates quickly.
No Need for Manual Data Entry
Instead of manually searching Oracle ERP, agents can query fulfillment status using AI-powered Agentforce workflows.
Why Not the Other Options?
B. Configure the Integration Flow Standard Action in Agent Builder
Incorrect because Integration Flow Standard Actions are for predefined use cases, not custom ERP integrations.
They do not provide the flexibility needed to connect with Oracle ERP dynamically.
C. Create a Flex Prompt Template in Prompt Builder
Incorrect because Flex prompts are used for structuring AI-generated responses, not executing queries on external systems.
This approach does not enable the AI to retrieve live fulfillment status from Oracle ERP.
Agentforce Specialist Reference
Salesforce AI Specialist Material confirms that custom Agent actions allow integration with external systems through Salesforce flows.
Salesforce Instructions for Certification mention that Agentforce supports custom Agent actions for external data retrieval.
Question #159
Universal Container’s internal auditing team asks An Agentforce to verify that address information is properly masked in the prompt being generated.
How should the Agentforce Specialist verify the privacy of the masked data in the Einstein Trust Layer?
- A . Enable data encryption on the address field
- B . Review the platform event logs
- C . Inspect the AI audit trail
Correct Answer: C
C
Explanation:
The AI audit trail in Salesforce provides a detailed log of AI activities, including the data used, its handling, and masking procedures applied in the Einstein Trust Layer. It allows the Agentforce Specialist to inspect and verify that sensitive data, such as addresses, is appropriately masked before being used in prompts or outputs.
Enable data encryption on the address field: While encryption ensures data security at rest or in transit, it does not verify masking in AI operations.
Review the platform event logs: Platform event logs capture system events but do not specifically focus on the handling or masking of sensitive data in AI processes.
Inspect the AI audit trail: This is the most relevant option, as it provides visibility into how data is processed and masked in AI activities.
Reference: "How Salesforce Ensures Trust in AI with Einstein Trust Layer | Salesforce" .
C
Explanation:
The AI audit trail in Salesforce provides a detailed log of AI activities, including the data used, its handling, and masking procedures applied in the Einstein Trust Layer. It allows the Agentforce Specialist to inspect and verify that sensitive data, such as addresses, is appropriately masked before being used in prompts or outputs.
Enable data encryption on the address field: While encryption ensures data security at rest or in transit, it does not verify masking in AI operations.
Review the platform event logs: Platform event logs capture system events but do not specifically focus on the handling or masking of sensitive data in AI processes.
Inspect the AI audit trail: This is the most relevant option, as it provides visibility into how data is processed and masked in AI activities.
Reference: "How Salesforce Ensures Trust in AI with Einstein Trust Layer | Salesforce" .
Question #160
Universal Containers recently added a custom flow for processing returns and created a new Agent Action.
Which action should the company take to ensure the Agentforce Service Agent can run this new flow as part of the new Agent Action?
- A . Recreate the flow using the Agentforce agent user.
- B . Assign the Manage Users permission to the Agentforce Agent user.
- C . Assign the Run Flows permission to the Agentforce Agent user.
Correct Answer: C
C
Explanation:
Comprehensive and Detailed In-Depth
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.
Reference: Salesforce Agentforce Documentation: Agent Builder > Custom Actions C Requires "Run Flows" for flow-based actions.
Trailhead: Set Up Agentforce Service Agents C Lists "Run Flows" in agent user permissions.
Salesforce Help: Agentforce Security > Permissions C Confirms flow execution needs.
C
Explanation:
Comprehensive and Detailed In-Depth
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.
Reference: Salesforce Agentforce Documentation: Agent Builder > Custom Actions C Requires "Run Flows" for flow-based actions.
Trailhead: Set Up Agentforce Service Agents C Lists "Run Flows" in agent user permissions.
Salesforce Help: Agentforce Security > Permissions C Confirms flow execution needs.