CCAR-F practice › Prompt Engineering & Structured Output · Question 79 of 105
Prompt Engineering & Structured Output
A vendor-onboarding extractor retries up to five times when tax_id is missing. These retries almost never succeed, and recent logs show later attempts returning tax IDs that don't exist. The tax ID is recorded on a separate registration form that isn't sent with the request. What should the team do?
Show answer and explanation
Answer: C — Stop retrying it: make tax_id nullable, flag it, and take it from the form
Retries can't succeed when the information is absent from the provided document; they only increase pressure to fabricate, which is what the invented IDs show. Make the field nullable, flag the gap, and get the value from its real source. More retries (a) or insisting the value is there (b) make fabrication worse. Prompted JSON (d) gives up schema reliability and doesn't supply the missing data.
Keep going
More Prompt Engineering & Structured Output questions
- An invoice extractor uses tool use with a strict schema, and every response passes…
- Developers dismiss about 40% of an automated reviewer's findings. The team tracks the…
- Documents arrive throughout the day and must be processed within 30 hours of arrival…
- A batch of 5,000 contract extractions completes with 120 failures. Most of the failed…
- A team wants to move workloads to the Message Batches API for its 50% cost savings…