Which combination of steps should the solutions architect take to meet these requirements?
(Choose three.)
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.
Use the AWS Schema Conversion Tool (AWS SCT) to create a new RDS for PostgreSQL DB instance in the target account with the schema and initial data from the source database.
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.
Temporarily allow the source DB instance to be publicly accessible to provide connectivity from the VPC in 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.
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.
Use 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. When the migration is complete, change the CNAME record to point to the target DB instance endpoint.
Explanations:
This step is necessary to set up the target PostgreSQL database with the appropriate schema. AWS Schema Conversion Tool (SCT) can migrate the schema from Oracle to PostgreSQL, which is required as the target database must match the source schema.
AWS SCT is used for schema conversion only, not for migrating both schema and initial data. A new RDS instance must be created separately, and DMS will handle data migration rather than relying on AWS SCT alone.
VPC peering allows secure network connectivity between the source and target RDS instances across AWS accounts, which is essential for continuous data replication during migration.
Making the source database publicly accessible is unnecessary and can increase security risks. VPC peering with proper security group configuration is the correct method for secure cross-account connectivity.
AWS DMS with full load plus change data capture (CDC) is the correct method to migrate both initial and ongoing changes with no downtime. Updating the Route 53 CNAME after migration ensures the applications connect to the new database seamlessly.
Using only CDC with DMS will not migrate the existing data. Both a full load and CDC are required to replicate the entire database and ongoing changes from Oracle to PostgreSQL.
I judge that the answer is:
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.