* Context of the QuestionUniversal Containers (UC) uses Agentforce, a specialized AI-driven assistant for Salesforce. A user reports that an Agent is unable to delete recent activities.
* Why Agentforce Cannot Delete Records
* Agentforce's Standard Actions: Agentforce typically has predefined or "standard" actions like Create, Update, or Summarize records. However, a standard Delete Record action is not part of the default set of Agentforce actions.
* Implication: If Agentforce has no built-in delete functionality, it cannot remove activities-even if the user has permission to delete them in the Salesforce UI.
* Why Other Options Are Incorrect
* Option A - Permission to Delete the User's Records: Standard Salesforce user permissions do not automatically extend to Agentforce's capabilities. Even if the user can delete records, that doesn't grant Agentforce a new action.
* Option B - Agentforce Delete Record Action Permission: There is no separate "Delete Record Action permission" for Agentforce to be toggled. The relevant issue is that the standard Delete Record action does not exist within Agentforce out of the box.
* ConclusionThe core reason for the issue is that Agentforce does not support a standard Delete Record action (Choice C).
Salesforce Agentforce Specialist References & Documents
* Salesforce Official Documentation - Agentforce(Note: Agentforce may be a pilot or specialized feature; check pilot release notes or official docs for standard actions.)
* Salesforce Agentforce Specialist Study GuideCovers the limitations of certain AI-enabled features regarding record operations.

In this scenario, the Agent capability that best helps the agent is its ability to execute tasks based on available actions and answer questions using data from Knowledge articles. Agent can assist the service agent by providing relevant Knowledge articles on canceling and rebooking flights, ensuring that the agent has access to the correct steps and procedures directly within the workflow.
This feature leverages the agent's existing context (the travel itinerary) and provides actionable insights or next steps from the relevant Knowledge articles to help the agent quickly resolve the customer's needs.
The other options are incorrect:
* B refers to invoking a flow to create a Knowledge article, which is unrelated to the task of retrieving existing Knowledge articles.
* C focuses on generating Knowledge articles, which is not the immediate need for this situation where the agent requires guidance on existing procedures.
References:
* Salesforce Documentation on Agent
* Trailhead Module on Einstein for Service

To address the ineffectiveness of a prompt template reported by a customer, the Salesforce Agentforce Specialist should use the Prompt Builder Scorecard (Option B). This tool is explicitly designed to evaluate and monitor prompt templates against key criteria such as relevance, accuracy, safety, and grounding. By leveraging the scorecard, the specialist can systematically identify weaknesses in the template and make data- driven refinements. While monitoring and refining based on user feedback (Option A) is a general best practice, the Prompt Builder Scorecard is Salesforce's recommended tool for structured evaluation, aligning with documented processes for maintaining prompt effectiveness. Changing the grounding object (Option C) without proper evaluation is reactive and does not address the root cause.
References:
* Salesforce Einstein Agentforce Specialist Certification Guide: Emphasizes using the Prompt Builder Scorecard to evaluate prompts and iterate based on results.
* Trailhead Module: "Einstein for Developers" highlights the scorecard as a critical tool for assessing prompt performance.
* Salesforce Help Documentation: Details the Scorecard's role in evaluating prompts against predefined criteria.

Universal Containers is considering the use of the Einstein Trust Layer along with Einstein Generative AI Audit Data. The Einstein Trust Layer provides a secure and compliant way to use AI by offering features like data masking and toxicity assessment.
The audit data available through the Einstein Trust Layer includes information about masked data-which ensures sensitive information is not exposed-and the toxicity score, which evaluates the generated content for inappropriate or harmful language.
References:
* Salesforce Agentforce Specialist Documentation - Einstein Trust Layer: Details the auditing capabilities, including logging of masked data and evaluation of generated responses for toxicity to maintain compliance and trust.

When a flow is invoked via a custom Agent action, its data access depends on the flow's runtime configuration, not system mode by default. Salesforce flows can be configured to respect the running user's permissions and sharing settings:
* If the flow is set to "Run as the User Who Launched the Flow" (enabled in Flow Settings), it adheres to the user's permissions, field-level security (FLS), and sharing rules.
* Option C is incorrect because flows do not always run in system mode unless explicitly configured to do so.
* Option A is misleading because "with sharing" is an Apex concept, not a flow setting. Flows use runtime settings like FLS and sharing enforcement.
References:
* Salesforce Help: Flow Runtime and Security Context
* Flow Settings: "Run with User Permission and Field-Level Security" ensures data access aligns with the user's permissions.