Exam AWS Certified Solutions Architect - Associate SAA-C02 topic 1 question 457 discussion

The answer is : A&C Turn off backups and transaction logging When migrating to an Amazon RDS database, it's a good idea to turn off backups and Multi-AZ on the target until you're ready to cut over. Similarly, when migrating to systems other than Amazon RDS, turning off any logging on the target until after cutover is usually a good idea. https://docs.aws.amazon.com/dms/latest/userguide/CHAP_BestPractices.html According to C - there is no service name DMS instance with transfer acceleration enabled

I believe the answers should be: A and C Why A and C? Turn off backups and transaction logging When migrating to an Amazon RDS database, it's a good idea to turn off backups and Multi-AZ on the target until you're ready to cut over. Similarly, when migrating to systems other than Amazon RDS, turning off any logging on the target until after cutover is usually a good idea. https://docs.aws.amazon.com/dms/latest/userguide/CHAP_BestPractices.html#CHAP_BestPractices.Performance Why not B? The questions establishes that "A solutions architect has decided to use an Amazon RDS for MySQL Multi-AZ DB instance that is deployed with 80,000 Provisioned IOPS for storage" Checking the AWS DMS replication instance for migration available from this link: https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.Types.html#CHAP_ReplicationInstance.Types.Deciding we can take dms.r5.24xlarge which can we give us a maximum of 80,000 IOPS based on this other link: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-optimized.html

You can increase the speed of an initial migration load by doing the following: If your target is an Amazon RDS DB instance, make sure that Multi-AZ isn't enabled for the target DB instance. Turn off any automatic backups or logging on the target database during the load, and turn back on those features after your migration is complete. If the feature is available on your target, use provisioned IOPS. If your migration data contains LOBs, make sure that the task is optimized for LOB migration. https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Troubleshooting.html#CHAP_Troubleshooting.General.SlowTask

Answer is A and C You can increase the speed of an initial migration load by doing the following: If your target is an Amazon RDS DB instance, make sure that Multi-AZ isn't enabled for the target DB instance. Turn off any automatic backups or logging on the target database during the load, and turn back on those features after your migration is complete. If the feature is available on your target, use provisioned IOPS. If your migration data contains LOBs, make sure that the task is optimized for LOB migration. For more information on optimizing for LOBs, see Target metadata task settings.

A and C

https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Troubleshooting.html#CHAP_Troubleshooting.General.SlowTask

A&C are correct

Answer is A, C Turn off backups and transaction logging When migrating to an Amazon RDS database, it's a good idea to turn off backups and Multi-AZ on the target until you're ready to cut over. Similarly, when migrating to systems other than Amazon RDS, turning off any logging on the target until after cutover is usually a good idea.

A and D for A https://docs.aws.amazon.com/dms/latest/userguide/CHAP_BestPractices.html#:~:text=When%20migrating%20to%20an%20Amazon%20RDS%20database%2C%20it%27s%20a%20good%20idea%20to%20turn%20off%20backups%20and%20Multi-AZ%20on%20the%20target%20until%20you%27re%20ready%20to%20cut%20over. for D https://aws.amazon.com/solutions/databasemigrations/database-migration-accelerator/ not C because it is valid if the target is not RDS.

the concern is bandwidth so A is not the answer. Multi-AZ load happens between database nodes not on-premises to Cloud. C, D

https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Troubleshooting.html

AB https://docs.aws.amazon.com/dms/latest/userguide/CHAP_BestPractices.html

A & C: "When migrating to Amazon RDS Instance, it is recommended to disable Backups and Transaction Logging onto Target data store until you are ready to cut over. Similarly, when migrating to non-Amazon RDS systems, disabling any logging on the target until after cut over is usually a good idea." https://www.linkedin.com/pulse/migrate-on-premises-rds-instance-amazon-using-data-bindlish-pmp-

AB A number of factors affect the performance of your AWS DMS migration: Resource availability on the source. The available network throughput. The resource capacity of the replication server. The ability of the target to ingest changes. The type and distribution of source data. The number of objects to be migrated.

Definitely 100% A&B. A is confirmed: With Amazon RDS databases, it's a good idea to turn off backups and Multi-AZ until the cutover. C is definitely out: While migrating to non-RDS systems, it's a good idea turn off any logging on the target until the cutover. (not a good idea to do this for RDS) https://docs.aws.amazon.com/dms/latest/userguide/CHAP_BestPractices.html#CHAP_BestPractices.ReducingLoad B is definitely the other solution. I've already checked it on the console. DMS uses ec2 instances --- you can choose how powerful you want them to be. So yeah : A&B. Final answer. No doubt.

A and B is correct https://docs.aws.amazon.com/dms/latest/userguide/CHAP_BestPractices.html#CHAP_BestPractices.Performance

Bandwidth utilization is the bottleneck here so we need to choose the action that will reduce the BW utilization. A - Would reduce the amount of data need to be transfered D - Would reduce the time the data takes to transfer