Circuit Breaker Pattern for Amazon Bedrock Pipeline Failures
Short answer
C Use a CloudWatch alarm on Bedrock error rates with an EventBridge rule to switch Step Functions traffic to an alternate processing path and automatically resume when recovered.
Question
The company needs a solution to detect when error rates exceed 10% within any 60-second window. The solution must switch to an alternate process path when the error rate threshold is exceeded. The solution must automatically resume normal Amazon Bedrock processing when the pipeline recovers. The company must ensure that the pipeline processes all documents within 15 minutes.
Which solution will meet these requirements?
Key Takeaways
The question tests the circuit breaker pattern for a Bedrock pipeline; the common trap is choosing custom DynamoDB failure tracking over CloudWatch's native alarm and EventBridge-driven automation.
This question tests how to implement an automated circuit breaker for an Amazon Bedrock document-processing pipeline using AWS Step Functions, CloudWatch alarms, and EventBridge. The correct solution uses a CloudWatch alarm to detect error-rate thresholds and EventBridge to automatically switch traffic, ensuring recovery without manual intervention.
Common mistake: Learners often choose Option A, which implements circuit-breaker logic via DynamoDB, because it uses the term 'circuit breaker pattern.' However, CloudWatch alarms natively handle threshold-based detection (10% over 60 seconds) and EventBridge provides event-driven switching—making Option C more idiomatic, scalable, and fully automated.
Expert Analysis
Why the Answer Is Correct
Option C correctly combines an AWS Step Functions state machine with Retry/Catch logic for resilient Bedrock invocations, a CloudWatch alarm to detect when error rates exceed 10% within any 60-second evaluation window, and an EventBridge rule to automatically redirect traffic to the alternate processing path. CloudWatch alarms natively support percentage-based thresholds over configurable windows, precisely matching the requirement. When the alarm transitions back to OK state, the EventBridge rule can trigger a return to the normal Bedrock path, satisfying the automatic-recovery requirement. This is the standard AWS architectural pattern for circuit breaking at the monitoring and event-routing layer.
Why the Other Options Are Wrong
Option A tracks failures in DynamoDB and routes based on that state—functional but ad hoc—requiring custom logic to evaluate the 10%/60-second threshold and manage recovery state manually within Step Functions. Option B requires company staff to manually update the workflow, which violates the automatic-resume requirement. Option D deploys multiple state machines behind API Gateway with a health-check Lambda routing to the fastest responder—this adds complexity but does not detect the specific 10% error-rate threshold or implement a true circuit breaker with automatic recovery.
Community Comment Notes
TNT87 voted for Option A, arguing the circuit breaker pattern with DynamoDB is the standard architectural method. However, while DynamoDB-based tracking is a valid implementation detail, it requires more custom code to evaluate the specific 10%/60-second threshold and manage recovery. CloudWatch alarms (Option C) handle this out of the box and pair naturally with EventBridge for event-driven automation, making C the more idiomatic AWS solution.
Official Reference
https://docs.aws.amazon.com/step-functions/latest/dg/circuit-breaker-pattern.html
This link opens the official vendor documentation in a new tab.
Exam Strategy
On AWS architecture questions, prefer solutions that use managed, native AWS services (CloudWatch alarms, EventBridge) over custom tracking logic—managed services handle threshold detection and event-driven automation more reliably and with less code. Always verify that the option fully automates both failure detection AND recovery with no manual steps.
Frequently Asked Questions
Why not use DynamoDB to track Bedrock failures as a circuit breaker?
Does Option C automatically resume Bedrock processing after recovery?
Discussion 2 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 2
-
sghdfghdfghdghdfh4w56346he346h 👍 1 Answered ACorrect answer: A. Use an AWS Step Functions workflow to implement a circuit breaker pattern, tracking Amazon Bedrock invocation failures in Amazon DynamoDB and routing processing jobs to an alternate path when the failure threshold is exceeded. Why A is correct Detect failures: Track invocation failures and calculate whether the error rate exceeds 10% within a rolling 60-second window. Automatic failover: When the threshold is exceeded, the workflow routes jobs to the alternate processing path without waiting for manual intervention. Automatic recovery: The circuit breaker can periodically check the failure state and resume normal Bedrock processing when the service recovers. Meet the 15-minute deadline: The workflow can use bounded retries, timeouts, and an alternate processing path to keep document processing within the required time limit. Why the other options are incorrect B: Requires staff to manually divert traffic, so failover is not automatic. C: Retry/Catch logic handles individual failures, but the proposed alarm-to-EventBridge routing does not, by itself, implement reliable dynamic routing and automatic recovery for the state machine. D: Routing to whichever state machine responds fastest does not explicitly enforce the 10% error threshold or implement circuit-breaker recovery.
-
TNT87 👍 1 Answered A• Circuit Breaker Pattern: Implementing a circuit breaker pattern is the standard architectural method to handle intermittent failures or timeouts of a downstream service under heavy load. By tracking invocation failures in a fast, low-latency datastore like Amazon DynamoDB, the Step Functions workflow can dynamically decide whether to attempt normal execution or divert to the alternate processing path automatically based on the failure rate. • Automation: It satisfies the requirement to automatically switch to the alternate path and gracefully resume normal Amazon Bedrock processing when the system recovers.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All AIP-C01 Questions
Access 110 questions with complete answers and detailed explanations.
View Full AIP-C01 Practice Test →