Explanation:

The issue is that the agent is misrouting billing inquiries to the wrong subagent because the planner is not reliably distinguishing between overlapping subagent responsibilities.

The most appropriate solution is to:

* Review the instructions for each subagent to identify semantic competition (overlapping descriptions, ambiguous responsibilities, or similar trigger phrases).
* Refine the instructions so each subagent has a clear, distinct purpose.
* Add deterministic filters (where appropriate) to explicitly route requests that meet certain criteria.

This approach:

* Improves routing accuracy.
* Is relatively quick to implement.
* Preserves the planner's ability to handle complex, non-linear conversations, which is one of Agentforce's strengths.

Why the Other Options Are Incorrect
A. ❌ Update the agent's global System Instructions to include a list of forbidden keywords for each subagent.
Global system instructions are not intended to manage routing through keyword blacklists. Keyword-based restrictions are brittle and do not address the underlying issue of overlapping subagent definitions. Agentforce routing relies on semantic understanding rather than simple keyword exclusion.

C. ❌ Create a Router sub-flow that uses a Decision element to manually assign every incoming request to a specific subagent.
Although this would provide deterministic routing, it replaces the planner's intelligent routing with rigid, rule-based logic. The requirement specifically calls for preserving the agent's ability to handle complex, non-linear conversations. This approach is more complex to maintain and reduces the flexibility of Agentforce.

Reference
Salesforce Agentforce documentation on designing effective subagents (formerly topics), including clear instructions and routing guidance.
Salesforce Agentforce best practices for reducing semantic overlap and using deterministic filters where appropriate.
Salesforce Certified Agentforce Specialist (AI-201) Exam Guide – agent planning, subagent design, and routing.

Exam Tip
For routing-related questions, distinguish between:

Ambiguous or overlapping subagent responsibilities → Refine subagent instructions and use deterministic filters.
Mandatory business rules or guaranteed execution → Use deterministic logic (such as filters or explicit action execution).
Replacing Agentforce planning with hard-coded routing → Usually not preferred unless the requirement explicitly calls for fully deterministic routing.

A common AI-201 pattern is that Salesforce favors improving the planner with clearer instructions and targeted deterministic controls, rather than replacing it with entirely rule-based routing.

Explanation:

Agent Script allows an Agentforce Specialist to define procedural, step-by-step instructions within a topic that the agent must follow in a specific, enforced order — while still allowing the LLM to handle the natural language conversation with the customer around those steps. This is exactly suited to UC's requirement: the agent needs to strictly validate order eligibility before proceeding with the return, but the overall interaction should still feel conversational and natural to the customer.

Agent Script achieves this balance by combining:

Deterministic control — ensuring critical business logic (like validation before action) is never skipped or reordered by the LLM's own reasoning.

Conversational flexibility — the LLM still manages the natural dialogue, rephrasing, and handling variations in how the customer expresses their request, rather than following a rigid, scripted UI flow.

This makes it the ideal tool when you need guardrails on sequence and logic without sacrificing the conversational experience that agents are meant to provide.

Why the Other Options Are Incorrect
A. ❌ Use Salesforce Flow to guide the LLM
While Flows can be invoked as actions within an agent (e.g., to perform validation lookup or process the return), a Flow itself does not guide the LLM's conversational reasoning or enforce step sequencing at the agent instruction level. That responsibility sits with how the topic or instructions (Agent Script) are structured, not the Flow itself. A Flow is useful as an action within the process, but not as the mechanism for enforcing conversational step order.

B. ❌ Use a custom Apex @InvocableMethod
This could technically perform the validation and return logic as an action, but a single invocable method handling the entire return process (including validation) does not preserve a natural conversational flow. It turns the interaction into a monolithic, black-box action rather than a guided, step-enforced conversation. It also does not address how the sequence is enforced conversationally, which is the core requirement.

Reference
Salesforce Agentforce documentation — "Agent Script: Combining Procedural Instructions with Conversational AI" (enforcing strict step sequencing, such as validation-before-action, while maintaining natural language interaction).

Explanation:

The requirement specifies a hospitality brand agent grounded in a data library containing 200 FAQ articles. To avoid a three-week manual process of authoring test cases, the specialist needs to leverage the Agentforce Testing Center's built-in automation to generate a comprehensive initial test suite from that existing content.

The correct approach is explained below:

In the Agentforce Testing Center, administrators can choose Generate test cases based on the knowledge available to the agent (also listed as Generate Tests from Knowledge Sources in Salesforce documentation).

When this feature is selected, the underlying generative AI analyzes the connected Data Libraries and Salesforce Knowledge base to automatically formulate realistic user questions (utterances) and Q&A-style test scenarios directly from your indexed documentation.

This process immediately covers the vast majority of your content's surface area, reducing the time required to build a testing baseline from weeks to minutes.

