Question 20
At Redfern Aviation, a supplier operations group is improving spare-part quotations during an agent routing evaluation (SF-D11-01). The administrator observes that product support queries contain error IDs alongside natural-language descriptions. Any fix must ensure that supplier prices are never shown outside entitled teams. Which action best addresses the issue while preserving the stated requirement?
Explanation
Correct Answer
The documented failure is that product support queries contain error IDs alongside natural-language descriptions. Use a hybrid keyword-and-vector search configuration for the indexed knowledge for Redfern Aviation's spare-part quotations workflow (SF-D11-01) while respecting that supplier prices are never shown outside entitled teams. Its outcome is not established merely by changing instructions: In a controlled Quote acceptance test, tests retrieve the exact error-code guidance and semantically relevant explanations; the record is retained under Redfern Aviation's rollout (SF-D11-01). The underlying reason is that Hybrid retrieval can combine exact lexical signals with semantic similarity. In this spare-part quotations scenario, this separates supported agent behavior from assumptions about the AI model.
Incorrect Answers
The action “Use a coherent chunking strategy to index smaller meaningful guide sections; implement it with a named deployment owner” addresses a separate source case: A twenty-page support guide is indexed as one oversized passage and retrieval is imprecise. The correction must ensure that employee procedures cannot be exposed to anonymous users. Its underlying reason is: Chunking trades passage granularity against preservation of useful context. This question instead describes product support queries contain error IDs alongside natural-language descriptions. The correction must ensure that supplier prices are never shown outside entitled teams. The original answer “Use a hybrid keyword-and-vector search configuration for the indexed knowledge; implement it within the documented Salesforce configuration” targets that failure because hybrid retrieval can combine exact lexical signals with semantic similarity.
The action “Create the search index over the appropriate DMO content and fields; implement it with traceable change approval” addresses a separate source case: A Data 360 source is ingested but no searchable index exists for its content. The correction must ensure that student records never cross program authorization boundaries. Its underlying reason is: Ingestion alone does not provide retriever-ready search access. This question instead describes product support queries contain error IDs alongside natural-language descriptions. The correction must ensure that supplier prices are never shown outside entitled teams. The original answer “Use a hybrid keyword-and-vector search configuration for the indexed knowledge; implement it within the documented Salesforce configuration” targets that failure because hybrid retrieval can combine exact lexical signals with semantic similarity.
The action “Consolidate or precisely filter the approved current source before routing retrieval; implement it before the next environment promotion” addresses a separate source case: Two overlapping libraries contain conflicting versions of the same return policy. The correction must ensure that copyrighted manuscripts remain within the approved workspace. Its underlying reason is: Duplicate knowledge sources can make retrieval ambiguous even with correct prompts. This question instead describes product support queries contain error IDs alongside natural-language descriptions. The correction must ensure that supplier prices are never shown outside entitled teams. The original answer “Use a hybrid keyword-and-vector search configuration for the indexed knowledge; implement it within the documented Salesforce configuration” targets that failure because hybrid retrieval can combine exact lexical signals with semantic similarity.