A legacy on-premises .NET application (load-balanced web tier, load-balanced application tier, and Microsoft SQL Server database) is being migrated to AWS. The company prefers managed services and does not want to rewrite the application. The solutions architect must eliminate scaling issues while minimizing licensing costs as the application scales. Which option is the most cost-effective solution that meets these goals?

This option is correct because it uses managed services (ALB, Auto Scaling, Aurora PostgreSQL) and avoids rewriting the application, aligning with the company's preferences. Aurora PostgreSQL with Babelfish allows the existing SQL Server protocol and queries to work without extensive code changes, minimizing replatforming effort and licensing costs compared to SQL Server. Auto Scaling groups address scaling issues effectively. The incorrect options are: Using AWS DMS to create images and then deploying to EC2 with NLBs for web/app tiers, and DynamoDB for the database, is problematic. AWS DMS is for database migration, not server imaging. DynamoDB is a NoSQL database and would require significant application rewrites for a SQL Server application. NLBs are layer 4 and less suitable for HTTP/HTTPS traffic than ALBs. Containerizing with EKS and RDS for SQL Server is a viable option for modernization, but RDS for SQL Server still incurs SQL Server licensing costs, which the question aims to minimize. Refactoring to Lambda, API Gateway, S3, and Athena involves a complete rewrite of the application, which the company explicitly wants to avoid.