Topic 1 Question 330
A company has a web application with a database tier that consists of an Amazon EC2 instance that runs MySQL. A SysOps administrator needs to minimize potential data loss and the time that is required to recover in the event of a database failure.
What is the MOST operationally efficient solution that meets these requirements?
Create an Amazon CloudWatch alarm for the StatusCheckFailed_System metric to invoke an AWS Lambda function that stops and starts the EC2 instance.
Create an Amazon RDS for MySQL Multi-AZ DB instance. Use a MySQL native backup that is stored in Amazon S3 to restore the data to the new database. Update the connection string in the web application.
Create an Amazon RDS for MySQL Single-AZ DB instance with a read replica. Use a MySQL native backup that is stored in Amazon S3 to restore the data to the new database. Update the connection string in the web application
Use Amazon Data Lifecycle Manager (Amazon DLM) to take a snapshot of the Amazon Elastic Block Store (Amazon EBS) volume every hour. In the event of an EC2 instance failure, restore the EBS volume from a snapshot.
ユーザの投票
コメント(10)
- 正解だと思う選択肢: D
To me both B&D minimize potential data loss. However, the question is not specifying availability (Multi-AZ is B) Instead, the question is emphasizing quick recovery from backup (not active/active recovery) Therefore, I think only option D meets both criteria for minimizing potential data loss and quick recovery.
- 1 Hour RPO (only D specifies hourly snapshots & hourly RPO)
- Snapshots (D) have faster RTO than native backup restore from S3 (B) In the real world, I've used both backups (regularly/scheduled) and snapshots (prior to scheduled changes, etc.)
👍 12Gomer2023/06/14 - 正解だと思う選択肢: B
B satisfy the "minimize potential data loss and the time that is required to recover in the event of a database failure and the MOST operationally efficient solution - doing one time and forget it.
👍 3Benly2023/11/01 - 正解だと思う選択肢: B
My first questions was: "why has this not already been migrated over to RDS Multi-AZ" I think it most operationally efficient to use a service that could be renamed "MySQL designed for failover events" data loss would be minutes. Data loss on EBS snapshots would be up to 60 mins. Being in this situation I would be quizzing my project manager on why in gods name are we storing this on EC2/EBS and aren't these backups slight overkill.
👍 3DeaconStJohn2023/11/14
シャッフルモード