A solutions architect is planning to migrate critical Microsoft SQL Server databases to AWS. Because the databases are legacy systems, the solutions architect will move the databases to a modern data architecture. The solutions architect must migrate the databases with near-zero downtime.
Which solution will meet these requirements?
The appropriate solution for migrating Microsoft SQL Server databases to AWS with near-zero downtime is to use AWS Database Migration Service (AWS DMS). AWS DMS supports continuous data replication, capturing ongoing changes in the source database and applying them to the target, which ensures near real-time synchronization. AWS DMS can be configured to use Amazon S3 as an intermediary storage before loading the data into an Amazon RDS for Microsoft SQL Server DB instance. This choice supports the requirement of minimal downtime during the migration process.
C. The proper way is to use AWS DMS, but the answer here uses S3 (???) which will take forever. So the answer is C.
the following link maybe helpful for some; https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Target.S3.html#CHAP_Target.S3.Limitations
C https://aws.amazon.com/blogs/database/part-3-migrating-to-amazon-rds-for-sql-server-using-transactional-replication-with-native-backup-and-restore/
Native database high availability (HA) tools include the Always On or distributed availability group clusters in Microsoft SQL Server and Oracle’s Data Guard replications. This approach requires a major effort to set up across extended, cross-site HA clusters, and might cause some performance degradation because of the longer latency to achieve fully synchronous active/active deployments. However, this method provides the closest to near-zero downtime during the cutover.
A. Use AWS Application Migration Service and the AWS Schema Conversion Tool (AWS SCT). Perform an in-place upgrade before the migration. Export the migrated data to Amazon Aurora Serverless after cutover. Repoint the applications to Amazon Aurora. Here's why this approach offers the best advantages: Minimal downtime: In-place upgrade and cutover minimize downtime compared to traditional database migrations. Modernization: AWS Schema Conversion Tool helps modernize legacy schema structures during migration. Serverless architecture: Amazon Aurora Serverless simplifies management and scales effortlessly. Application compatibility: Repointing applications directly to Aurora minimizes disruption.
Agree with C; B was goo until it talked about S3 :(
Answer B.
b - always on feature
Both B and C are possible but I would go with DMS.
DMS should be the better service for this use case
AWS Application Migration Service (MGN) is a highly automated lift-and-shift (rehost) solution that simplifies the migration of applications to AWS. It supports near-zero downtime migrations by continuously replicating the source servers to AWS. Repointing the applications to Amazon Aurora Serverless satisfies the migration to the modern data architecture.
In option C - "Connect the source system to an Amazon RDS for Microsoft SQL Server DB instance", should be target, not source
Use AWS Database Migration Service (AWS DMS) to "rehost" the database???? How you can "rehost" database with DMS
Answer: C.
Why not A as the question the it should rearchitected from legacy
What is "native database high availability tools"????
B. Use AWS Database Migration Service (AWS DMS) to rehost the database. This action is not 'rehost'
C: Use distributed AG, it will work. https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/migrate-sql-server-to-aws-using-distributed-availability-groups.html