AWS Certified Solutions Architect - Professional SAP-C02 Exam QuestionsBrowse all questions from this exam

AWS Certified Solutions Architect - Professional SAP-C02 Exam - Question 229


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?

Show Answer
Correct Answer: B

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.

Discussion

34 comments
Sign in to comment
SmileyCloudOption: C
Jun 23, 2023

C. The proper way is to use AWS DMS, but the answer here uses S3 (???) which will take forever. So the answer is C.

yorkicurke
Nov 2, 2023

the following link maybe helpful for some; https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Target.S3.html#CHAP_Target.S3.Limitations

Ganshank
Aug 27, 2023

C https://aws.amazon.com/blogs/database/part-3-migrating-to-amazon-rds-for-sql-server-using-transactional-replication-with-native-backup-and-restore/

Arnaud92Option: B
Jul 25, 2023

Correct B Always On Availability Groups (AG) cannot be used between an on-premise SQL Server database and Amazon RDS for SQL Server on AWS. Always On Availability Groups is a feature specific to SQL Server Enterprise Edition and requires Windows Failover Clustering-based network connectivity. Amazon RDS for SQL Server supports both Standard and Enterprise editions of SQL Server, but it does not support the cluster failover features required for Always On Availability Groups. So only DMS is the correct answer

nexus2020Option: C
Jun 22, 2023

Native Database High Availability Tools: AWS provides native high availability tools for Microsoft SQL Server, such as database mirroring, Always On Availability Groups, and transactional replication. These tools are designed to minimize downtime during the migration process and ensure data consistency and integrity.

longngo0924Option: B
Aug 15, 2023

Correct answer is B. https://repost.aws/questions/QUw-bHxHYITuC3IqDwgyx6fw/is-it-possible-to-use-aws-rds-sql-server-as-an-aag-target-from-on-premise-primary

billtranOption: B
Aug 25, 2023

Only B can do it. https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Target.S3.html https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_PostgreSQL.S3Import.html

ayadmawlaOption: C
Dec 6, 2023

Agree with C; B was goo until it talked about S3 :(

duriselvan
Dec 13, 2023

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.

JOKERO
Mar 15, 2024

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.

0b43291Option: C
Nov 20, 2024

By using native database high availability tools and replication methods, you can achieve near-zero downtime during the migration process. The other options may not provide the same level of seamless data replication and minimal downtime as the native SQL Server replication tools. Option 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. While AWS DMS can be used for migrations, it introduces additional complexity compared to native SQL Server replication tools. Staging data in Amazon S3 and then loading into the target RDS instance can cause downtime during the final cutover. Native replication tools can directly replicate data to the target RDS instance without an intermediate storage solution.

career360guruOption: B
Nov 24, 2023

Both B and C are possible but I would go with DMS.

geekgirl007Option: B
Nov 27, 2023

b - always on feature

shaaam80Option: B
Nov 30, 2023

Answer B.

easytoo
Jun 23, 2023

c-c-c-c-c-c Microsoft SQL Server provides native high availability tools such as Always On Availability Groups or database mirroring. These tools enable real-time data replication and failover capabilities, allowing for minimal downtime during the migration process.

Bengi
Jul 18, 2023

B - Refer to https://docs.aws.amazon.com/dms/latest/sbs/chap-manageddatabases.sqlserveralwayson.html

BrijMohan08Option: A
May 1, 2024

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.

michele_scarOption: B
May 25, 2024

DMS should be the better service for this use case

grandcanyonOption: B
Jul 6, 2024

In option C - "Connect the source system to an Amazon RDS for Microsoft SQL Server DB instance", should be target, not source

gd1
Jun 24, 2023

GPT 4.0 is B

Jackhemo
Jun 25, 2023

Olabiba says "C"...so it is C.

NikkyDickyOption: C
Jul 6, 2023

C for no downtime

ggrodskiy
Jul 23, 2023

Correct B.

rxhan
Jul 29, 2023

RDS SQL Server is a managed service, so it will not be possible to add RDS Instance as an extension node to your on-premise primary instance. However, you can connect directly from your on-premise App to hosted RDS SQL Server instance in AWS. Alternatively, if you need RDS as a DR node for your on-premises primary, you can use an option like DMS (Database Migration Service) to set up on-going replication to RDS.

PhilTheAnimal
Aug 8, 2023

So what is your answer then ?

duriselvan
Sep 23, 2023

In this post, we showed you how to configure transactional replication with native backup and restore that replicates data from an on-premises SQL Server or SQL Server on an EC2 instance. You can use this strategy to migrate your large mission-critical workloads to an RDS for SQL Server instance with minimal to near-zero downtime. C ans

severlightOption: C
Nov 18, 2023

C. https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-sql-server/always-on.html

adelynllllllllll
Jan 2, 2024

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

tmlong18Option: C
Jan 17, 2024

B. Use AWS Database Migration Service (AWS DMS) to rehost the database. This action is not 'rehost'

ftaws
Jan 22, 2024

What is "native database high availability tools"????

svenkata18
Mar 31, 2024

Why not A as the question the it should rearchitected from legacy

titi_rOption: C
May 9, 2024

Answer: C.

trungtdOption: C
Jun 11, 2024

Use AWS Database Migration Service (AWS DMS) to "rehost" the database???? How you can "rehost" database with DMS

CAIYasiaOption: C
Jul 24, 2024

C. Correct, Near-Zero Downtime. A. In-Place Upgrade and Migration to Aurora: This involves multiple steps and the potential for increased downtime during the cutover process. Schema Conversion: Depending on the complexity of the legacy system, converting schemas and ensuring compatibility with Amazon Aurora can be challenging and time-consuming. B. Intermediate Storage in Amazon S3: Adds complexity Two-Step Process: First replicating to Amazon S3 and then loading into Amazon RDS adds additional steps and potential points of failure.

8693a49Option: B
Aug 1, 2024

B is the AWS way of doing a DB migration. C might work and could be better in some cases, but because the DBs are legacy you might run into compatibility issues or limitations with the tooling. If the databases are very large you really want to use B because you need to ship the bulk of the data with Snowball.

jefnmet
Aug 15, 2024

B look correct to me

helloworldabc
Aug 24, 2024

just C