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:
The AWS Schema Conversion Tool (AWS SCT) is used to convert database schemas from one database engine to another. In this case, it’s used to convert the Oracle schema to PostgreSQL. Creating the target RDS for PostgreSQL instance first is a prerequisite for using SCT.
AWS SCT is used for schema conversion, not for creating the target database instance with initial data. Creating the target database is a separate step that must be done before using SCT. SCT helps migrate the schema, not the data itself directly into a new instance creation process.
VPC peering provides the necessary network connectivity between the source and target VPCs, allowing DMS to access the source database. Configuring security groups to allow traffic on the database port is essential for secure communication between the DMS replication instance and both the source and target databases. This avoids transferring data over the internet.
Making the source DB instance publicly accessible is a major security risk and violates the requirement of not transferring data over the internet. This approach should be avoided. VPC peering or other private connectivity methods should be used instead.
AWS DMS is the correct tool for migrating databases with minimal downtime. Using full load plus change data capture (CDC) ensures that all existing data is migrated and that any changes made to the source database during the migration are also replicated to the target database. Changing the CNAME record at the end performs the cutover with minimal downtime.
Using only CDC for the migration is incorrect. CDC captures changes madeafterthe migration process starts. It does not migrate the initial bulk of existing data. A full load is required to migrate the initial data before CDC can capture ongoing changes.
I rate 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.
As far as I can tell, 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.