Migrate .NET Framework applications to Elastic Beanstalk with the Web Application Migration Assistant

SAP-C02 By islever Editorial Last updated

Determine the optimal migration approach for existing workloads. Determine a new architecture for existing workloads.

Short answer

B Use the Windows Web Application Migration Assistant to move the applications to Elastic Beanstalk, which handles deployment and infrastructure management.

Question

A company needs to migrate 60 on-premises legacy applications to AWS. The applications are based on the NET Framework and run on Windows. The company needs a solution that minimizes migration time and requires no application code changes. The company also does not want to manage the infrastructure. Which solution will meet these requirements?
  1. Refactor the applications and containerize them by using AWS Toolkit for NET Refactoring. Use Amazon Elastic Container Service (Amazon ECS) with the Fargate launch type to host the containerized applications.
  2. Use the Windows Web Application Migration Assistant to migrate the applications to AWS Elastic Beanstalk. Use Elastic Beanstalk to deploy and manage the applications. Correct Answer
  3. Use the Windows Web Application Migration Assistant to migrate the applications to Amazon EC2 instances. Use the EC2 instances to deploy and manage the applications.
  4. Refactor the applications and containerize them by using AWS Toolkit for NET Refactoring. Use Amazon Elastic Kubernetes Service (Amazon EKS) with the Fargate launch type to host the containerized applications.

Key Takeaways

The Windows Web Application Migration Assistant automates the lift-and-shift move, and Elastic Beanstalk is the only option in the list that also removes infrastructure management, which is the second half of the requirement.

Sixty on-premises .NET Framework applications on Windows must move to AWS with minimal migration time, no code changes, and no infrastructure management by the company. Refactoring-based options change the application code, which is explicitly disallowed.

Common mistake: Stopping at the tool choice and picking a refactoring option. AWS Toolkit for .NET Refactoring does containerize .NET applications, but it requires rewriting application code, which violates the no-code-changes requirement.

Expert Analysis

Why the Answer Is Correct

The Windows Web Application Migration Assistant automates packaging and moving.NET Framework applications, and Elastic Beanstalk provisions, deploys, scales, load balances, and patches the underlying infrastructure. Together they satisfy minimal migration time, no code changes, and no infrastructure management, and Elastic Beanstalk supports any.NET application running on Windows Server.

Why the Other Options Are Wrong

A and D: AWS Toolkit for.NET Refactoring requires refactoring the application source, which contradicts the no-code-changes requirement, and hosting on ECS or EKS Fargate adds cluster operations the company does not want. C: Migrating to EC2 instances moves the application but leaves the company responsible for patching, scaling, and load balancing, so infrastructure is still managed internally.

Community Comment Notes

The community voted 81 to 19 for B, and the two dissenting A votes were answered by the simplest observation: refactoring is a code change, which the question forbids.

Official Reference

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/dotnet-getstarted.html

This link opens the official vendor documentation in a new tab.

Community Votes

B
81%
A
19%

81% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 12 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 12

  1. 0b43291 👍 2 Answered B
    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.
  2. pangchn 👍 2 Answered B
    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
  3. Dgix 👍 2 Answered B
    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.
  4. ovladan 👍 2
    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.
  5. titi_r 👍 2 Answered B
    Getting started with Windows .NET on Elastic Beanstalk https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/dotnet-getstarted.html
Show 7 more comments
  1. VerRi 👍 2 Answered B
    This is a typical Beanstalk feature. Refactoring and containerizing applications often involve some level of code change.
  2. AzureDP900 👍 1
    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.
  3. JoeTromundo 👍 1 Answered B
    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.
  4. CMMC 👍 1 Answered A
    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.
  5. AwsZora 👍 1 Answered A
    No, AWS Elastic Beanstalk is not a serverless platform.
  6. yog927 👍 1 Answered A
    A Not B as company does not want to manage the infra.
  7. asquared16 👍 2 Answered B
    Refactoring = Code Change

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Modernize centralized firewall appliances with a Gateway Load Balancer and Auto Scaling

S-grade

Use Lambda over a CloudWatch Logs stream to count unique users per client

S-grade

Serve global game assets with Route 53 latency records and health checks

S-grade

Reach a cross-account S3 data lake through a gateway endpoint and an access point bucket policy

S-grade

Practice All SAP-C02 Questions

Access 85 questions with complete answers and detailed explanations.

View Full SAP-C02 Practice Test →

← Back to SAP-C02 Study Guide