SAP-C02 · Question #351
A Solutions Architect is building a containerized .NET Core application that will run in AWS Fargate. The backend of the application requires Microsoft SQL Server with high availability. All tiers…
The correct answer is B. Create a Multi-AZ deployment of SQL Server on Amazon RDS. Create a secret in AWS Secrets. Secrets Manager natively supports SQL Server on RDS. No real need to create additional 'ephemeral storage' to fetch credentials, as these can be injected to containers as environment https://aws.amazon.com/premiumsupport/knowledge-center/ecs-data-security-container-task/
Question
A Solutions Architect is building a containerized .NET Core application that will run in AWS Fargate. The backend of the application requires Microsoft SQL Server with high availability. All tiers of the application must be highly available. The credentials used for the connection string to SQL Server should not be stored on disk within the .NET Core front-end containers. Which strategies should the Solutions Architect use to meet these requirements?
Options
- ASet up SQL Server to run in Fargate with Service Auto Scaling. Create an Amazon ECS task
- BCreate a Multi-AZ deployment of SQL Server on Amazon RDS. Create a secret in AWS Secrets
- CCreate an Auto Scaling group to run SQL Server on Amazon EC2. Create a secret in AWS
- DCreate a Multi-AZ deployment of SQL Server on Amazon RDS. Create a secret in AWS Secrets
How the community answered
(16 responses)- A13% (2)
- B63% (10)
- C19% (3)
- D6% (1)
Explanation
Secrets Manager natively supports SQL Server on RDS. No real need to create additional 'ephemeral storage' to fetch credentials, as these can be injected to containers as environment https://aws.amazon.com/premiumsupport/knowledge-center/ecs-data-security-container-task/
Community Discussion
No community discussion yet for this question.