A stable Java application depends on VMs in the company data center and the company wants to modernize while minimizing server administration and code changes. Which migration approach meets these goals with the least code modification?

The correct option minimizes server administration and code changes by leveraging AWS Fargate, a serverless compute engine for containers, eliminating the need to provision or manage servers. AWS App2Container automates containerization, reducing manual effort. Amazon ECS is a managed container orchestration service, and an ALB provides load balancing. This approach offers a good balance of modernization and operational simplicity. Incorrect options: Running as an AWS Lambda container with API Gateway would likely require significant code refactoring for the application to conform to the Lambda event-driven model, which contradicts the "least code modification" requirement. Using Amazon EKS with managed node groups still involves managing Kubernetes clusters and nodes, which is more administrative overhead than Fargate. Also, using API Gateway directly in front of EKS is less common than an ALB or Network Load Balancer for general HTTP/S traffic. Configuring Lambda to use an ALB is possible, but the core issue remains: migrating a stable Java application to Lambda often necessitates substantial code changes to fit the serverless function paradigm.