Question 760
At Delta Transit, a passenger support center is improving service disruption updates during a least-privilege verification (SF-D11-02). The administrator observes that product support queries contain error IDs alongside natural-language descriptions. Any fix must ensure that safety-critical changes need an attributable human approval. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?
Explanation
Correct Answer
The governing distinction is: Hybrid retrieval can combine exact lexical signals with semantic similarity. In this service disruption updates scenario, this separates supported agent behavior from assumptions about the AI model. Because product support queries contain error IDs alongside natural-language descriptions, the intended response is to use a hybrid keyword-and-vector search configuration for the indexed knowledge. An observable check is that tests retrieve the exact error-code guidance and semantically relevant explanations.
Incorrect Answers
The idea “Structured record grounding differs from unstructured chunk search; interpret this independent of the surface wording of the conversation” explains another source-defined situation: An LLM response requires current account status stored in a structured DMO rather than long documents. The correction must ensure that shipment changes remain attributable and reversible. That situation depends on: Structured record grounding differs from unstructured chunk search. The present question instead concerns product support queries contain error IDs alongside natural-language descriptions. The correction must ensure that safety-critical changes need an attributable human approval. Its directly relevant mechanism is: Hybrid retrieval can combine exact lexical signals with semantic similarity.
The idea “Ingestion alone does not provide retriever-ready search access; interpret this rather than assuming a generative instruction is an access rule” explains another source-defined situation: 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. That situation depends on: Ingestion alone does not provide retriever-ready search access. The present question instead concerns product support queries contain error IDs alongside natural-language descriptions. The correction must ensure that safety-critical changes need an attributable human approval. Its directly relevant mechanism is: Hybrid retrieval can combine exact lexical signals with semantic similarity.
The idea “Data-library setup is a pipeline with dependent indexing and retrieval stages; interpret this as distinct from unrelated UI configuration” explains another source-defined situation: A knowledge-backed agent has no useful results after initial library setup. The correction must ensure that guest profile fields are used only with permitted access. That situation depends on: Data-library setup is a pipeline with dependent indexing and retrieval stages. The present question instead concerns product support queries contain error IDs alongside natural-language descriptions. The correction must ensure that safety-critical changes need an attributable human approval. Its directly relevant mechanism is: Hybrid retrieval can combine exact lexical signals with semantic similarity.