A company must migrate an Amazon RDS for Oracle database to an RDS for PostgreSQL instance in a different AWS account with zero downtime and minimal migration cutover time. The migration must replicate all existing data and any new data created during migration, and the target must be identical to the source at completion. Applications use a Route 53 CNAME for the RDS for Oracle endpoint. The source DB is in a private subnet. Which combination of steps should the solutions architect take? (Choose three.)

To achieve zero downtime and minimal cutover for a cross-account, heterogeneous database migration, a multi-step approach is necessary. First, creating the target RDS for PostgreSQL instance in the target account and using AWS SCT to migrate the schema is crucial. SCT handles the conversion of Oracle-specific schema objects to PostgreSQL-compatible formats. Second, since the source DB is in a private subnet and the migration is cross-account, VPC peering between the two accounts is required to establish secure network connectivity, along with appropriate security group adjustments. Finally, AWS DMS is the ideal service for replicating data. Running DMS in the target account with a full load plus change data capture (CDC) ensures all existing data is migrated and any new transactions during the migration period are continuously replicated, enabling a seamless cutover by updating the Route 53 CNAME. Incorrect options: Using SCT to create the DB instance and include initial data is not its primary function; SCT is for schema conversion. DMS handles data migration. Temporarily making the source DB publicly accessible is a security risk and unnecessary with VPC peering. Running DMS with only CDC would miss the initial dataset, leading to an incomplete migration.