Migrate to RDS PostgreSQL and reach the retained Oracle databases over Direct Connect

Answer Correct answer: D — Migrate with SCT and DMS to RDS PostgreSQL, use its native spatial support, run cron on the instance, and reach on-premises Oracle over Direct Connect.

A company needs to move some on-premises Oracle databases to AWS. The company has chosen to keep some of the databases on premises for business compliance reasons. The on-premises databases contain spatial data and run cron jobs for maintenance. The company needs to connect to the on-premises systems directly from AWS to query data as a foreign table. Which solution will meet these requirements?

  1. Create Amazon DynamoDB global tables with auto scaling enabled. Use the AWS Schema Conversion Tool (AWS SCT) and AWS Database Migration Service (AWS DMS) to move the data from on premises to DynamoDB. Create an AWS Lambda function to move the spatial data to Amazon S3. Query the data by using Amazon Athena. Use Amazon EventBridge to schedule jobs in DynamoDB for maintenance. Use Amazon API Gateway for foreign table support.
  2. Create an Amazon RDS for Microsoft SQL Server DB instance. Use native replication to move the data from on premises to the DB instance. Use the AWS Schema Conversion Tool (AWS SCT) to modify the SQL Server schema as needed after replication. Move the spatial data to Amazon Redshift. Use stored procedures for system maintenance. Create AWS Glue crawlers to connect to the on-premises Oracle databases for foreign table support.
  3. Launch Amazon EC2 instances to host the Oracle databases. Place the EC2 instances in an Auto Scaling group. Use AWS Application Migration Service to move the data from on premises to the EC2 instances and for real-time bidirectional change data capture (CDC) synchronization. Use Oracle native spatial data support. Create an AWS Lambda function to run maintenance jobs as part of an AWS Step Functions workflow. Create an internet gateway for foreign table support.
  4. Create an Amazon RDS for PostgreSQL DB instance. Use the AWS Schema Conversion Tool (AWS SCT) and AWS Database Migration Service (AWS DMS) to move the data from on premises to the DB instance. Use PostgreSQL native spatial data support. Run cron jobs on the DB instance for maintenance. Use AWS Direct Connect to connect the DB instance to the on-premises environment for foreign table support. Correct Answer

Community Votes

D
100%

100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

Direct Connect gives the RDS PostgreSQL instance a private network path to the on-premises environment, which is what makes a foreign table pointing at the on-premises Oracle source possible, and PostgreSQL handles the Oracle spatial types through its own native spatial support after schema conversion.

A company is moving some on-premises Oracle databases to AWS while keeping others on premises for compliance. The source data includes spatial data and the on-premises systems run cron maintenance jobs. AWS must query the retained on-premises databases directly as a foreign table.

Attempting foreign table access over the public internet with an internet gateway. The on-premises database is not internet-facing, and the requirement is to connect directly to the on-premises systems, so a private dedicated connection is required rather than exposing either side to the internet.

Community Discussion (6 comments)

JoeTromundo 👍 4 Selected: D
PostgreSQL natively supports spatial data through the PostGIS extension. This makes it well-suited for handling spatial data from the Oracle databases. AWS Schema Conversion Tool (SCT) and AWS Database Migration Service (DMS) are both effective tools for migrating schema and data from Oracle to Amazon RDS for PostgreSQL, ensuring minimal disruption during the migration process. Amazon RDS for PostgreSQL allows the use of cron jobs directly on the instance through extensions like pg_cron for scheduling maintenance tasks. AWS Direct Connect provides a dedicated, secure connection between the on-premises systems and the AWS environment. This low-latency link will allow querying data from on-premises Oracle databases as foreign tables in the PostgreSQL instance without going through the internet, which supports compliance and performance needs.
neta1o 👍 2 Selected: D
I didn't realize SCT could convert from Oracle to things like Aurora MySQL and PostgreSQL. But since that is true and a direct connect also makes sense, I'd go D. https://aws.amazon.com/dms/schema-conversion-tool/
Helpnosense 👍 2 Selected: D
It's Data Migration Service that provides real-time bidirectional change data capture (CDC) synchronization
goldeneye 👍 3 Selected: D
Option D is the most appropriate because it leverages AWS services effectively to migrate and manage the databases while ensuring compatibility with spatial data types and maintaining connectivity for querying on-premises data.
goldeneye 👍 2
Option D is the most appropriate because it leverages AWS services effectively to migrate and manage the databases while ensuring compatibility with spatial data types and maintaining connectivity for querying on-premises data.
mifune 👍 3 Selected: D
PostgreSQL has native support for spatial data, which is required by the company, so answer for me is D

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Amazon RDS for PostgreSQL is a managed target that AWS Schema Conversion Tool can assess and convert from Oracle, and AWS Database Migration Service performs the data movement, which is the standard path for moving Oracle workloads to a managed relational database. PostgreSQL has native spatial data support, so the spatial columns in the source can be represented without moving them to a separate analytics engine. Because the requirement is to query the databases that stay on premises directly as a foreign table, the RDS instance needs a private network path to the data centre, and AWS Direct Connect provides exactly that without exposing either side to the internet. Maintenance cron jobs then run on the DB instance, which is the managed tier.

Why the Other Options Are Wrong

A: DynamoDB global tables are a NoSQL multi-Region construct, not a relational target for Oracle data, and API Gateway does not provide foreign table support, so the core requirement of querying on-premises systems as a foreign table is unmet. Moving spatial data to S3 and querying it with Athena also breaks the relational model. B: RDS for SQL Server is the wrong engine for a workload migrating from Oracle, and AWS Glue crawlers are a data integration and cataloging service rather than a mechanism to query an on-premises Oracle database as a foreign table. C: Hosting Oracle on EC2 instances means the team manages the database themselves, which contradicts the objective of moving to managed services, and an internet gateway exposes the instances publicly, which is neither private nor appropriate for direct on-premises querying.

Community Comment Notes

The community voted 100 to 0 for D, and the top-voted comment identified the decisive technical facts: PostgreSQL supports spatial data natively through PostGIS, and SCT plus DMS is the standard Oracle migration path. Other commenters confirmed that SCT converts from Oracle to targets such as Aurora PostgreSQL and RDS PostgreSQL, that DMS is the service providing real-time change data capture, and that Direct Connect is what makes the direct on-premises connection sensible.

Official Reference

Related Analysis

Practice All SAP-C02 Questions

Access 85 questions with complete answers and detailed explanations.

View Full SAP-C02 Practice Test →

← Back to SAP-C02 Study Guide