A small team has a Java web application and no operations staff. They want to hand AWS the application package and have it provision the instances, the load balancer and the scaling policy, while keeping the ability to inspect and adjust those resources later if they need to. Which service fits?

AWS Certified Cloud Practitioner (CLF-C02), objective 3. Cloud technology and services easy

Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.

Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.

The options

Correct AWS Elastic Beanstalk

Correct. You upload the application and Beanstalk provisions and manages the environment for you, on a supported platform. The resources it creates remain visible and adjustable in your account, and Beanstalk itself carries no extra charge beyond what those resources cost.

Not correct AWS Lambda

Wrong for this shape of application. Lambda also removes server management, but it expects the code to be repackaged as event-driven functions with a maximum run time per invocation, and it gives you no environment to inspect at all.

Not correct Amazon EC2 on its own

Wrong. EC2 hands you the servers and nothing else. Choosing an AMI, installing the runtime, wiring a load balancer and writing the scaling policy are all still yours, which is the work this team said it cannot staff.

Not correct AWS CloudFormation

Wrong, though related. CloudFormation faithfully builds whatever infrastructure you describe, which means you first have to know and write down what the application needs. It never takes application code and chooses a platform for it.

Why

Line these up by how much you hand over. EC2: you build everything. CloudFormation: you describe everything, once, and it builds it. Elastic Beanstalk: you supply the code and AWS chooses and manages the environment, which you can still see and tune. Lambda and Fargate: no servers of yours at all. Beanstalk is the usual answer when a question stresses both 'just deploy my code' and 'we still want access to the underlying resources'.

Where this comes from

Cited
AWS exam guide task statement 3.1

Practise this

Reading one question is not practice. The trainer will draw a set from objective 3 and space the ones you get wrong.

Practise AWS Certified Cloud Practitioner (CLF-C02)

More questions on this objective

All questions on Cloud technology and services