Q29 of 60 — CCA Practice Exam

Structured Data Extraction

Your team is building a contract analysis pipeline that must both verify claims against source documents (for auditor traceability) and produce a machine-readable JSON output consumed by a downstream CRM system. A developer proposes enabling citations.enabled=true on the uploaded contract PDFs while also setting output_config.format to enforce a strict JSON schema. QA catches that this configuration returns a 400 error before it reaches production. What is the root cause of the incompatibility, and which architectural decision resolves it?

A. Citations interleave citation blocks with text output, which cannot conform to a strict JSON schema; the two requirements must be served by separate API calls — one citations-enabled call for auditor review, one structured-output call for the CRM.

B. The output_config.format parameter conflicts with PDF-type documents specifically; switching the contracts to plain-text document blocks will allow citations and structured outputs to coexist in the same request without a 400 error.

C. Citations are only incompatible with nested JSON schemas; flattening the CRM schema to a single-level object will eliminate the 400 error while still allowing citation blocks to appear in the response alongside the output.

D. The 400 error is triggered by exceeding a document block limit when citations are enabled; splitting the contracts across smaller batched requests will allow both citations and structured outputs to be used together successfully.