Q84 — AWS SAA-C03 Ch.17

Question 84 of 89 | ← Chapter 17

Q1384. A company has an Amazon RDS for MySQL database that runs in the AWS Cloud. The company needs to implement a disaster recovery (DR) plan. The company wants to regularly back up the database. The DR plan must also retain copies in the company's on-premises DR data center that can be restored in the on- premises DRenvironment if needed.Which solution meets these requirements with the LEAST operational overhead?

Correct Answer: A. Create individual RDS DB snapshots and export the snapshots to Amazon S3. Sync the snapshots to the on-premises DR data center by using the aws s3 sync command.

Explanation

Let's analyze each option to determine the solution that meets the requirements with the least operational overhead:Option ACreating individual RDS DB snapshots and exporting to Amazon S3: This process involves manually creating snapshots of the Amazon RDS for MySQL database and then exporting them to Amazon S3. While it is a valid way to back up the database, it requires manual intervention or custom - scripting to automate the snapshot creation and export process.Syncing to on - premises using aws s3 sync: The aws s3 sync command can be used to synchronize the snapshots from S3 to the on - premises DR data center. However, setting up and managing this synchronization, including handling errors, scheduling, and ensuring data integrity, adds to the operational overhead. Overall, this approach requires significant manual setup and ongoing management.Option BConfiguring AWS Backup for RDS backups: AWS Backup is a fully - managed backup service that simplifies the process of backing up and restoring data across AWS services, including Amazon RDS. By configuring AWS Backup, you can easily set up automated backup policies for your RDS database, such as backup frequency, retention period, etc. This reduces the need for manual snapshot creation and management.Copying backups to an on - premises vault: The description of copying backups to a vault in the on - premises DR data center is a bit inaccurate in the context of AWS Backup. AWS Backup can be configured to copy backups to another AWS region for disaster recovery purposes. To get the backups to the on - premises DR data center, you would still need an additional step like exporting the backups from AWS Backup (which might involve more complex operations) or using a third - party tool for data transfer. This option has some limitations in directly meeting the on - premises backup requirement with minimal overhead.Option CUsing mysqldump utility: The mysqldump utility is a command - line tool used to export the contents of a MySQL database into a SQL file. While it is a well - known and reliable method for database backup, it has several drawbacks in terms of operational overhead.Storing in Amazon S3 and syncing daily: Similar to Option A, you need to set up a process to run mysqldump regularly (either manually or through scripting), store the dump file in Amazon S3, and then sync it to the on - premises DR data center. This involves multiple manual steps, error handling, and scheduling, which increases the operational complexity.Option DCreating individual RDS DB snapshots and exporting to Amazon S3: Just like in Option A, creating RDS DB snapshots and exporting them to S3 requires some initial setup and potentially ongoing management of the snapshot process.Using AWS DataSync to transfer snapshots: AWS DataSync is a fully - managed data transfer service that simplifies and accelerates data transfer between on - premises storage and AWS storage services, such as Amazon S3. Once the RDS snapshots are in S3, DataSync can be configured to automatically transfer them to the on - premises DR data center. This reduces the manual effort required for data synchronization compared to using aws s3 sync. However, setting up DataSync still requires some initial configuration and management.Among the given options, Option A is a relatively straightforward approach that can be implemented with basic AWS CLI knowledge. Although it has some manual aspects, compared to the other options:Option B has limitations in directly getting backups to the on - premises data center. Option C involves more complex and manual steps for database export and transfer. Option D requires setting up AWS DataSync in addition to snapshot management. Option A provides a balance between simplicity and meeting the requirements. You can create a script to automate the snapshot creation, export to S3, and use the aws s3 sync command to keep the on - premises data center in sync. This can be set up with relatively less operational overhead compared to the other options.So, the answer is A.