AI-201 · Question #267
Universal Containers needs to bring individual customer warranties from an external system into Data Cloud. They want Agentforce to return warranty-related responses only for accounts whose warranty s
The correct answer is C. Use Hybrid Search and apply pre-filtering in a new custom retriever for matching accounts and. To reliably restrict responses to only accounts with an active warranty status, the correct approach is Hybrid Search with pre-filtering applied in a custom retriever. Pre-filtering acts at the index/retrieval layer - it filters candidate records based on a metadata field (warran
Question
Universal Containers needs to bring individual customer warranties from an external system into Data Cloud. They want Agentforce to return warranty-related responses only for accounts whose warranty status is active. Which search approach should the Agentforce Specialist configure to ensure warranty-related information is retrieved correctly?
Options
- ADepend on Agentforce instructions to enforce warranty constraints and include only
- BStore the account's warranty status in an Agentforce custom variable to dynamically filter
- CUse Hybrid Search and apply pre-filtering in a new custom retriever for matching accounts and
How the community answered
(20 responses)- A10% (2)
- B5% (1)
- C85% (17)
Explanation
To reliably restrict responses to only accounts with an active warranty status, the correct approach is Hybrid Search with pre-filtering applied in a custom retriever. Pre-filtering acts at the index/retrieval layer - it filters candidate records based on a metadata field (warranty status = active) before any vector or keyword scoring occurs. This is more reliable than relying on agent instructions (Option A) to enforce the constraint, because LLM instructions can be inconsistent. Storing the status in a custom variable (Option B) alone does not filter the underlying search results.
Topics
Community Discussion
No community discussion yet for this question.