A company developed a multimodal content analysis application by using Amazon Bedrock. The application routes different content types (text, images…

This scenario requires a solution that efficiently handles two distinct routing paths: a low-latency path for simple decisions and an orchestrated path for complex ones. A hybrid approach is optimal. Simple routing based on file extensions can be handled directly in the application code for minimal latency. For complex semantic analysis and routing, AWS Step Functions is the ideal service. It provides a visual workflow to orchestrate multiple steps, maintains a detailed execution history for auditing, and has built-in error handling (e.g., Catch fields) to implement fallback logic when a primary model fails. This separation of concerns meets all requirements effectively.

A. A single Lambda function for all logic would introduce unnecessary latency for simple requests and makes implementing robust, stateful fallbacks and history tracking more complex than using a dedicated orchestration service.
C. Using separate Step Functions workflows coordinated by EventBridge is overly complex. A single state machine can handle conditional logic and fallbacks internally, reducing architectural complexity and potential points of failure.
D. Amazon SQS is a queuing service, not an orchestration engine. While it decouples components, it does not provide the state management, detailed history, or built-in error handling needed for the complex routing workflow.

1. AWS Step Functions Developer Guide. (2024). What is AWS Step Functions? "AWS Step Functions is a visual workflow service that helps developers use AWS services to build distributed applications, automate processes, orchestrate microservices, and create data and machine learning (ML) pipelines."

2. AWS Step Functions Developer Guide. (2024). Error handling in Step Functions. "Step Functions state machines can be configured to handle errors... A state can have a field named Catch, whose value must be an array of objects that are known as catchers."

3. AWS Step Functions Developer Guide. (2024). Execution history. "Step Functions provides visibility into each execution's history. You can review the detailed information... in the Step Functions console."