Question 38
Domain 5Your document processing pipeline must return results within 30 hours of document receipt. You plan to use the Message Batches API (24-hour processing window). What is the maximum allowable time between document receipt and batch submission to guarantee the 30-hour SLA?
Correct answer: C
Explanation
The Message Batches API has a "24-hour processing window," so once a batch is submitted, processing can take up to 24 hours. To meet a 30-hour end-to-end SLA from document receipt, the remaining time before submission is 30 minus 24, which is 6 hours.
Why each option is right or wrong
A. 12 hours — leave buffer on both sides of the 24-hour window
Adding extra buffer is unnecessary; 12 hours would exceed the 30-hour total in worst case.
B. 24 hours — the batch window starts after submission so documents can wait a full day
A full 24-hour wait before submission leaves no time for the batch's own 24-hour processing window.
C. 6 hours — SLA (30h) minus the maximum batch processing time (24h) leaves 6 hours for pre-submission queuing
The Message Batches API allows up to a 24-hour processing window after submission, so that entire interval must be reserved in the end-to-end schedule. To satisfy a 30-hour service-level deadline measured from document receipt, the latest permissible delay before submission is 30 hours minus 24 hours, leaving 6 hours for intake, validation, and queueing before the batch is sent.
D. There is no safe window; the Batches API cannot guarantee a 30-hour SLA
A safe window exists if pre-submission delay is capped at 6 hours.