Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 455 discussion

Beanstalk simplifies the process but it still requires managing infrastructure. While Beanstalk automatically handles many infrastructure tasks, it still involves creating and managing environments, deploying applications, and configuring various setting. I would vote for A

By using the Windows Web Application Migration Assistant and AWS Elastic Beanstalk, the company can migrate their .NET applications to AWS with minimal migration time, no code changes, and without the need to manage the underlying infrastructure, meeting all the stated requirements. The other options have limitations or do not fully meet the requirements: Options A and D (containerization with ECS or EKS) would require refactoring the applications, which goes against the requirement of avoiding code changes. Additionally, these options would require more infrastructure management compared to Elastic Beanstalk. Option C (migration to EC2 instances) would require the company to manage the EC2 instances, configure networking, load balancing, and auto-scaling, which contradicts the requirement of not managing the infrastructure.

Option B uses the Windows Web Application Migration Assistant, a tool specifically designed for .NET Framework-based applications on Windows. It helps migrate these applications to AWS Elastic Beanstalk without requiring code changes or manual infrastructure management. Elastic Beanstalk then takes care of deploying and managing the applications, meeting the company's requirements. This approach ensures a smooth migration with minimal disruption, while also avoiding any significant changes to the application code or infrastructure management responsibilities.

Elastic Beanstalk abstracts the infrastructure, so the company won’t need to manage EC2 instances, scaling, load balancing, or patching. Elastic Beanstalk takes care of these tasks automatically, which fits the requirement of not managing infrastructure. This is not the same thing as serverless (which is NOT a requirement), as Zas1 commented. The answer can't be A because refactoring=code change, as asquared16 have already commented.

Refactoring = Code Change

Getting started with Windows .NET on Elastic Beanstalk https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/dotnet-getstarted.html

No, AWS Elastic Beanstalk is not a serverless platform.

This is a typical Beanstalk feature.  Refactoring and containerizing applications often involve some level of code change.

I vote for B when googling Windows Web Application Migration Assistant, all top 3 are using EB. https://github.com/awslabs/windows-web-app-migration-assistant Compare to EC2 in C, the question mentioned do not manage infrastructure See below wording With Elastic Beanstalk, you can quickly deploy and manage applications in the AWS Cloud without having to learn about the infrastructure that runs those applications https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/Welcome.html

A Not B as company does not want to manage the infra.

Correct answer is B, use Beanstalk. It's a classic use for Beanstalk: remember - no application changes is a requirement. A involves quite a bit of work and application changes. AWS Toolkit for .NET is a help, but there's operational overhead. Also, moving to ECS Fargate, serverless as it is, requires containerising the application, which also adds overhead.

Refactoring the applications and containerizing them using AWS Toolkit for .NET Refactoring allows for easy migration without needing to modify application code. Using Amazon ECS with the Fargate launch type is optimized for running containers (when comparing to #D) and allows the provisioning and scaling of containers. #A provides a streamlined migration process with minimal management overhead.

Solution: B If you look at the request "Company needs a solution that minimizes migration time and requires no changes to application code," you can eliminate the answer under A & D (refactoring suggested). The answers under B & C are fine, but the "minimize migration time" part, the better solution is under B.