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 EC2 Auto Scaling

  Why it's wrong here

  Incorrect. Amazon EC2 with Auto Scaling still requires provisioning and managing Amazon Machine Images (AMIs), instances, and scaling policies. You pay for running instances even when no requests are being processed, which does not meet the 'pay only for compute time when requests are processed' requirement. It also involves more operational overhead than desired.

  When this WOULD be correct

  A company needs to run a stateful application that requires persistent storage or long-running processes, and expects steady or predictable traffic. The team is willing to manage server configurations but wants to automatically adjust capacity based on demand.

• ✓

  AWS Lambda

  Why this is correct

  Correct. AWS Lambda is a serverless compute service that runs your code only when triggered (e.g., via Amazon API Gateway). It automatically scales to handle any number of requests and you pay only for the compute time consumed during execution (per millisecond). There are no servers or containers to manage, aligning perfectly with the team's focus on writing code and minimizing operational overhead.

• ✗

  AWS Fargate

  Why it's wrong here

  AWS Fargate is incorrect because, while it abstracts away the underlying EC2 instances, it still requires the team to manage container images and configure container scaling, which contradicts the desire to focus solely on code and avoid managing containers. Furthermore, Fargate bills for container uptime, not just when requests are processed, failing the pay-per-request requirement. It is tempting as it offers a serverless operational model for containers, making it suitable for teams wanting to run containerised applications without provisioning or managing servers.

  When this WOULD be correct

  A team needs to run containerized applications without managing servers, but the workload has predictable or sustained usage patterns, and they are willing to pay for running containers even when idle. For example, a long-running microservice that processes messages from a queue.

• ✗

  Amazon API Gateway

  Why it's wrong here

  Incorrect. Amazon API Gateway is a fully managed service for creating, publishing, and managing REST APIs. However, it does not execute application code itself; it acts as a proxy or front door to a backend service (such as AWS Lambda or an HTTP endpoint). API Gateway must be used together with a compute service to process requests. Therefore, it alone does not meet the requirement for a compute service.

  When this WOULD be correct

  A company wants to expose a RESTful API to external clients and needs features like request throttling, authentication, and API versioning. The team plans to integrate the API with a backend service (e.g., AWS Lambda or EC2) but wants to offload API management tasks. In this scenario, Amazon API Gateway would be the correct choice.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The CLF-C02 exam frequently reuses these exact scenarios with slightly different constraints.

Analysis generated from the official CLF-C02blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”