Claude Certified Architect — Foundations · Free practice question 5 of 10
Evidence fields for auditable structured output
Your support automation summarizes customer threads into JSON for downstream routing. Product wants to start measuring how often the summary's "topic" field is wrong. Which output-design change best supports that measurement?
- A.Add a `rationale: string` field explaining why the topic was chosen.
- B.Add an `evidence: { thread_msg_ids: string[] }` field listing which messages drove the topic decision.
- C.Lower the temperature so the summary is more deterministic.
- D.Have Claude emit the top three candidate topics, not just one.
Show answer and explanation
Correct answer: B. Add an `evidence: { thread_msg_ids: string[] }` field listing which messages drove the topic decision.
Why: Wrongness is only auditable if you can trace the decision back to source. Listing the messages that influenced the topic gives reviewers a concrete artifact to disagree with. Rationales are useful but unfalsifiable; multiple topics multiply the labeling cost without anchoring the disagreement.
More free Claude Certified Architect — Foundations questions
- Narrowing label definitions to stop over-triggering
- Severity and confidence metadata for review findings
- Tool-based verification to prevent hallucinated APIs
- Precision vs recall trade-offs in extraction
- Tool schemas for strict JSON conformance
- Routing scarce human review capacity
- Execution-based evals for SQL generation
- Prompt caching for repeated context
- Shadow-mode rollout for prompt changes