Migrating SQL Server to AWS with Reduced Overhead
Short answer
B Migrate the databases to a Multi-AZ Amazon RDS for SQL Server DB instance and use an AWS Key Management Service (AWS KMS) AWS managed key for encryption.
Question
Key Takeaways
The core concept is leveraging managed services (RDS) to offload administrative tasks like patching and backups, contrasting with self-managed EC2 instances.
This question evaluates the selection of a managed database service that reduces operational overhead while maintaining relational capabilities and security. The correct solution utilizes Amazon RDS for SQL Server with Multi-AZ deployment and KMS encryption.
Common mistake: Learners often incorrectly choose Amazon EC2 (Option A) because they underestimate the significant operational overhead associated with managing databases on raw compute resources compared to managed services.
Expert Analysis
Why the Answer Is Correct
Amazon Relational Database Service (RDS) is a managed service that automates tedious administrative tasks such as provisioning, patching, backup, recovery, failure detection, and repair. By migrating to Amazon RDS for SQL Server with Multi-AZ deployment, the company achieves high availability and fault tolerance automatically. Using an AWS KMS managed key ensures data is encrypted at rest without requiring manual key management, directly addressing the requirements to increase security and reduce operational overhead.
Why the Other Options Are Wrong
Option A uses Amazon EC2, which requires the user to manage the operating system, database software, patches, and backups, resulting in high operational overhead rather than reduced. Option C suggests migrating to Amazon S3 and using Macie; however, S3 is object storage, not suitable for replacing a relational SQL Server database that requires transactional integrity and complex queries. Option D proposes Amazon DynamoDB, which is a NoSQL database incompatible with existing SQL Server applications without significant code refactoring, and CloudWatch Logs are for monitoring, not primary data security/encryption.
Community Comment Notes
Community consensus strongly supports Option B. Users noted that this option provides the best balance between increased security, reduced operational overhead, and maintaining relational functionalities. One commenter highlighted that DynamoDB is NoSQL and thus inappropriate for direct migration from SQL Server. Another user confirmed that the managed nature of RDS is key to reducing overhead compared to EC2.
Exam Strategy
When a question emphasizes 'reducing operational overhead' or 'managed service,' always prioritize AWS PaaS offerings (like RDS, ElastiCache, Lambda) over IaaS options (like EC2). Look for keywords indicating the need to maintain specific database engines or compatibility.
Frequently Asked Questions
Why not use EC2 with KMS for encryption?
Can we migrate SQL Server to DynamoDB directly?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 4 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 4
-
trinh_le 👍 6 Answered BMigrate the databases to a Multi-AZ Amazon RDS for SQL Server DB instance. Use an AWS Key Management Service (AWS KMS) AWS managed key for encryption.
-
Seb888 👍 4 Answered BB. Migrate the databases to a Multi-AZ Amazon RDS for SQL Server DB instance. Use an AWS Key Management Service (AWS KMS) AWS managed key for encryption. This option provides the best balance between increased security, reduced operational overhead, and maintaining the relational database functionalities that the company needs.
-
muhammadahmer36 👍 2 Answered BB. Migrate the databases to a Multi-AZ Amazon RDS for SQL Server DB instance. Use an AWS Key Management Service (AWS KMS) AWS managed key for encryption.
-
mk168898 👍 2looking to migrate SQL server isntance. D is wrong because dynamoDB is noSQL
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SAA-C03 Questions
Access 120 questions with complete answers and detailed explanations.
View Full SAA-C03 Practice Test →