AI-201 · Question #254
Universal Containers wants to use an Al agent to answer questions about warranties, Warranty information has already been uploaded as unstructured data in Data Cloud. When answering user questions, th
The correct answer is B. Build a custom retriever in Einstein Studio with product line filters and regency ranking.. The requirements here are specific and compound: results must be (1) filterable by a metadata field (product line) and (2) ranked by recency (most recently updated first). The default retriever in Agentforce/Einstein Search uses pure semantic similarity ranking and does not nativ
Question
Universal Containers wants to use an Al agent to answer questions about warranties, Warranty information has already been uploaded as unstructured data in Data Cloud. When answering user questions, the results must be filterable by product line and ranked by recent updates. Which approach should the Agentforce Specialist implement?
Options
- AUse the default retriever which automatically accounts for regency ranking.
- BBuild a custom retriever in Einstein Studio with product line filters and regency ranking.
- CApply semantic embeddings with default metadata filters to achieve the desired result
How the community answered
(67 responses)- A10% (7)
- B75% (50)
- C15% (10)
Explanation
The requirements here are specific and compound: results must be (1) filterable by a metadata field (product line) and (2) ranked by recency (most recently updated first). The default retriever in Agentforce/Einstein Search uses pure semantic similarity ranking and does not natively support custom metadata filters or recency-based re-ranking out of the box. To meet both requirements deterministically, the Agentforce Specialist must build a custom retriever in Einstein Studio, where they can configure metadata filter conditions (e.g., filter by product_line field) and apply a recency ranking signal to the results. Option A (default retriever) cannot be relied upon to apply regency ranking or product-line filtering without customization. Option C (semantic embeddings with default metadata filters) still relies on the default retriever's limited filter capabilities and does not address custom recency ranking, making it insufficient for these business requirements.
Topics
Community Discussion
No community discussion yet for this question.