Key points
- Retry-with-error-feedback: the follow-up includes the original document, the failed extraction and the specific validation errors.
- Retries are ineffective when the required information is absent from the source; they work for format mismatches and structural errors.
- A detected_pattern field records which construct triggered a finding, so dismissals can be analyzed for systematic false positives.
- Semantic errors (values that do not sum, wrong field placement) differ from schema syntax errors, which tool use eliminates.
- Extracting calculated_total next to stated_total and adding conflict_detected lets the output flag its own inconsistencies.
Skills the exam expects
- Build follow-up requests with document, failed output and specific errors for self-correction.
- Recognize when a retry will not work (information lives in a document not provided) versus when it will.
- Add detected_pattern to structured findings to analyze false-positive patterns.
- Design self-correction flows with calculated versus stated totals and conflict flags.
Common misconceptions
- "Resending the same prompt is a retry." Without the errors it is a blind re-roll.
- "Enough retries will eventually find the missing value." Absent data stays absent; the retries just cost money.
- "Schema validation catches wrong values." It catches wrong shapes.
Watch for
- Retry loops that never classify why the validation failed.
- Pressure to fill required fields, which invites fabrication.
- Findings that carry only a message and severity, leaving dismissals impossible to analyze.
Practice task 4.4
56 practice items cover this task in CCA Prep Studio: flashcards, matching, scenario questions and explain-it-back exercises, each tracked toward your mastery score.