Exam AWS Certified SysOps Administrator - Associate topic 1 question 286 discussion

Option A - Automated Snapshot: Since automated backups are enabled with a 7-day retention period, you can easily identify the most recent automated snapshot taken within the last 24 hours. You can use this snapshot to restore a new RDS DB cluster. This process is straightforward and does not require much operational overhead. Option C - Read Replica and Promotion: By creating a read replica in the original RDS DB cluster, you ensure that the replica stays up-to-date with the source database in near real-time. To meet the requirement of having data no more than 24 hours old, you can promote the read replica to a standalone DB cluster within the desired time frame. This option leverages the replication mechanism and is also relatively simple to implement.

There are actually CLI commands defined to do both "A" and "C". I believe the DB Migration Service is used to migrate and reformat external databases to AWS. I see no references to it being used to copy/migrate data within AWS. Anyway, here are the CLI examples I mentioned which I found online: # Promotes specified read replica to become a standalone DB cluster. aws rds promote-read-replica-db-cluster --db-cluster-identifier mydbcluster-1 # Creates a new DB cluster by resoring a DB cluster snapshot named test-instance-snapshot. aws rds restore-db-cluster-from-snapshot --db-cluster-identifier newdbcluster --snapshot-identifier test-instance-snapshot --engine aurora-postgresql --engine-version 10.7

Options B, D, and E involve additional steps and may have more operational overhead: B. Back up the database to Amazon S3 by using native database backup tools. Create a new RDS DB cluster and restore the data to the new RDS DB cluster. This involves manual steps and might have more operational overhead. D. Create a new RDS DB cluster. Use AWS Database Migration Service (AWS DMS) to migrate data from the current RDS DB cluster to the newly created RDS DB cluster. AWS DMS is a powerful tool but may introduce more complexity, especially if the goal is a relatively straightforward copy of data within a short time frame. E. Use the pg_dump utility to export data from the original RDS DB cluster to an Amazon EC2 instance. Create a new RDS DB cluster. Use the pg_restore utility to import the data from the EC2 instance to the new RDS DB cluster. This involves manual export/import steps and may not be as efficient as using automated snapshot restoration or read replica promotion.

backup, migration require "Read" Transaction - cause "Operational Overhead".

Create new from backup or read replica

A - https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithAutomatedBackups.html C - You can promote a read replica into a standalone DB instance. When you promote a read replica, the DB instance is rebooted before it becomes available. https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ReadRepl.html

A C looks good