Q69 — AWS SAP-C02 Ch.1

Question 69 of 75 | ← Chapter 1

Q144. 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?

Correct Answer: C. Use native database high availability tools. Connect the source system to an Amazon RDS for Microsoft SQL Server DB instance. Configure replication accordingly. When data replication is finished, transition the workload to an Amazon RDS for Microsoft SQL Server DB instance

Explanation

Given the requirements for migrating critical Microsoft SQL Server databases to AWS with near-zero downtime, let's analyze each option: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:This option mentions using AWS Application Migration Service and AWS SCT, but AWS Application Migration Service primarily focuses on migrating applications and not specifically databases. AWS SCT can be used for schema conversion, but it's not directly involved in the migration process itself.Migrating to Amazon Aurora Serverless directly after an in-place upgrade and cutover may not guarantee near-zero downtime, as it involves a cutover point where the source database is stopped and the applications are repointed to the new Aurora instance.B. Use AWS Database Migration Service (AWS DMS) to rehost the database. Set Amazon S3 as a target. Set up change data capture (CDC) replication. When the source-and destination are fully synchronized, load the data from Amazon S3 into an Amazon RDS for Microsoft SQL Server DB instance:This option involves using AWS DMS, which is specifically designed for database migrations. However, storing the data in Amazon S3 as an intermediate step introduces complexity and doesn't directly address the need for near-zero downtime. Also, loading data from S3 to RDS for SQL Server doesn't guarantee seamless transition.C. Use native database high availability tools. Connect the source system to an Amazon RDS for Microsoft SQL Server DB instance. Configure replication accordingly. When data replication is finished, transition the workload to an Amazon RDS for Microsoft SQL Server DB instance:This option leverages native database replication capabilities (like SQL Server Always On Availability Groups or Transactional Replication) and combines it with Amazon RDS for Microsoft SQL Server. By setting up replication, the data is continuously synchronized between the source and the RDS instance.When the data replication is confirmed to be in sync, a seamless transition of the workload can be achieved with minimal downtime, as the applications can be repointed to the RDS instance without stopping the source database.D. Use AWS Application Migration Service. Rehost the database server on Amazon EC2. When data replication is finished, detach the database and move the database to an Amazon RDS for Microsoft SQL Server DB instance. Reattach the database and then cut over all networking:This option involves rehosting the database on EC2 first, which doesn't directly leverage AWS's managed database services for SQL Server. Moving a database between EC2 and RDS involves detaching and reattaching, which can be complex and doesn't necessarily guarantee near-zero downtime.Based on the requirements for migrating critical SQL Server databases with near-zero downtime, option C is the most suitable solution. It leverages native database replication capabilities with Amazon RDS for SQL Server, ensuring a seamless transition of the workload with minimal downtime.考虑到将关键的Microsoft SQL Server数据库迁移到AWS并实现近乎零停机的需求，让我们分析每个选项: A.使用AWS应用迁移服务和AWS架构转换工具(AWS SCT)。在迁移之前执行就地升级。在切换后将迁移的数据导出到Amazon Aurora Serverless。将应用程序重新指向Amazon Aurora: 此选项提到使用AWS应用程序迁移服务和AWS SCT，但AWS应用程序迁移服务主要关注迁移应用程序，而不是特定于数据库。AWS SCT可用于模式转换，但它并不直接参与迁移过程本身。在就地升级和切换后直接迁移到Amazon Aurora Serverless可能不能保证接近零停机时间，因为它涉及到一个切换点，源数据库停止，应用程序被重新指向新的Aurora实例。B.使用AWS数据库迁移服务(AWS DMS)重新托管数据库。将Amazon S3设置为目标。设置更改数据捕获(CDC)复制。当源端和目的端完全同步时，将Amazon S3中的数据加载到Microsoft SQL Server DB实例的Amazon RDS中: 这个选项涉及到使用AWS DMS，它是专门为数据库迁移而设计的。但是，将数据存储在Amazon S3中作为中间步骤会引入复杂性，并且不能直接满足接近零停机时间的需求。此外，将数据从S3加载到SQL Server的RDS并不能保证无缝转换。C.使用本地数据库高可用性工具。将源系统连接到Amazon RDS for Microsoft SQL Server DB实例。配置相应的复制。当数据复制完成后，将工作负载转移到Microsoft SQL Server DB实例的Amazon RDS: 该选项利用了本地数据库复制功能(如SQL Server Always On Availability Groups或事务性复制)，并将其与Microsoft SQL Server的Amazon RDS结合起来。通过设置复制，可以在源和RDS实例之间持续同步数据。当确认数据复制处于同步状态时，可以以最小的停机时间实现工作负载的无缝转换，因为可以将应用程序重新指向RDS实例，而无需停止源数据库。D.使用AWS应用迁移服务。在Amazon EC2上重新托管数据库服务器。当数据复制完成后，分离数据库并将数据库移动到Amazon RDS for Microsoft SQL Server DB实例。重新连接数据库，然后切断所有网络: 此选项涉及首先在EC2上重新托管数据库，这不会直接利用AWS的SQL Server托管数据库服务。在EC2和RDS之间移动数据库涉及分离和重新连接，这可能很复杂，并且不一定保证接近零停机时间。根据迁移关键SQL Server数据库的需求，几乎零停机时间，选项C是最合适的解决方案。它利用Amazon RDS for SQL Server的本地数据库复制功能，以最小的停机时间确保工作负载的无缝过渡。