Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 148 discussion

Tricky one. This is not an on premise migration use case which prompts for answer C. Its a current situation of on premise application which the company wants to continue its state in the requirement of using AWS as DR solution. https://docs.aws.amazon.com/images/drs/latest/userguide/images/drs-failback-arc.png https://docs.aws.amazon.com/drs/latest/userguide/what-is-drs.html

https://docs.aws.amazon.com/drs/latest/userguide/what-is-drs.html https://docs.aws.amazon.com/drs/latest/userguide/recovery-workflow-gs.html Option C is wrong. That just mentions the migration method. I think this question asks us the DR architecture between on-premises and AWS cloud.

The answer should be C. Take note of the statement, "The application runs on physical servers that also run other applications". If you use the Application Migration Service, you will migrate these other applications, which have nothing to do with the application you are trying to protect.

A = to use AWS DRS you first need to set it up in each AWS Region in which you want to use it. installing AWS Replication agent is not enough B = correct (to me the sentence "Frequently perform failover and fallback from the most recent point in time" is ambiguous as this points to actual failover/failback and not to drills) C = SCT is not needed wwith same engine db migration. also, install the rest of the software is not enough for app DR D = Volume Gateway can be used in a Back and Restore DR scenario, but the option D is very confused. Anyway, Storage Gateway for DR requires more overhead with respect to AWS DRS

Option B is right option. Option C only addresses DB instance replication and DR, it does not meet requirements of replicating other applications running on on-premise.

Selected answer C changed from B The application runs on physical servers that also run other applications. The on-premises application that the company is planning to migrate uses a MySQL database as a data store.

Elastic Disaster Recovery does the job

C We are looking for a Business Continuity Solution Meaning RTO should be low

Answer is B. Questions mentions "least operational overhead" (efforts in the future), and B mentions "Frequently performing...". However, that is the best-practice for AWS DR (as misleading as it sounds): https://docs.aws.amazon.com/drs/latest/userguide/failback-overview.html

the question is a bit misleading, first part says "company is planning for business continuity" the later part of the sentence says "applications are migrating". nevertheless, we should focus on the word business continuity. Going by that "no migration" is required so choose B. that is my analysis.

B for BC

keyword = AWS Elastic Disaster Recovery B

The company is looking for a disaster recovery solution and not a full migration to cloud. In my view the answer should use Elastic Disaster Recovery and not DMS. References https://www.cloudthat.com/resources/blog/scalable-cost-effective-cloud-disaster-recovery-with-aws-drs-elastic-disaster-recovery https://catalog.us-east-1.prod.workshops.aws/workshops/080af3a5-623d-4147-934d-c8d17daba346/en-US/introduction https://docs.aws.amazon.com/pt_br/mgn/latest/ug/Network-Settings-Video.html

it appears that option C has the least operational overhead since it involves creating AWS DMS replication servers and a target Amazon Aurora MySQL DB cluster to host the database, creating a DMS replication task to copy existing data to the target DB cluster, creating a local AWS SCT CDC task to keep data synchronized, and installing the rest of the software on EC2 instances by starting with a compatible base AMI. The other options involve additional steps such as setting up replication for all servers (option A), initializing AWS Elastic Disaster Recovery and frequently performing failover and fallbacks (option B), or deploying an AWS Storage Gateway Volume Gateway and mounting volumes on all on-premises servers (option D).

C seems correct to me (DMS with SCT and CDC)

B has less operational overhead.

B, tricky