Why the Other Options Are Incorrect
A. ❌ Upload test cases.
Uploading test cases relies on a downloadable CSV template where the project team must have already manually populated the utterances, expected topics, and expected actions. This directly contradicts the requirement to generate a test suite without manual authoring.

C. ❌ Generate test cases based on subagents and actions.
While this is a valid option in the Agentforce Testing Center (Beta), it creates test scenarios aimed at verifying topic routing, intent classification, and flow tool execution based on subagent metadata. It is not optimized to crawl through and evaluate the deep knowledge text inside 200 specific FAQ data library files like option B does.

Reference
Salesforce Help: Generate Tests from Knowledge Sources (Agentforce Testing Center). To quickly evaluate an agent's grounded accuracy, select the option to generate test cases based on the knowledge available to the agent to automatically parse connected libraries.

Exam Tip
When a question emphasizes testing Knowledge Bases, FAQs, or Data Libraries quickly:

✅ Grounded Document / FAQ Verification → Generate test cases based on the knowledge available to the agent
✅ Topic / Flow Tool Execution Verification → Generate test cases based on subagents and actions

Explanation:

Option B (Implement a larger chunk size) is the recommended strategy here.

For long, complex, hierarchically structured documents like legal agreements (with nested clauses inside sections, subsections, etc.), the standard or smaller chunking strategy often breaks context across boundaries. A larger chunk size helps preserve broader structural context, headings, and surrounding sections so the retrieval process (RAG via Agentforce Data Library) can deliver more complete and relevant clauses along with their necessary context.

Why the Other Options Are Incorrect
A. ❌ Smaller chunk size
This would worsen the problem by creating even more fragmented pieces, causing the nested relationships and surrounding context that are critical for legal documents to be lost.

C. ❌ Keyword-based chunking
Keyword-based chunking can help with targeted retrieval in some scenarios, but it does not inherently preserve document structure such as hierarchy, sections, and nested content. It is better viewed as a complementary technique rather than the primary solution for structural context loss.

Additional Context & Tips
In Agentforce Data Library and Salesforce Knowledge implementations, the chunking strategy plays a major role in Retrieval-Augmented Generation (RAG) quality. Larger chunks are generally better for documents with rich internal structure, while smaller chunks are more suitable for uniform, fact-dense content.

For even better results, combine larger chunk sizes with well-defined metadata (such as section titles and clause IDs), hierarchical indexing where available, and prompt instructions that guide the agent on how to synthesize information from retrieved chunks.

Use Agentforce evaluation tools (such as factuality, completeness, and coherence metrics) to validate that the new chunking strategy improves retrieval quality.

This topic aligns with the Data Cloud, Data Library, Prompt Engineering, and Agent Optimization objectives covered in the Salesforce Certified Agentforce Specialist (AI-201) exam.

Explanation:

Summary: 📝
This question focuses on the appropriate Salesforce best practice for granting Agentforce Service Agents access to existing custom fields and custom objects related to the Case object. The goal is to allow agents to leverage this proprietary data when formulating responses to customer inquiries using the Agentforce features. The best approach involves utilizing the dedicated permission set group designed for these agents, ensuring the security model is correctly configured for data retrieval.

Correct Option: ✅

A. Update the Object and Field access in the AgentforceServiceAgentUserPsg permission set group that is already assigned to the Agentforce Service Agent user.
The AgentforceServiceAgentUserPsg (Permission Set Group) is the standard and recommended container for managing permissions for users who are licensed and intended to be Agentforce Service Agents.
🔹 Best Practice: Modifying this existing permission set group is the most efficient and scalable way to grant the necessary Read access to the new custom fields and objects. It centralizes permission management for this specific user type.
The Agentforce license and core permissions are managed by this group, so adding object and field permissions here ensures the agent's complete access requirements are met in a single place.

Incorrect Option: ❌

B. Create a new permission set with the Einstein Agent License and enable Read access to the custom fields and custom objects, and assign it to the Agentforce Service Agent user.
While creating a new permission set can grant access, the Einstein Agent License is typically assigned via a dedicated Permission Set or the AgentforceServiceAgentUserPsg itself, not an ad-hoc new permission set. Assigning the license is generally separate from granting object/field access for specific custom data. The best practice is to aggregate these permissions into the dedicated Psg. Creating separate permission sets for every data access need quickly complicates security maintenance.

C. Update the Object and Field access in the Einstein Agent User Profile so that the Agentforce Service Agents will always get the necessary access.
Salesforce best practices heavily favor using Permission Sets and Permission Set Groups over Profiles for granular and ongoing access management (Field-Level Security and Object Permissions). Profiles are primarily used for broad settings like page layouts and login hours. Using the AgentforceServiceAgentUserPsg (Option A) is the modern, flexible, and recommended approach, moving away from profile-based access control.

Reference: 🌐
Salesforce Help: Permission Set Groups
Salesforce Help: Service Cloud Agentforce (General context on agent setup and licensing)