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

  Amazon EC2 Auto Scaling is a service that automatically adjusts the number of EC2 instances in a group based on conditions like CPU utilization or network traffic, but it is not a deployment platform. The team must manually create an AMI or use a configuration script to get the application onto instances, define launch templates, set up an Auto Scaling group, and connect it to a load balancer. It does not orchestrate the deployment of new code and provides no native mechanism for application-level health checks or rolling version updates. Therefore, it leaves most of the infrastructure management and deployment complexity in the hands of the developers, which is exactly what the team wants to avoid.

• ✗

  AWS CloudFormation

  Why it's wrong here

  AWS CloudFormation is an infrastructure-as-code service that provisions and manages AWS resources by defining them in declarative templates. However, using CloudFormation requires deep knowledge of AWS components such as EC2, VPCs, load balancers, and IAM, and every resource—including the server, scaling policies, and deployment mechanism—must be explicitly defined. It does NOT accept uploaded application code and automatically handle the rest; instead, you must also design a deployment strategy to get your code onto the provisioned resources. This makes it far more complex than the simple 'upload code and deploy' workflow the scenario requires.

• ✗

  Amazon ECS

  Why it's wrong here

  Amazon ECS is a container orchestration service that runs Docker containers on a managed cluster of EC2 instances. To use ECS, the team must first containerize the application by writing a Docker image, define task definitions, configure the cluster, set up networking, and manage service auto scaling. ECS does not accept plain application source code—it expects container images—and the team must still handle load balancers, scaling, and deployment pipelines. This adds significant operational overhead compared to a fully managed platform that accepts raw code and runs it directly.

• ✓

  AWS Elastic Beanstalk

  Why this is correct

  AWS Elastic Beanstalk is a Platform-as-a-Service (PaaS) specifically created for developers who want to deploy applications without dealing with the underlying infrastructure. You upload your code (or a ZIP/war file) and choose a supported platform such as Java, Node.js, Python, or Docker, and Elastic Beanstalk automatically provisions the needed resources—EC2 instances, a load balancer, an auto scaling group, and health monitoring—behind the scenes. It also manages capacity scaling and rolling application updates with minimal configuration, while still allowing fine-grained control through configuration files when needed. This makes it the simplest and most direct fit for the stated need.

Go deeper

Related to this question