SAP-C02 · Question #611
A company has a legacy application that runs on multiple NET Framework components. The components share the same Microsoft SQL Server database and communicate with each other asynchronously by using…
The correct answer is D. Host the NET Core components on Amazon Elastic Container Service (Amazon ECS) with the. Amazon ECS with EC2 offers the needed control and orchestration capabilities. Amazon Aurora MySQL Serverless v2 can support the relational database model, though it requires adapting from Microsoft SQL Server to MySQL. Amazon SQS aligns well with the need for asynchronous…
Question
A company has a legacy application that runs on multiple NET Framework components. The components share the same Microsoft SQL Server database and communicate with each other asynchronously by using Microsoft Message Queueing (MSMQ). The company is starting a migration to containerized .NET Core components and wants to refactor the application to run on AWS. The .NET Core components require complex orchestration. The company must have full control over networking and host configuration. The application's database model is strongly relational. Which solution will meet these requirements?
Options
- AHost the INET Core components on AWS App Runner. Host the database on Amazon RDS for
- BHost the .NET Core components on Amazon Elastic Container Service (Amazon ECS) with the
- CHost the .NET Core components on AWS Elastic Beanstalk. Host the database on Amazon
- DHost the NET Core components on Amazon Elastic Container Service (Amazon ECS) with the
How the community answered
(15 responses)- A13% (2)
- B7% (1)
- C20% (3)
- D60% (9)
Explanation
Amazon ECS with EC2 offers the needed control and orchestration capabilities. Amazon Aurora MySQL Serverless v2 can support the relational database model, though it requires adapting from Microsoft SQL Server to MySQL. Amazon SQS aligns well with the need for asynchronous messaging and can be a suitable replacement for MSMQ.
Community Discussion
No community discussion yet for this question.