Q33 — AWS SAA-C03 Ch.14
Question 33 of 100 | ← Chapter 14
Q1033. A company currently runs an on-premises application that usesASP.NET on Linux machines. The application is resource-intensive and serves customers directly.The company wants to modernize the application to .NET. The company wants to run the application on containers and to scale based on Amazon CloudWatch metrics. The company also wants to reduce the time spent on operational maintenance activities.Which solution will meet these requirements with the LEAST operational overhead?
- A. Use AWS App2Container to containerize the application. Use an AWS CloudFormation template to deploy the application to Amazon Elastic Container Service (Amazon ECS) on AWS Fargate. ✓
- B. Use AWS App2Container to containerize the application. Use an AWS CloudFormation template to deploy the application to Amazon Elastic Container Service (Amazon ECS) on Amazon EC2 instances.
- C. Use AWS App Runner to containerize the application. Use App Runner to deploy the application to Amazon Elastic Container Service (Amazon ECS) on AWS Fargate.
- D. Use AWS App Runner to containerize the application. Use App Runner to deploy the application to Amazon Elastic Kubernetes Service (Amazon EKS) on Amazon EC2 instances.
Correct Answer: A. Use AWS App2Container to containerize the application. Use an AWS CloudFormation template to deploy the application to Amazon Elastic Container Service (Amazon ECS) on AWS Fargate.
Explanation
To modernize the application from ASP.NET on Linux machines to a containerized environment with minimal operational overhead, the best solution is:A. Use AWS App2Container to containerize the application. Use an AWS CloudFormation template to deploy the application to Amazon Elastic Container Service (Amazon ECS) on AWS Fargate.Explanation:\1. AWS App2Container: - This tool simplifies the process of containerizing existing applications, allowing for a smooth transition from an on-premises environment to a containerized architecture without extensive manual effort.\2. Amazon ECS on AWS Fargate: - Deploying the application on AWS Fargate means that the company does not have to manage the underlying EC2 instances. Fargate is a serverless compute engine for containers that automatically handles the scaling and operational maintenance, significantly reducing the operational overhead.\3. Scaling with CloudWatch Metrics: - ECS can be configured to scale based on CloudWatch metrics, ensuring that the application can handle varying loads efficiently. Fargate integrates seamlessly with ECS, providing automatic scaling capabilities.Evaluation of Other Options:B. Use AWS App2Container to containerize the application. Use an AWS CloudFormation template to deploy the application to Amazon Elastic Container Service (Amazon ECS) on Amazon EC2 instances: - While this option works, managing EC2 instances adds operational overhead compared to using Fargate. You would need to handle instance provisioning, scaling, and maintenance.C. Use AWS App Runner to containerize the application. Use App Runner to deploy the application to Amazon Elastic Container Service (Amazon ECS) on AWS Fargate: - AWS App Runner is a good option for simpler applications but is not necessary in this case since App2Container is already being used for containerization. This option would introduce unnecessary complexity as it involves two different services for a similar outcome.D. Use AWS App Runner to containerize the application. Use App Runner to deploy the application to Amazon Elastic Kubernetes Service (Amazon EKS) on Amazon EC2 instances: - This option adds significant operational overhead due to the complexity of managing EKS and the underlying EC2 instances. EKS requires more management compared to ECS with Fargate, making it less suitable for minimizing operational activities.Conclusion:Option A provides the most efficient and least operationally intensive solution for modernizing the application, leveraging AWS services effectively to reduce maintenance while ensuring scalability and performance.