Q80 — AWS SAA-C03 Ch.13

Question 80 of 100 | ← Chapter 13

Q980. A company wants to migrate several legacy .NET applications from an on-premises data center to AWS. The company converted the code base for the applications to use a newer version of .NET.The company needs a scalable, high-performance solution to host the updated .NET applications on AWS Which solution will meet these requirements with the LEAST ongoing administrative overhead?

Correct Answer: A. Containerize the .NET applications. Create a task definition in Amazon Elastic Container Service (Amazon ECS) with AWS Fargate as the launch type. Configure auto scaling based on the amount of CPU and memory required.

Explanation

The correct answer is:A. Containerize the .NET applications. Create a task definition in Amazon Elastic Container Service (Amazon ECS) with AWS Fargate as the launch type. Configure auto scaling based on the amount of CPU and memory required.Explanation:A. Containerize the .NET applications. Create a task definition in Amazon Elastic Container Service (Amazon ECS) with AWS Fargate as the launch type. Configure auto scaling based on the amount of CPU and memory required.- This solution would have the least ongoing administrative overhead compared to the other options. With AWS Fargate, you don't have to manage the underlying infrastructure, such as provisioning and scaling the EC2 instances. Fargate automatically handles the container orchestration, resource allocation, and scaling based on the specified CPU and memory requirements.- The containerized approach also provides a consistent runtime environment for the .NET applications, making it easier to manage and deploy the applications across different environments.- Additionally, the ECS auto scaling capabilities can automatically scale the container instances based on the application's resource requirements, ensuring a scalable and high-performance hosting environment.B. Store the static content of the applications in an Amazon S3 bucket. Convert the .NET applications to AWS Lambda functions. Use Amazon API Gateway to route requests to the Lambda functions.- This solution would require significant refactoring of the .NET applications to convert them to Lambda functions, which may not be feasible for legacy applications. It would also introduce additional complexity in terms of managing the API Gateway and Lambda functions.C. Deploy the .NET applications on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer. Use path-based routing to route traffic to the applications.- This solution would provide a scalable and high-performance hosting environment, but it would require ongoing administrative overhead in terms of managing the EC2 instances, the Auto Scaling group, and the Load Balancer.D. Package the applications into deployable archives. Create a new application on AWS Elastic Beanstalk.Upload the deployment archives to Elastic Beanstalk.- This solution would also have low ongoing administrative overhead, as AWS Elastic Beanstalk abstracts away the underlying infrastructure management tasks. However, it may not provide as much flexibility and control as the containerized approach with ECS and Fargate.Therefore, the solution that will meet the requirements with the least ongoing administrative overhead is to containerize the .NET applications and use Amazon ECS with AWS Fargate.