AWS Certified Solutions Architect Professional SAP-C02 Practice Question

The correct approach involves using the AWS Schema Conversion Tool (SCT) and AWS Database Migration Service (DMS) together, as they are designed for this specific type of heterogeneous migration. First, SCT should be used to analyze the source Oracle schema and code. SCT generates a database migration assessment report that details which objects can be automatically converted and which require manual intervention, directly addressing the requirement for a pre-migration analysis. Second, SCT is used to convert the compatible schema objects and code to a format suitable for Aurora PostgreSQL. Finally, to meet the minimal downtime requirement, AWS DMS is used to perform a full data load and then continuously replicate changes from the source Oracle database to the target Aurora database using Change Data Capture (CDC). This allows the source application to remain fully operational during the migration, with a very short cutover window.

Incorrect options:

• Using only DMS is incorrect because DMS is a data replication service and does not convert database schema code like stored procedures or packages. The manual rewrite of code would be inefficient and risky without the initial assessment from SCT.
• Reversing the roles of DMS and SCT is incorrect. SCT is for schema/code assessment and conversion, not data replication. DMS is for data replication and does not provide the detailed code-level assessment reports that SCT does.
• Using AWS Snowball Edge is not optimal for this scenario. While Snowball can be used for the initial load of very large datasets to reduce network transfer time, it is a data transport solution, not a live migration tool. It does not address the critical requirement of converting the proprietary Oracle PL/SQL code, nor does it inherently provide a minimal downtime solution without being paired correctly with DMS for ongoing replication.