CLF-C02 Cloud Technology and Services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Amazon EventBridge

  Why it's wrong here

  Amazon EventBridge is a serverless event bus service that ingests and routes events between AWS services, SaaS applications, and custom apps based on rules. It reacts to individual events by invoking targets, but it does not maintain execution state or define a sequence of dependent steps. While you could chain multiple EventBridge rules together, that would not provide the built-in retry, rollback, or state management needed for true workflow orchestration, so it is not the right service for this use case.

• ✗

  Amazon SQS

  Why it's wrong here

  Amazon SQS is a fully managed message queuing service that decouples application components by allowing them to exchange messages asynchronously. A queue simply holds messages until a consumer polls and processes them, and it has no concept of a workflow or a state machine. SQS offers retries only at the individual message level, not across a multi-step business process, and it cannot automatically execute subsequent steps, make decisions, or track progress. Therefore, using SQS alone would require you to build all orchestration logic manually, which is why it is not correct.

• ✓

  AWS Step Functions

  Why this is correct

  AWS Step Functions is a serverless orchestration service that lets you define workflows as state machines using the Amazon States Language (ASL). It supports sequential steps, parallel branches, choice states, wait states, and Map/Item loops, while automatically managing execution state and ensuring that each step's output feeds into the next. Step Functions provides native error handling, configurable retry policies with exponential backoff, and integrated service calls via the AWS SDK connectors, making it ideal for orchestrating complex, multi-step processes across hundreds of AWS services. This combination of state management and resilience is precisely what the scenario requires, so it is the correct answer.

• ✗

  AWS Batch

  Why it's wrong here

  AWS Batch is a job scheduling and compute service designed specifically for batch computing workloads that run as containerized jobs on managed EC2 or Fargate compute environments. It handles job queueing, dependency analysis, and dynamic provisioning of compute resources, but it does not function as a general-purpose workflow orchestrator. AWS Batch lacks built-in states for branching, human approval, or cross-service integration, and its retry and error handling are limited to job submission rather than step-level workflow recovery. Because the scenario asks for orchestration of a multi-step process with state management, AWS Batch is not the appropriate choice.

Go deeper

Related to this question