Question 360 An agent produces a wrong invoice answer, and its current logs show only the final chat message, not the SQL tool call used. Which design change directly satisfies the stated constraints? Reconcile the March exam's Agent Framework terms with the October 2026 Agent Bricks CLI deployment guidance before migrating code. Log tool result identifiers and prompt context spans in the trace, then use recorded traces to review the failing branches. Instrument the framework stages with MLflow traces carrying prompts, retrieval events, tool results and output identifiers under appropriate redaction. Enable MLflow tracing of the authorized tool invocation, input parameters and result metadata with sensitive values redacted. ExplanationCorrect Answer D:The action targets the stated cause: Agent behavior spans tool calls and intermediate messages; missing spans block root-cause attribution. Check the repair by: replay the invoice and inspect an end-to-end trace linking the request, SQL query span and returned amount. Other Answers A:Agent behavior spans tool calls and intermediate messages; missing spans block root-cause attribution. B:Agent behavior spans tool calls and intermediate messages; missing spans block root-cause attribution. C:Agent behavior spans tool calls and intermediate messages; missing spans block root-cause attribution.
Question 361 An agent produces a wrong invoice answer, and its current logs show only the final chat message, not the SQL tool call used. Which causal explanation best accounts for the failure? Trace context provides causality between retrieval, tool execution and final generation; isolated logs cannot reconstruct the path. Agent behavior spans tool calls and intermediate messages; missing spans block root-cause attribution. Historical certification vocabulary and current agent serving products can describe different deployment lifecycles. Without step-level observability, a final answer alone cannot attribute errors to retrieval, chain formatting or model generation. ExplanationCorrect Answer B:Enable MLflow tracing of the authorized tool invocation, input parameters and result metadata with sensitive values redacted. Other Answers A:Agent behavior spans tool calls and intermediate messages; missing spans block root-cause attribution. C:That mechanism describes another problem: A custom Python agent uses an old deployment scaffold that no longer aligns with current Agent Runtime guidance. It does not explain this case, where agent behavior spans tool calls and intermediate messages; missing spans block root-cause attribution. D:Agent behavior spans tool calls and intermediate messages; missing spans block root-cause attribution.
Question 362 An agent produces a wrong invoice answer, and its current logs show only the final chat message, not the SQL tool call used. Which concrete acceptance test best demonstrates the proposed change works? Trigger a known unsupported-answer case and confirm the trace identifies the failing stage and available source evidence. Replay the invoice and inspect an end-to-end trace linking the request, SQL query span and returned amount. Verify a staging deployment with supported agent entry points, health checks and trace capture against current docs. Select a failed response in MLflow and navigate to the exact source/tool span responsible for its unsupported content. ExplanationCorrect Answer B:Agent behavior spans tool calls and intermediate messages; missing spans block root-cause attribution. Other Answers A:Replay the invoice and inspect an end-to-end trace linking the request, SQL query span and returned amount. C:Replay the invoice and inspect an end-to-end trace linking the request, SQL query span and returned amount. D:Replay the invoice and inspect an end-to-end trace linking the request, SQL query span and returned amount.
Question 363 An agent produces a wrong invoice answer, and its current logs show only the final chat message, not the SQL tool call used. Which operational practice should be made a durable requirement? Require trace coverage and sanitized observability as release criteria for agent implementations. Require reproducible trace IDs and stable experiment tagging for each agent revision. Standardize trace instrumentation and safe field redaction across agent tools. Maintain a platform-version crosswalk and migration test suite rather than hard-coding legacy sample APIs. ExplanationCorrect Answer C:Agent behavior spans tool calls and intermediate messages; missing spans block root-cause attribution. Other Answers A:This control addresses a different exposure: A RAG application emits answers without a way to identify which tool or prompt stage produced an unsupported claim. It would not prevent this failure, because agent behavior spans tool calls and intermediate messages; missing spans block root-cause attribution. B:That agent behavior spans tool calls and intermediate messages; missing spans block root-cause attribution. D:Agent behavior spans tool calls and intermediate messages; missing spans block root-cause attribution.
Question 364 A custom Python agent uses an old deployment scaffold that no longer aligns with current Agent Runtime guidance. What should the implementation team change first to resolve the described defect? Log tool result identifiers and prompt context spans in the trace, then use recorded traces to review the failing branches. Reconcile the March exam's Agent Framework terms with the October 2026 Agent Bricks CLI deployment guidance before migrating code. Enable MLflow tracing of the authorized tool invocation, input parameters and result metadata with sensitive values redacted. Route policy prose to the document agent and current counts to governed Genie data tooling, then reconcile the combined answer with citations. ExplanationCorrect Answer B:The action targets the stated cause: Historical certification vocabulary and current agent serving products can describe different deployment lifecycles. Check the repair by: verify a staging deployment with supported agent entry points, health checks and trace capture against current docs. Other Answers A:Historical certification vocabulary and current agent serving products can describe different deployment lifecycles. C:Historical certification vocabulary and current agent serving products can describe different deployment lifecycles. D:Historical certification vocabulary and current agent serving products can describe different deployment lifecycles.
Question 365 A custom Python agent uses an old deployment scaffold that no longer aligns with current Agent Runtime guidance. Why does the current approach fail under these conditions? Historical certification vocabulary and current agent serving products can describe different deployment lifecycles. Different facts live in different authoritative systems; a multi-agent router can delegate to each without conflating evidence types. Agent behavior spans tool calls and intermediate messages; missing spans block root-cause attribution. Trace context provides causality between retrieval, tool execution and final generation; isolated logs cannot reconstruct the path. ExplanationCorrect Answer A:Reconcile the March exam's Agent Framework terms with the October 2026 Agent Bricks CLI deployment guidance before migrating code. Other Answers B:That mechanism describes another problem: A user asks a mixed question about warranty terms and current claim counts, but one general assistant fabricates both from a single paragraph. It does not explain this case, where historical certification vocabulary and current agent serving products can describe different deployment lifecycles. C:Historical certification vocabulary and current agent serving products can describe different deployment lifecycles. D:Historical certification vocabulary and current agent serving products can describe different deployment lifecycles.
Question 366 A custom Python agent uses an old deployment scaffold that no longer aligns with current Agent Runtime guidance. Which observation would establish that the requirement is now met? Test a mixed question and verify the policy citation and SQL-backed count both appear with correct provenance. Select a failed response in MLflow and navigate to the exact source/tool span responsible for its unsupported content. Verify a staging deployment with supported agent entry points, health checks and trace capture against current docs. Replay the invoice and inspect an end-to-end trace linking the request, SQL query span and returned amount. ExplanationCorrect Answer C:Historical certification vocabulary and current agent serving products can describe different deployment lifecycles. Other Answers A:Verify a staging deployment with supported agent entry points, health checks and trace capture against current docs. B:Verify a staging deployment with supported agent entry points, health checks and trace capture against current docs. D:Verify a staging deployment with supported agent entry points, health checks and trace capture against current docs.
Question 367 A custom Python agent uses an old deployment scaffold that no longer aligns with current Agent Runtime guidance. What lasting control best prevents recurrence of the identified issue? Require reproducible trace IDs and stable experiment tagging for each agent revision. Standardize trace instrumentation and safe field redaction across agent tools. Maintain a platform-version crosswalk and migration test suite rather than hard-coding legacy sample APIs. Document per-agent evidence boundaries and validate cross-agent answer aggregation. ExplanationCorrect Answer C:Historical certification vocabulary and current agent serving products can describe different deployment lifecycles. Other Answers A:That historical certification vocabulary and current agent serving products can describe different deployment lifecycles. B:Historical certification vocabulary and current agent serving products can describe different deployment lifecycles. D:This control addresses a different exposure: A user asks a mixed question about warranty terms and current claim counts, but one general assistant fabricates both from a single paragraph. It would not prevent this failure, because historical certification vocabulary and current agent serving products can describe different deployment lifecycles.
Question 368 A multi-tool agent is returning unpredictable answers because intermediate tool results are not linked to the generated text in its MLflow experiment. What is the most targeted corrective step for this observed failure? Reconcile the March exam's Agent Framework terms with the October 2026 Agent Bricks CLI deployment guidance before migrating code. Compare factual groundedness and error severity alongside lexical overlap; reject the model change until unsupported claims are addressed. Enable MLflow tracing of the authorized tool invocation, input parameters and result metadata with sensitive values redacted. Log tool result identifiers and prompt context spans in the trace, then use recorded traces to review the failing branches. ExplanationCorrect Answer D:The action targets the stated cause: Trace context provides causality between retrieval, tool execution and final generation; isolated logs cannot reconstruct the path. Check the repair by: select a failed response in MLflow and navigate to the exact source/tool span responsible for its unsupported content. Other Answers A:Trace context provides causality between retrieval, tool execution and final generation; isolated logs cannot reconstruct the path. B:Trace context provides causality between retrieval, tool execution and final generation; isolated logs cannot reconstruct the path. C:Trace context provides causality between retrieval, tool execution and final generation; isolated logs cannot reconstruct the path.
Question 369 A multi-tool agent is returning unpredictable answers because intermediate tool results are not linked to the generated text in its MLflow experiment. What is the decisive mechanism behind the observed result? Surface-form similarity cannot establish factual entailment or safety in free-form generated explanations. Historical certification vocabulary and current agent serving products can describe different deployment lifecycles. Trace context provides causality between retrieval, tool execution and final generation; isolated logs cannot reconstruct the path. Agent behavior spans tool calls and intermediate messages; missing spans block root-cause attribution. ExplanationCorrect Answer C:Log tool result identifiers and prompt context spans in the trace, then use recorded traces to review the failing branches. Other Answers A:Trace context provides causality between retrieval, tool execution and final generation; isolated logs cannot reconstruct the path. B:Trace context provides causality between retrieval, tool execution and final generation; isolated logs cannot reconstruct the path. D:That mechanism describes another problem: An agent produces a wrong invoice answer, and its current logs show only the final chat message, not the SQL tool call used. It does not explain this case, where trace context provides causality between retrieval, tool execution and final generation; isolated logs cannot reconstruct the path.
Question 370 A multi-tool agent is returning unpredictable answers because intermediate tool results are not linked to the generated text in its MLflow experiment. Which verification is strongest for this particular failure mode? Select a failed response in MLflow and navigate to the exact source/tool span responsible for its unsupported content. Use adjudicated summary cases to score citation support and hallucinations separately from n-gram overlap. Replay the invoice and inspect an end-to-end trace linking the request, SQL query span and returned amount. Verify a staging deployment with supported agent entry points, health checks and trace capture against current docs. ExplanationCorrect Answer A:Trace context provides causality between retrieval, tool execution and final generation; isolated logs cannot reconstruct the path. Other Answers B:Select a failed response in MLflow and navigate to the exact source/tool span responsible for its unsupported content. C:Select a failed response in MLflow and navigate to the exact source/tool span responsible for its unsupported content. D:Select a failed response in MLflow and navigate to the exact source/tool span responsible for its unsupported content.
