Question 240
A catalog assistant receives many repeated public product questions while underlying SKUs change only at managed publish times. What is the most defensible next step?
Explanation
Correct Answer
Use a cache keyed by query, permissions where relevant, and content version, with invalidation tied to source updates; freshness and authorization checks are essential alongside speed gains; evaluate the design with repeated-query latency with zero stale or cross-scope cache responses after updates.
Incorrect Answers
Keep the critical verified signal independent and return a clearly limited result when optional enrichment exceeds its budget; silently presenting an unverified enriched conclusion would violate accuracy requirements despite meeting a timer; this alternative would measure deadline compliance and correct indication of omitted enrichment; it does not establish repeated-query latency with zero stale or cross-scope cache responses after updates for the described use case.
Acknowledge an asynchronous job, persist its state, and let the client poll or receive authorized completion notifications; a longer synchronous timeout would still tie up request resources and expose users to unreliable waits; this alternative would measure job completion reliability and duplicate-submission rate during slow-system simulations; it does not establish repeated-query latency with zero stale or cross-scope cache responses after updates for the described use case.
Use an evaluated routing policy that sends straightforward lookups to a light path and escalates uncertain cases to more capable reasoning; uniform deep reasoning does not add value to deterministic records and may increase response time; this alternative would measure accuracy by difficulty segment and unit cost under p95 constraints; it does not establish repeated-query latency with zero stale or cross-scope cache responses after updates for the described use case.
Retrieve a bounded candidate set and rerank against the actual question to concentrate useful evidence without feeding all candidates to the model; taking every retrieved hit into context may raise token cost and distraction without raising answer quality; this alternative would measure grounded-answer accuracy and retrieval-stage p95 latency at several rerank depths; it does not establish repeated-query latency with zero stale or cross-scope cache responses after updates for the described use case.