Question 650 A production service intermittently returns empty context, yet model completion traces show a normal success status. Which verification is strongest for this particular failure mode? Examine inference tables for synthetic sensitive identifiers and verify retrieval debugging remains possible using safe IDs. Correlate empty-answer cases with retrieval latency and tool error events in the same trace ID. Reproduce a reported answer and find the exact document IDs and index revision in the recorded trace. Introduce a mocked failing tool call and verify its span/error is detected independently of the final-answer score. ExplanationCorrect Answer B:A generator can complete successfully after an upstream retrieval failure, so final model status alone hides the incident. Other Answers A:Correlate empty-answer cases with retrieval latency and tool error events in the same trace ID. C:Correlate empty-answer cases with retrieval latency and tool error events in the same trace ID. D:Correlate empty-answer cases with retrieval latency and tool error events in the same trace ID.
Question 651 A production service intermittently returns empty context, yet model completion traces show a normal success status. What change to engineering governance would reduce this risk over time? Apply field-level retention, access policies and redaction validation to inference telemetry. Require source-version metadata and sanitized retrieval-span logging for grounded applications. Keep stage-specific structured checks alongside model-based evaluators. Monitor required context availability and define fallback behavior for upstream search errors. ExplanationCorrect Answer D:A generator can complete successfully after an upstream retrieval failure, so final model status alone hides the incident. Other Answers A:This control addresses a different exposure: An engineer stores full customer account data in inference tables to debug a rare RAG issue, creating a second uncontrolled sensitive-data repository. It would not prevent this failure, because a generator can complete successfully after an upstream retrieval failure, so final model status alone hides the incident. B:That a generator can complete successfully after an upstream retrieval failure, so final model status alone hides the incident. C:A generator can complete successfully after an upstream retrieval failure, so final model status alone hides the incident.
Question 652 An engineer stores full customer account data in inference tables to debug a rare RAG issue, creating a second uncontrolled sensitive-data repository. Which engineering action most directly addresses this specific requirement? Configure the supported scorer sampling/monitoring schedule and verify trace ingestion and service prerequisites. Inspect per-stage inference records for search timeouts and missing-context flags before changing prompt text. Enable approved inference/trace logging with query, index revision, retrieved document IDs and citations while redacting sensitive values. Log minimal redacted diagnostics and stable trace/source IDs rather than raw protected customer fields. ExplanationCorrect Answer D:The action targets the stated cause: Observability pipelines retain data independently from serving and must meet the same access and privacy requirements. Check the repair by: examine inference tables for synthetic sensitive identifiers and verify retrieval debugging remains possible using safe IDs. Other Answers A:Observability pipelines retain data independently from serving and must meet the same access and privacy requirements. B:Observability pipelines retain data independently from serving and must meet the same access and privacy requirements. C:Observability pipelines retain data independently from serving and must meet the same access and privacy requirements.
Question 653 A team sees its monthly model bill grow, but metrics expose only total dollars without token counts or request attribution. What is the most targeted corrective step for this observed failure? Reduce context to approved relevant history and measure token savings without losing resolution quality. Apply rate limits and budget safeguards at the approved gateway/service boundary, with graceful error handling for excess traffic. Record input/output tokens and per-application usage, then isolate cost drivers by model, tenant and workflow. Use approved Unity Gateway usage visibility and caller-scoped rate or budget policies where supported, with clear version/availability caveats. ExplanationCorrect Answer C:The action targets the stated cause: Cost visibility requires decomposing usage by request path and token consumption, not relying on a single aggregate invoice. Check the repair by: reconcile sampled request token usage and model pricing to recorded daily spend per application. Other Answers A:Cost visibility requires decomposing usage by request path and token consumption, not relying on a single aggregate invoice. B:Cost visibility requires decomposing usage by request path and token consumption, not relying on a single aggregate invoice. D:Cost visibility requires decomposing usage by request path and token consumption, not relying on a single aggregate invoice.
Question 654 A team sees its monthly model bill grow, but metrics expose only total dollars without token counts or request attribution. What is the decisive mechanism behind the observed result? Central gateway controls can attribute usage to callers and enforce request-level policies beyond the raw model API. Model serving cost is coupled to request rate and generated tokens; uncontrolled callers can exhaust capacity or spend. Cost visibility requires decomposing usage by request path and token consumption, not relying on a single aggregate invoice. Input token costs and latency grow with unnecessary history; context reduction must still preserve required state. ExplanationCorrect Answer C:Record input/output tokens and per-application usage, then isolate cost drivers by model, tenant and workflow. Other Answers A:Cost visibility requires decomposing usage by request path and token consumption, not relying on a single aggregate invoice. B:Cost visibility requires decomposing usage by request path and token consumption, not relying on a single aggregate invoice. D:That mechanism describes another problem: A support app repeatedly sends full conversation histories to a model when only the latest summarized context is required. It does not explain this case, where cost visibility requires decomposing usage by request path and token consumption, not relying on a single aggregate invoice.
Question 655 A team sees its monthly model bill grow, but metrics expose only total dollars without token counts or request attribution. Which verification is strongest for this particular failure mode? Reconcile sampled request token usage and model pricing to recorded daily spend per application. Generate traffic from two identities and verify the selected policy throttles only the configured caller. Compare token usage and answer correctness on long conversation tests before and after pruning. Load-test above the configured quota and verify excess requests are throttled with clear telemetry. ExplanationCorrect Answer A:Cost visibility requires decomposing usage by request path and token consumption, not relying on a single aggregate invoice. Other Answers B:Reconcile sampled request token usage and model pricing to recorded daily spend per application. C:Reconcile sampled request token usage and model pricing to recorded daily spend per application. D:Reconcile sampled request token usage and model pricing to recorded daily spend per application.
Question 656 A team sees its monthly model bill grow, but metrics expose only total dollars without token counts or request attribution. What change to engineering governance would reduce this risk over time? Enforce history budgets, retention limits and quality regression checks. Maintain rate-limit policies and incident escalation thresholds per consumer identity. Define gateway usage dashboards and per-consumer budget thresholds under change control. Configure usage tagging and cost anomaly alerts for serving endpoints and gateway policies. ExplanationCorrect Answer D:Cost visibility requires decomposing usage by request path and token consumption, not relying on a single aggregate invoice. Other Answers A:Cost visibility requires decomposing usage by request path and token consumption, not relying on a single aggregate invoice. B:This control addresses a different exposure: A public-facing assistant receives an abrupt bot-driven traffic surge that consumes the team's inference budget within minutes. It would not prevent this failure, because cost visibility requires decomposing usage by request path and token consumption, not relying on a single aggregate invoice. C:That cost visibility requires decomposing usage by request path and token consumption, not relying on a single aggregate invoice.
Question 657 A public-facing assistant receives an abrupt bot-driven traffic surge that consumes the team's inference budget within minutes. Which engineering action most directly addresses this specific requirement? Reduce context to approved relevant history and measure token savings without losing resolution quality. Inspect gateway tool-usage telemetry for the MCP service and attribute calls, errors and latency to the tool and request identity. Apply rate limits and budget safeguards at the approved gateway/service boundary, with graceful error handling for excess traffic. Record input/output tokens and per-application usage, then isolate cost drivers by model, tenant and workflow. ExplanationCorrect Answer C:The action targets the stated cause: Model serving cost is coupled to request rate and generated tokens; uncontrolled callers can exhaust capacity or spend. Check the repair by: load-test above the configured quota and verify excess requests are throttled with clear telemetry. Other Answers A:Model serving cost is coupled to request rate and generated tokens; uncontrolled callers can exhaust capacity or spend. B:Model serving cost is coupled to request rate and generated tokens; uncontrolled callers can exhaust capacity or spend. D:Model serving cost is coupled to request rate and generated tokens; uncontrolled callers can exhaust capacity or spend.
Question 658 A public-facing assistant receives an abrupt bot-driven traffic surge that consumes the team's inference budget within minutes. What architectural constraint is most directly responsible? Model serving cost is coupled to request rate and generated tokens; uncontrolled callers can exhaust capacity or spend. Input token costs and latency grow with unnecessary history; context reduction must still preserve required state. Cost visibility requires decomposing usage by request path and token consumption, not relying on a single aggregate invoice. Agent spend and reliability include tool invocations; model-only tokens omit MCP service activity. ExplanationCorrect Answer A:Apply rate limits and budget safeguards at the approved gateway/service boundary, with graceful error handling for excess traffic. Other Answers B:Model serving cost is coupled to request rate and generated tokens; uncontrolled callers can exhaust capacity or spend. C:That mechanism describes another problem: A team sees its monthly model bill grow, but metrics expose only total dollars without token counts or request attribution. It does not explain this case, where model serving cost is coupled to request rate and generated tokens; uncontrolled callers can exhaust capacity or spend. D:Model serving cost is coupled to request rate and generated tokens; uncontrolled callers can exhaust capacity or spend.
Question 659 A public-facing assistant receives an abrupt bot-driven traffic surge that consumes the team's inference budget within minutes. What validation evidence would most specifically confirm the resolution? Execute a controlled MCP query and verify a corresponding attributed tool entry appears in permitted usage logs. Reconcile sampled request token usage and model pricing to recorded daily spend per application. Load-test above the configured quota and verify excess requests are throttled with clear telemetry. Compare token usage and answer correctness on long conversation tests before and after pruning. ExplanationCorrect Answer C:Model serving cost is coupled to request rate and generated tokens; uncontrolled callers can exhaust capacity or spend. Other Answers A:Load-test above the configured quota and verify excess requests are throttled with clear telemetry. B:Load-test above the configured quota and verify excess requests are throttled with clear telemetry. D:Load-test above the configured quota and verify excess requests are throttled with clear telemetry.
Question 660 A public-facing assistant receives an abrupt bot-driven traffic surge that consumes the team's inference budget within minutes. What prevention measure is most targeted to this underlying cause? Enforce history budgets, retention limits and quality regression checks. Maintain rate-limit policies and incident escalation thresholds per consumer identity. Monitor both tool and model events with trace correlation and separate access policies. Configure usage tagging and cost anomaly alerts for serving endpoints and gateway policies. ExplanationCorrect Answer B:Model serving cost is coupled to request rate and generated tokens; uncontrolled callers can exhaust capacity or spend. Other Answers A:This control addresses a different exposure: A support app repeatedly sends full conversation histories to a model when only the latest summarized context is required. It would not prevent this failure, because model serving cost is coupled to request rate and generated tokens; uncontrolled callers can exhaust capacity or spend. C:That model serving cost is coupled to request rate and generated tokens; uncontrolled callers can exhaust capacity or spend. D:Model serving cost is coupled to request rate and generated tokens; uncontrolled callers can exhaust capacity or spend.
