Exam AWS Certified Database - Specialty topic 1 question 283 discussion

about the concerns about heterogeneous for SCT: Per: https://aws.amazon.com/dms/schema-conversion-tool/ SCT would be used during the migration between: Src : PostgreSQL Des : Aurora MySQL, Aurora PostgreSQL, MySQL, PostgreSQL A is the best practice C downtime,transfer, reload,verify ... too much workloads

AWS encourages to use AWS services and it might expect you also to answer inline with that so will go with A as there is no proper difference between A and C

We can have downtime in this scenario. In the first link is mentioned that if you have more than 100 GB aws the pg_dump and pg_restore function MAY not be suitable for your usecase, but if time is not the problem here it could be suitable. The second link points out the current bp and there is nothing mentioned about DMS. I'm realy not sure about this one but I would go with c here. https://docs.aws.amazon.com/dms/latest/sbs/chap-manageddatabases.postgresql-rds-postgresql-full-load-pd_dump.html Best Practice: https://aws.amazon.com/blogs/database/best-practices-for-migrating-postgresql-databases-to-amazon-rds-and-amazon-aurora/

Only option here is A C. cannot be used - pg_dump and pg_restore is only for DBs 100 GB or less https://docs.aws.amazon.com/dms/latest/sbs/chap-manageddatabases.postgresql-rds-postgresql-full-load.html

A. Use the AWS Schema Conversion Tool (AWS SCT) and AWS Database Migration Service (AWS DMS)

I will pick A. Per linke, https://docs.aws.amazon.com/dms/latest/sbs/chap-manageddatabases.postgresql-rds-postgresql-full-load-publisher.html, 100G is the threshhold. If it is less than 100G, C works fine. But in this question, the database size is 200G. So I will go with A.

NOT A- This is a homogeneous migration . SCT is required only for Heterogeneous migration. NOT D- Can't crate RR using On-prem PG as source NOT B - Irrelevant 'C' is the answer - Easy, Error free and fast migration method

A. It is quite a bit of work to set up. There is no need for schema conversion since it is a homogeneous migration. B. What? C. If you need to create secondary database objects, then pg_dump and pg_restore is the most appropriate option. However, this option incurs a performance tradeoff compared to other options. D. Creating Aurora read-replicas from self-managed databases is not supported. https://docs.aws.amazon.com/dms/latest/sbs/chap-manageddatabases.postgresql-rds-postgresql-summary.html

Ans: C - Nothing said about downtime - 200Gb is not so big size

Dont need SCT as the migration is not heterogenous.(PostgreSQL to PostgreSQL)

A. Customers looking to migrate self-managed PostgreSQL databases to Amazon RDS for PostgreSQL or Aurora PostgreSQL, can use one of the three main approaches. Use a native or third-party database migration method such as pg_dump and pg_restore for full load only migrations. Use a managed service such as AWS Database Migration Service (AWS DMS) for full load and ongoing replication. Use a native tool for full load and a managed AWS DMS service for ongoing replication. We call this strategy the hybrid approach. https://docs.aws.amazon.com/dms/latest/sbs/chap-manageddatabases.postgresql-rds-postgresql.html

Option C is the best option here. Option A could have been correct if Schema conversion was not mentioned. Option B is not the most efficient way and option D is not applicable as Aurora doesn't support on-prem database source for creating read replica.