How to Meet a 10-Second Bedrock Batch Analysis SLA?
A financial services company needs to build a document analysis system that uses Amazon Bedrock to process quarterly reports. The system must analyze financial data, perform sentiment analysis, and validate compliance across batches of reports. Each batch contains 5 reports. Each report requires multiple foundation model (FM) calls. The solution must finish the analysis within 10 seconds for each batch. Current sequential processing takes 45 seconds for each batch. Which solution will meet these requirements?
Community Insight
The test is spotting that a 4.5x latency gap requires explicit parallel fan-out across analysis tasks, not warmed Lambda capacity or more queue consumers; options that keep the per-report chain sequential are traps.
This question asks how to orchestrate Amazon Bedrock document analysis so a five-report batch finishes in 10 seconds instead of the current 45 seconds. The page establishes that a Step Functions Parallel state with concurrent Lambda branches is the correct answer (B) over sequential Lambda, SQS buffering, or ECS containers.
The common wrong pick is A because provisioned concurrency sounds like a performance fix, but it only reduces cold starts; the financial, sentiment, and compliance calls still execute sequentially and a 10-second Lambda timeout can cut them off.
Community Discussion (9 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option B is the only choice that explicitly removes the sequential bottleneck: a Step Functions Parallel state fans out separate Lambda functions for financial analysis, sentiment analysis, and compliance validation so their Bedrock FM calls overlap instead of running one after another. It also keeps the operational controls the scenario needs, including Bedrock client timeouts to cap slow model calls and CloudWatch metrics to confirm the batch stays under the 10-second target. Within this option set, that is the intended horizontal-scaling pattern for a 45-second to sub-10-second requirement, even if a Step Functions Map state over the five reports could provide additional report-level fan-out.Why the Other Options Are Wrong
Option A keeps the analysis types sequential, so provisioned concurrency only reduces cold starts and does not fix the 45-second critical path; a 10-second Lambda timeout can even truncate work. Option C adds an SQS buffer and reserved concurrency, but it still describes processing aspects of each report sequentially and adds queue latency without an explicit parallel orchestration step. Option D runs containers that process each report sequentially and relies on CPU-based auto-scaling plus a load balancer, which does not collapse the 45-second chain within a strict 10-second SLA. None of A, C, or D introduces the explicit Parallel state that makes the Bedrock analysis branches run concurrently.Community Comment Notes
Several learners converged on B: eesa described the Parallel state as the best solution because it processes financial, sentiment, and compliance analyses simultaneously instead of sequentially, and tumi98 emphasized concurrent execution plus Bedrock timeouts and CloudWatch. Chibuzo1 framed the requirement as roughly a 4.5x speedup that only parallelization can deliver. blieskies raised a worthwhile nuance, saying "I wish they'd suggested MAP instead of PARALLEL," which is a reminder that Map over the five reports may be an even tighter design, but Parallel remains the best fit among the offered options. GiorgioGss dismissed the alternatives succinctly because they add latency.Official Reference
Exam Strategy
When a question gives a current time and a target time, calculate the required speedup before reading the options; if it is greater than 1, look for explicit parallel branches or Map/Parallel states. Treat provisioned and reserved concurrency as throughput controls, not as latency reducers for a single sequential chain.
Frequently Asked Questions
Why doesn't provisioned concurrency in Option A meet the 10-second batch requirement?
Provisioned concurrency keeps Lambda instances warm but still runs financial, sentiment, and compliance analysis sequentially; it reduces cold starts, not the 45-second critical path.
Would an SQS queue with reserved concurrency in Option C be enough to parallelize five reports?
It can increase throughput, but it does not by itself orchestrate the three analysis types in parallel, and queue buffering adds latency to a strict 10-second per-batch SLA.
Related Analysis
Practice All AIP-C01 Questions
Access 110 questions with complete answers and detailed explanations.
View Full AIP-C01 Practice Test →