A startup wants to deploy their web application to AWS with minimal configuration. They want AWS to handle provisioning, load balancing, scaling, and health monitoring automatically. Which service is most appropriate?
Elastic Beanstalk handles all infrastructure management automatically — developers provide the application code and Beanstalk provisions and manages the environment.
Why this answer
AWS Elastic Beanstalk is the correct choice because it is a Platform-as-a-Service (PaaS) offering that automatically handles provisioning, load balancing, auto scaling, and health monitoring with minimal configuration. The startup simply uploads their web application code, and Elastic Beanstalk manages the underlying infrastructure, including the EC2 instances, Elastic Load Balancer, and CloudWatch health checks, without requiring manual setup.
Exam trap
AWS often tests the distinction between managed services (PaaS) and infrastructure services (IaaS), and the trap here is that candidates confuse Amazon EC2 with Auto Scaling as a 'fully managed' solution when it actually requires significant manual configuration for load balancing and health monitoring.
How to eliminate wrong answers
Option A is wrong because Amazon EC2 with Auto Scaling requires manual configuration of the Auto Scaling group, launch templates, load balancer, and health checks, which contradicts the 'minimal configuration' requirement. Option C is wrong because Amazon EKS is a managed Kubernetes service that demands significant setup and expertise to configure clusters, node groups, and networking, making it overkill for a simple web application deployment. Option D is wrong because AWS CloudFormation is an Infrastructure as Code (IaC) service that requires writing and maintaining templates to define resources, which is not a fully managed platform and does not automatically handle provisioning or scaling without explicit configuration.