Exam SAA-C03 All QuestionsBrowse all questions from this exam
Question 136

A company is migrating its on-premises PostgreSQL database to Amazon Aurora PostgreSQL. The on-premises database must remain online and accessible during the migration. The Aurora database must remain synchronized with the on-premises database.

Which combination of actions must a solutions architect take to meet these requirements? (Choose two.)

    Correct Answer: A, C

    To meet the requirement of migrating an on-premises PostgreSQL database to Amazon Aurora PostgreSQL while keeping the on-premises database online and synchronized, two primary actions are necessary. First, creating an AWS Database Migration Service (AWS DMS) replication server will facilitate the replication process. Second, creating an ongoing replication task will ensure continuous data synchronization between the on-premises database and the Aurora PostgreSQL database. These actions ensure real-time data replication and minimal downtime, meeting both criteria of accessibility and synchronization.

Discussion
123jhl0Options: AC

AWS Database Migration Service (AWS DMS) helps you migrate databases to AWS quickly and securely. The source database remains fully operational during the migration, minimizing downtime to applications that rely on the database. ... With AWS Database Migration Service, you can also continuously replicate data with low latency from any supported source to any supported target. https://aws.amazon.com/dms/

pentium75

PostgreSQL -> Aurora PostgreSQL requires schema conversion per https://aws.amazon.com/dms/schema-conversion-tool/

LoXoL

SCT is compatible with PostgreSQL as source and Aurora PostgreSQL as destination, but not required.

gustavtdOptions: AC

AC, here it is clearly shown https://docs.aws.amazon.com/zh_cn/dms/latest/sbs/chap-manageddatabases.postgresql-rds-postgresql.html

LuckyAro

You nailed it !

TariqKipkemeiOptions: AC

Create an AWS Database Migration Service (AWS DMS) replication server then create an ongoing replication task

cookieMrOptions: AC

These two actions (AC) will help meet the requirements of migrating the on-premises PostgreSQL database to Amazon Aurora PostgreSQL while keeping the on-premises database accessible and synchronized with the Aurora database. The ongoing replication task will ensure continuous data replication between the on-premises database and Aurora. The AWS DMS replication server will facilitate the migration process and handle the data replication. B. Creating a database backup does not ensure ongoing synchronization. D. Converting the database schema does not address the requirement of synchronization. E. Creating an EventBridge rule only monitors synchronization, but doesn't handle migration. The correct combination is A and C.

Hopeyemi

To meet the requirements of migrating an on-premises PostgreSQL database to Amazon Aurora PostgreSQL while keeping the on-premises database online and ensuring synchronization with the Aurora database, the following actions need to be taken: Create an ongoing replication task (Option A): This action involves setting up continuous replication between the on-premises PostgreSQL database and the Aurora PostgreSQL database. This ensures that changes made to the on-premises database are replicated to the Aurora database in real-time, keeping them synchronized. Create an AWS Database Migration Service (AWS DMS) replication server (Option C): AWS DMS provides a reliable and efficient way to migrate databases to AWS while minimizing downtime. By creating an AWS DMS replication server, you can configure and manage the replication tasks between the on-premises database and the Aurora database.

farnamjamOptions: AC

DMS has Continuous Data Replication using CDC

Michael_Li

CD A is out because it does not specify what is the service to perform the replication task, clearly what needed here is DMS B is out because backup is solution to keep 2 DB in sync, backup and restore takes long time C is correct as DMS takes care both full load and ongoing replication, see this youtube video https://www.youtube.com/watch?v=VhXDa9SPDLw D is right as from to PostgreSQL to Amazon Aurora PostgreSQL you need AWS Schema Conversion Tool, see https://aws.amazon.com/dms/schema-conversion-tool/ E is out monitor itself doen't perform the replication work, if we have to choose 3 options then we can have E selected

pentium75

https://docs.aws.amazon.com/zh_cn/dms/latest/sbs/chap-manageddatabases.postgresql-rds-postgresql-ongoing-replication.html literally says that you must "configure the ongoing replication task"

Amitabha09

C. Create an AWS Database Migration Service (AWS DMS) replication server. E. Create an Amazon EventBridge (Amazon CloudWatch Events) rule to monitor the database synchronization. AWS DMS can replicate data from on-premises databases to Aurora PostgreSQL in real time, so the on-premises database will remain online and accessible during the migration. AWS DMS can also automatically convert the database schema, so there is no need to use AWS SCT. An Amazon EventBridge rule can be used to monitor the database synchronization and send notifications if any errors occur. This is important because it allows the solutions architect to quickly identify and resolve any issues that may arise during the migration. A database backup of the on-premises database is not necessary because AWS DMS will replicate the data in real time. Creating an ongoing replication task is not necessary because AWS DMS will automatically create an ongoing replication task when the replication server is created.

David_Ang

Mate you can monitor everything you want but it is not going to make sure the synchronization is working, an alert is not going to help.

jatricOptions: AC

AC is more accurate as DMS will help to migrate the on-premises data base to cloud with ease and for ongoing replication to synchronized the datbase "ongiong replication task" will be helpfull. And yes its PostgreSQL to PostgreSQL migration so no SCT is needed ehre

BombAratOptions: AC

WeLL CHATGPT says SCT is not required so , AC makes sense

CCCatOptions: AC

Keywords: - migrating its on-premises PostgreSQL database to Amazon Aurora PostgreSQL - The Aurora database must remain synchronized with the on-premises database Analysis: Option A satisfy the requirement of “synchronized with the on-premises database” Option C suits for the homogeneous database migration. Option D is not needed in this scenario, it suits for the heterogeneous database. Homogeneous database migration tools: https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-oracle-database/homogeneous-migration-tools.html Heterogeneous database migration tools: https://aws.amazon.com/dms/schema-conversion-tool/

sumpatil

CD: Migrating a schema from PostgreSQL to Amazon Aurora (PostgreSQL) usually requires using the AWS Schema Conversion Tool (SCT) and the AWS Database Migration Service (DMS)

Alphateccc

answer is CD : postgresql and aurora postgresql have different schemes, you need sct for conversion and dms for the migration (replication)

vip2Options: AC

AC perform ongoing replication using AWS DMS to keep the source and target databases in sync

Mikado211

Well technically when you operate such task, you must create a database on the cloud, then operate a migration using DMS and none of the propositions give you those two tasks separately. Sometimes those questions can be really frustrating.

Guru4CloudOptions: AC

A) Create an ongoing replication task C) Create an AWS Database Migration Service (AWS DMS) replication server The key reasons are: An ongoing DMS replication task keeps the source and target databases synchronized during the migration. The DMS replication server manages and executes the replication tasks. Together, these will continuously replicate changes from on-prem to Aurora to keep them in sync. A database backup alone wouldn't maintain synchronization.

MutiverseAgentOptions: AC

https://docs.aws.amazon.com/dms/latest/sbs/chap-manageddatabases.postgresql-rds-postgresql.html https://docs.aws.amazon.com/dms/latest/userguide/CHAP_GettingStarted.Replication.html