DBS-C01 · Question #230
A development team asks a database specialist to create a copy of a production Amazon RDS for MySQL DB instance every morning. The development team will use the copied DB instance as a testing…
The correct answer is A. Create a snapshot of the production database each day before the 6 AM deadline. B. Create an RDS for MySQL DB instance from the snapshot. Select the desired DB instance size. C. Update a defined Amazon Route 53 CNAME record to point to the copied DB instance. To create a daily, cost-effective copy of an Amazon RDS for MySQL DB instance in a different VPC with a consistent endpoint, create a daily snapshot, restore it to a new DB instance, and then update a Route 53 CNAME record to point to the new instance's endpoint.
Question
A development team asks a database specialist to create a copy of a production Amazon RDS for MySQL DB instance every morning. The development team will use the copied DB instance as a testing environment for development. The original DB instance and the copy will be hosted in different VPCs of the same AWS account. The development team wants the copy to be available by 6 AM each day and wants to use the same endpoint address each day. Which combination of steps should the database specialist take to meet these requirements MOST cost-effectively? (Choose three.)
Options
- ACreate a snapshot of the production database each day before the 6 AM deadline.
- BCreate an RDS for MySQL DB instance from the snapshot. Select the desired DB instance size.
- CUpdate a defined Amazon Route 53 CNAME record to point to the copied DB instance.
- DSet up an AWS Database Migration Service (AWS DMS) migration task to copy the snapshot to
- EUse the CopySnapshot action on the production DB instance to create a snapshot before 6 AM.
- FUpdate a defined Amazon Route 53 alias record to point to the copied DB instance.
How the community answered
(16 responses)- A56% (9)
- D6% (1)
- E13% (2)
- F25% (4)
Why each option
To create a daily, cost-effective copy of an Amazon RDS for MySQL DB instance in a different VPC with a consistent endpoint, create a daily snapshot, restore it to a new DB instance, and then update a Route 53 CNAME record to point to the new instance's endpoint.
Creating a snapshot of the production database daily is the most effective way to capture a point-in-time copy of the data for restoration into a new development environment.
Restoring an RDS for MySQL DB instance from a snapshot is the standard procedure to create a copy of the database, allowing for selection of the desired instance size for the testing environment.
Updating an Amazon Route 53 CNAME record to point to the new DB instance's endpoint allows the development team to use a consistent, logical endpoint address each day, abstracting away the underlying, dynamically assigned RDS endpoint.
AWS Database Migration Service (AWS DMS) is designed for live data migrations and synchronization, not for creating copies of RDS instances from snapshots, which is a simpler restore operation.
The `CopySnapshot` action is primarily used for copying an existing snapshot, typically across regions or accounts, rather than for the initial creation of a daily snapshot from a running production DB instance.
While Route 53 alias records can be used, CNAME records are generally more flexible and appropriate for mapping a custom domain name to an arbitrary DNS endpoint like an RDS DB instance endpoint.
Concept tested: RDS snapshot, restore, and Route 53 for consistent endpoints
Source: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_CreateSnapshot.html
Topics
Community Discussion
No community discussion yet for this question.