CCAR-F practice › Prompt Engineering & Structured Output · Question 82 of 105
Prompt Engineering & Structured Output
Documents arrive throughout the day and must be processed within 30 hours of arrival. The pipeline uses the Message Batches API, which can take up to 24 hours to process a batch, and currently submits one batch every 24 hours. How should submission be scheduled?
Show answer and explanation
Answer: C — Submit about every 4 hours, keeping wait plus processing under 30 hours
Worst-case latency is the wait for the next submission plus up to 24 hours of processing. Every 4 hours gives about 28 hours, inside the SLA with margin. Daily (a) gives 48 hours, and batches have no latency guarantee. Every 12 hours (b) gives 36, and every 8 hours (d) gives 32, both over the SLA.
Keep going
More Prompt Engineering & Structured Output questions
- 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…
- A Claude session generates a database migration, then in the same session is asked to…
- A team moved its large pull request reviews to one pass per file, and review depth is…
- A review pipeline posts every finding directly to pull requests. The team wants to send…