The correct answer is to **build the workflow using AWS Step Functions and define a state machine that orchestrates AWS Lambda functions to handle each step of the process**. Step Functions provide a fully managed service for coordinating distributed applications using visual workflows. They support retries, parallelism, and conditional logic. By using Lambda for each step, the architecture remains serverless and event-driven, reducing operational overhead and infrastructure management.

The option to use Amazon EventBridge to schedule events and trigger Lambda functions offers event-driven triggers but lacks the ability to define complex workflow logic such as retries, error handling, and sequential step execution. EventBridge is best suited for event routing rather than workflow orchestration.

The suggestion to use AWS Glue to invoke Lambda functions is better suited for ETL workloads involving structured data. AWS Glue provides powerful data cataloging and transformation features, but its not designed for general-purpose workflow orchestration involving diverse application logic.

The choice to use Step Functions with EC2 instances introduces more operational burden. EC2 requires provisioning, patching, and scaling, which contradicts the goal of minimizing operational overhead and embracing serverless concepts.

This question is critical because it tests your understanding of AWS serverless orchestration services. The key to solving it is recognizing that **Step Functions + Lambda** is the ideal combination for serverless, event-driven workflows that require stateful orchestration. The challenge lies in distinguishing between services that handle event routing (like EventBridge) and those that manage multi-step workflows (like Step Functions).

Full AWS Practitioner Certification Question