Scenario 6: Structured Data Extraction

You are building a structured data extraction system using Claude. The system extracts information from unstructured documents, validates the output using JavaScript Object Notation (JSON) schemas, and maintains high accuracy. It must handle edge cases gracefully and integrate with downstream systems.

Passage quoted verbatim from the official CCAR-F exam guide v1.0, section 5.

This scenario on the exam

Scenario: 6 of 6 — four are dealt at random
Primary domains: 2
Questions in this hive: 45

Primary domains

Prompt Engineering & Structured Output
Context Management & Reliability

What the exam asks inside this context

Guaranteed shape. tool_use with a JSON schema, and tool_choice set so a tool is actually called — 'any' when the document type is unknown, forced when one extraction must run first.
Schema design against fabrication. Optional and nullable fields where the source may be silent; an 'unclear' enum value and 'other' plus a detail string where the categories may not fit.
Validation that catches meaning. Schemas remove syntax errors and leave semantic ones. calculated_total beside stated_total, and a conflict_detected boolean, put the check in the output shape.
Retry, and knowing when not to. Retry with the specific validation errors attached. Do not retry when the information is simply absent from the document.

Scenario 6: Structured Data Extraction

You are building a structured data extraction system using Claude. The system extracts information from unstructured documents, validates the output using JavaScript Object Notation (JSON) schemas, and maintains high accuracy. It must handle edge cases gracefully and integrate with downstream systems.

Passage quoted verbatim from the official CCAR-F exam guide v1.0, section 5.

This scenario on the exam

Scenario: 6 of 6 — four are dealt at random
Primary domains: 2
Questions in this hive: 45

What the exam asks inside this context

Guaranteed shape. tool_use with a JSON schema, and tool_choice set so a tool is actually called — 'any' when the document type is unknown, forced when one extraction must run first.

Schema design against fabrication. Optional and nullable fields where the source may be silent; an 'unclear' enum value and 'other' plus a detail string where the categories may not fit.

Validation that catches meaning. Schemas remove syntax errors and leave semantic ones. calculated_total beside stated_total, and a conflict_detected boolean, put the check in the output shape.

Retry, and knowing when not to. Retry with the specific validation errors attached. Do not retry when the information is simply absent from the document.