Q57 — AWS SAP-C02 Ch.3

Question 57 of 75 | ← Chapter 3

Q282. A company is planning to migrate an Amazon RDS for Oracle database to an RDS for PostgreSQL DB instance in another AWS account. A solutions architect needs to design a migration strategy that will require no downtime and that will minimize the amount of time necessary to complete the migration. The migration strategy must replicate all existing data and any new data that is created during the migration. The target database must be identical to the source database at completion of the migration process. All applications currently use an Amazon Route 53 CNAME record as their endpoint for communication with the RDS for Oracle DB instance. The RDS for Oracle DB instance is in a private subnet. Which combination of steps should the solutions architect take to meet these requirements? (Select THREE)

Correct Answer: A. Create a new RDS for PostgreSQL DB instance in the target account. Use the AWS Schema Conversion Tool (AWS SCT) to migrate the database schema from the source database to the target database, C. Configure VPC peering between the VPCs in the two AWS accounts to provide connectivity to both DB instances from the target account. Configure the security groups that are attached to each DB instance to allow traffic on the database port from the VPC in the target account, E. Use AWS Database Migration Service (AWS DMS) in the target account to perform a full load plus change data capture (CDC) migration from the source database to the target database. When the migration is complete, change the CNAME record to point to the target DB instance endpoint.

Explanation

To migrate an Amazon RDS for Oracle database to an RDS for PostgreSQL DB instance in another AWS account without downtime and minimal time required, a solutions architect should take the following steps: Create a new RDS for PostgreSQL DB instance in the target account using option A or B, depending on whether the existing schema needs to be converted or not. Configure VPC peering between the VPCs in the two AWS accounts to provide connectivity to both DB instances from the target account. Configure the security groups that are attached to each DB instance to allow traffic on the database port from the VPC in the target account, as described in option C. Use AWS Database Migration Service (AWS DMS) in the target account to perform a full load plus change data capture (CDC) migration from the source database to the target database, as described in option E. When the migration is complete, change the CNAME record to point to the target DB instance endpoint. Therefore, options A, C, and E are the correct answers. Option D suggests temporarily allowing the source DB instance to be publicly accessible to provide connectivity from the VPC in the target account. This approach is less secure than using VPC peering and may introduce additional complexity due to managing public accessibility. Option F suggests using AWS Database Migration Service (AWS DMS) in the target account to perform a change data capture (CDC) migration from the source database to the target database. While this approach can work, it may not replicate all existing data and may require additional time to catch up with any new data that is created during the migration. Therefore, the most appropriate solution is to create a new RDS for PostgreSQL DB instance in the target account, configure VPC peering between the VPCs in the two AWS accounts, and use AWS Database Migration Service (AWS DMS) in the target account to perform a full load plus change data capture (CDC) migration from the source database to the target database