
Answer-first summary for fast verification
Answer: AWS Elastic Beanstalk
## Explanation AWS Elastic Beanstalk is the correct choice because: - **Non-containerized Java application**: Elastic Beanstalk is specifically designed for deploying traditional web applications (like Java, .NET, PHP, etc.) without requiring containerization - **Managed service**: Elastic Beanstalk is a fully managed Platform as a Service (PaaS) that handles infrastructure management - **Automatic provisioning**: Automatically provisions and manages the underlying infrastructure including EC2 instances, load balancers, and auto scaling groups - **Load balancing**: Automatically sets up and configures Elastic Load Balancing - **Auto scaling**: Automatically scales the application up and down based on demand - **Health monitoring**: Monitors application health and automatically replaces unhealthy instances - **Quick deployment**: Provides a simple way to deploy applications quickly using familiar deployment methods **Why other options are incorrect**: - **Amazon ECS**: Requires containerization of the application - **AWS Lambda**: Serverless function service, not suitable for traditional web applications - **Amazon EKS**: Kubernetes service that requires containerization and more complex setup Elastic Beanstalk abstracts the underlying infrastructure while giving developers control over their application code and configuration.
Author: Ritesh Yadav
Ultimate access to all questions.
A company wants to deploy a non-containerized Java-based web application on AWS. The company wants to use a managed service to quickly deploy the application. The company wants the service to automatically provision capacity, load balance, scale, and monitor application health. Which AWS service will meet these requirements?
A
Amazon Elastic Container Service (Amazon ECS)
B
AWS Lambda
C
Amazon Elastic Kubernetes Service (Amazon EKS)
D
AWS Elastic Beanstalk
No comments yet.