Migrate .NET Framework 4.7 with COM+ Using Windows Containers on ECS
A company is migrating a legacy .NET Framework 4.7 application to AWS. The application uses Windows authentication and COM+ components. Which migration approach is most suitable?
Quick Answer
The answer is to use Windows containers on Amazon ECS with the ECS-optimized Windows Server AMI, because this is the only approach that fully supports .NET Framework 4.7 applications with COM+ components and Windows authentication. Windows containers on ECS run on Windows Server Core, which provides the necessary Windows kernel and COM+ infrastructure that Linux containers and serverless options lack. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this question tests your understanding of the hard boundary between .NET Framework (Windows-only) and .NET Core/.NET 5+ (cross-platform), and it often appears as a distractor where candidates mistakenly choose Elastic Beanstalk or Lambda. A common trap is assuming that any "container" solution works, but Linux containers cannot host COM+ or full .NET Framework. Memory tip: "COM+ means Windows+ — never try to run legacy COM on Linux."
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Windows containers on Amazon ECS with Amazon ECS-optimized Windows Server AMI
Windows containers on Amazon ECS with the ECS-optimized Windows Server AMI support .NET Framework applications and COM+ components, making them the most suitable migration approach. Option A is incorrect because replatforming to .NET Core on Linux would require significant code changes and does not support COM+. Option C is incorrect because AWS Lambda does not support full .NET Framework or COM+. Option D is incorrect because Linux containers cannot run Windows-based .NET Framework applications.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Replatform to .NET Core on AWS Elastic Beanstalk (Linux)
Why it's wrong here
.NET Core on Linux cannot host COM+ components or Windows authentication, both of which the application depends on. Replatforming to .NET Core is tempting because it modernises code with minimal changes, and would be right for a portable ASP.NET application without COM+ dependencies, but here it breaks required Windows-only runtime features.
- ✓
Use Windows containers on Amazon ECS with Amazon ECS-optimized Windows Server AMI
Why this is correct
Windows containers on Amazon ECS with the ECS-optimised Windows Server AMI preserve .NET Framework 4.7, Windows authentication and COM+ registration, which Linux containers cannot host. This satisfies the constraint of running COM+ components without rewriting the application.
- ✗
Refactor to run on AWS Lambda with .NET Core 3.1
Why it's wrong here
Lambda's execution model cannot host COM+ components or Windows authentication, and .NET Core 3.1 lacks COM+ support entirely. Refactoring to Lambda is tempting because it removes server management for event-driven workloads, and would suit a stateless .NET Core API, but this legacy application's Windows dependencies make it unworkable.
- ✗
Containerize with Linux containers on Amazon ECS
Why it's wrong here
Linux containers cannot run COM+ components or Windows authentication, which the application requires. Containerising on ECS is tempting because it modernises deployment and scaling, and would be correct for a portable .NET Core service, but the Windows-only COM+ and authentication dependencies demand Windows containers on Amazon ECS or EC2.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
About these practice questions
Courseiva writes every SAP-C02 question from scratch — 984 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on SAP-C02
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company is migrating a legacy .NET Framework 4.8 application to AWS. The application uses Windows authentication integrated with Active Directory and relies on a shared file system for configuration files. The company wants to minimize operational overhead and use managed services. Which combination of AWS services should the company use to modernize the application?
hard- A.AWS Managed Microsoft AD, Amazon EFS, and AWS Elastic Beanstalk for .NET on Windows
- B.Amazon Cognito, Amazon RDS for SQL Server, and AWS Lambda
- C.AWS Directory Service for Microsoft AD, Amazon S3, and AWS App Runner
- ✓ D.AWS Managed Microsoft AD, Amazon FSx for Windows File Server, and AWS Elastic Beanstalk for .NET on Windows
Why D: AWS Managed Microsoft AD provides Windows authentication integrated with Active Directory, FSx for Windows File Server provides a managed shared file system that supports Windows-native SMB protocol and NTFS permissions, and AWS Elastic Beanstalk for .NET on Windows minimizes operational overhead for hosting a .NET Framework 4.8 application. Option A (EFS) does not natively support Windows authentication or SMB protocol, making it unsuitable. Option B (RDS for SQL Server) is unnecessary as the application does not require a database. Option C (App Runner) does not support .NET Framework applications, and S3 cannot function as a Windows shared file system.
Variation 2. A company is migrating a .NET application from Windows Server to Linux on EC2. The application uses a proprietary COM+ component that cannot be recompiled. Which migration path should they take?
medium- A.Rehost the application on Linux EC2 using Wine
- ✓ B.Rehost the application on Windows Server EC2 instances
- C.Refactor the COM+ component to a REST API
- D.Replatform the application to .NET Core and run on Linux
Why B: The application uses a proprietary COM+ component that cannot be recompiled, and COM+ is a Windows-specific technology. Therefore, the only viable migration path is to rehost the application on Windows Server EC2 instances, where COM+ is natively supported. Migrating to Linux would require recompilation or emulation, which is not feasible for a proprietary component.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAP-C02 exam.