nerdexam
Amazon

SAP-C02 · Question #766

A company plans to migrate a legacy on-premises application to AWS. The application is a Java web application that runs on Apache Tomcat with a PostgreSQL database. The company does not have access…

The correct answer is D. Use AWS Elastic Beanstalk to deploy the Tomcat servers with auto scaling in multiple Availability. To migrate a legacy Java web application with JAR files and minimal operational overhead, AWS Elastic Beanstalk is the most suitable solution as it natively supports Tomcat, handles automatic scaling, and manages the underlying infrastructure.

Submitted by tarun92· Mar 6, 2026Migrate Workloads and Modernize Solutions

Question

A company plans to migrate a legacy on-premises application to AWS. The application is a Java web application that runs on Apache Tomcat with a PostgreSQL database. The company does not have access to the source code but can deploy the application Java Archive (JAR) files. The application has increased traffic at the end of each month. Which solution will meet these requirements with the LEAST operational overhead?

Options

  • ALaunch Amazon EC2 instances in multiple Availability Zones. Deploy Tomcat and PostgreSQL to
  • BProvision Amazon Elastic Kubernetes Service (Amazon EKS) in an Auto Scaling group across
  • CRefactor the Java application into Python-based containers. Use AWS Lambda functions for the
  • DUse AWS Elastic Beanstalk to deploy the Tomcat servers with auto scaling in multiple Availability

How the community answered

(63 responses)
  • A
    3% (2)
  • B
    13% (8)
  • C
    6% (4)
  • D
    78% (49)

Why each option

To migrate a legacy Java web application with JAR files and minimal operational overhead, AWS Elastic Beanstalk is the most suitable solution as it natively supports Tomcat, handles automatic scaling, and manages the underlying infrastructure.

ALaunch Amazon EC2 instances in multiple Availability Zones. Deploy Tomcat and PostgreSQL to

Launching Amazon EC2 instances directly requires manual management of the operating system, Apache Tomcat, and PostgreSQL, which results in significant operational overhead.

BProvision Amazon Elastic Kubernetes Service (Amazon EKS) in an Auto Scaling group across

Provisioning Amazon Elastic Kubernetes Service (Amazon EKS) involves managing a Kubernetes cluster, which has higher operational overhead and typically requires containerizing the application, which may not be straightforward with only JAR files and no source code access.

CRefactor the Java application into Python-based containers. Use AWS Lambda functions for the

Refactoring the Java application into Python-based containers and using AWS Lambda for the database is a significant re-architecture effort, not a migration with the least operational overhead, and is not feasible without access to the source code.

DUse AWS Elastic Beanstalk to deploy the Tomcat servers with auto scaling in multiple AvailabilityCorrect

AWS Elastic Beanstalk is a Platform as a Service (PaaS) that natively supports deploying Java web applications on Apache Tomcat from JAR files, automatically handling the provisioning, load balancing, auto scaling, and health monitoring of the underlying infrastructure, thus providing the least operational overhead.

Concept tested: PaaS (Elastic Beanstalk) for Web Application Migration

Source: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/Welcome.html

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full SAP-C02 Practice