ExamTopics Logo
Mail Us[email protected]
Menu
Amazon Discussions
exam questions

Exam AWS Certified Database - Specialty All Questions

View all questions & answers for the AWS Certified Database - Specialty exam
Go to Exam

Exam AWS Certified Database - Specialty topic 1 question 11 discussion

Exam question from Amazon's AWS Certified Database - Specialty
Question #: 11
Topic #: 1
[All AWS Certified Database - Specialty Questions]

The Development team recently executed a database script containing several data definition language (DDL) and data manipulation language (DML) statements on an Amazon Aurora MySQL DB cluster. The release accidentally deleted thousands of rows from an important table and broke some application functionality.
This was discovered 4 hours after the release. Upon investigation, a Database Specialist tracked the issue to a DELETE command in the script with an incorrect
WHERE clause filtering the wrong set of rows.
The Aurora DB cluster has Backtrack enabled with an 8-hour backtrack window. The Database Administrator also took a manual snapshot of the DB cluster before the release started. The database needs to be returned to the correct state as quickly as possible to resume full application functionality. Data loss must be minimal.
How can the Database Specialist accomplish this?

  • A. Quickly rewind the DB cluster to a point in time before the release using Backtrack.
  • B. Perform a point-in-time recovery (PITR) of the DB cluster to a time before the release and copy the deleted rows from the restored database to the original database.
  • C. Restore the DB cluster using the manual backup snapshot created before the release and change the application configuration settings to point to the new DB cluster.
  • D. Create a clone of the DB cluster with Backtrack enabled. Rewind the cloned cluster to a point in time before the release. Copy deleted rows from the clone to the original database.
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️
by chicagomassageseeker at July 7, 2020, 11:06 p.m.
Disclaimers:
  • - ExamTopics website is not related to, affiliated with, endorsed or authorized by Amazon.
  • - Trademarks, certification & product names are used for reference only and belong to Amazon.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
edmondme
Highly Voted 3 years, 7 months ago
D is right, you can create a clone with backtrack if the database was created with backtrack which it was in this case. It's either B (pitr) or D (backtrack). Backtrack is faster. A is wrong, because if you backtrack, you lose the data that users entered for the past 4 hours. you want to clone to another area and copy the data that was lost.
upvoted 25 times
Jiang_aws1
2 years, 7 months ago
X A. May lose 4 hrs users entered X B. Take too long ( restored -> copy delete rows to Org-DB ) X C. Take too long & May lose 4 hrs users entered D. Better a. clone is faster than restore b. Copy delete rows to Org-DB
upvoted 2 times
Jiang_aws1
2 years, 7 months ago
Only A, D using "Rewind" which is good D is correct if we can rewind "clone with Backtrack enabled" Anyone know ?
upvoted 3 times
aqiao
1 year, 8 months ago
Agree with you, D is the best option:https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Managing.Backtrack.html
upvoted 1 times
aqiao
1 year, 8 months ago
Correct my answer, it should be B. D is wrong because "you can't backtrack a database clone to a time before that database clone was created" from the backtrack limitation here :https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Managing.Backtrack.html
upvoted 2 times
...
...
...
...
lelesp6
2 years ago
D its wrong, da backtrack only right after you create clone.
upvoted 3 times
...
...
halol
Highly Voted 3 years, 7 months ago
A&B correct.however, A cause loss data for last 4 hours but it's quickly will take just few minutes to rewind the databse to 4 hours before, however B will keep database and fix it by reinsert deleted records from database which created from restore point in time this will take more time but without loss data as the question refer to "Data loss must be minimal" So I guess B the correct answer
upvoted 24 times
ChauPhan
3 years, 6 months ago
B is wrong because "Perform a point-in-time recovery (PITR) of the DB cluster to a time before the release" I example: The release time was 5AM, and you found that the records are deleted at 9AM. So why we recover the database "before 5AM" (release time). ==> we still lose 4 hours. The correct way to minimize data loss is: recover as nearest as possible time such as 8:55AM) then copy the deletion data. So only 5 mins data loss. Only this minimizes data loss.
upvoted 4 times
khchan123
3 years ago
Agree with ChauPhan. B is wrong. A is correct.
upvoted 1 times
swakan
2 years, 8 months ago
Option B suggest to restore the db to a point before the records were deleted, then copy the required records from this newly restored db (using PITR) to the original DB. So this way, all the other changes made on the DB are still there, while we copied the deleted rows from the PITR db. I think option B is correct. Please correct if wrong.
upvoted 3 times
...
...
Maze
2 years, 7 months ago
PITR is restored another cluster with Product cluster. Executing PITR doesn't mean back-forward. we dont lose 4 hours. we can export and import from PITR restored cluster.
upvoted 1 times
...
...
...
missipssamarsh
Most Recent 1 year, 1 month ago
Selected Answer: B
X D : You can't backtrack a database clone to a time before that database clone was created. https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Managing.Backtrack.html
upvoted 1 times
...
Bezi
1 year, 2 months ago
I will go for "A". Here's an excerpt from the below link: https://aws.amazon.com/blogs/aws/amazon-aurora-backtrack-turn-back-time/ … After that regrettable moment when all seems lost, you simply pause your application, open up the Aurora Console, select the cluster, and click Backtrack DB cluster. Then you select Backtrack and choose the point in time just before your epic fail, and click Backtrack DB cluster.
upvoted 2 times
...
MultiAZ
1 year, 4 months ago
Selected Answer: B
The answer is B. With A you would lose all the data gathered in the last 4 hours
upvoted 1 times
...
Hisayuki
1 year, 4 months ago
Selected Answer: A
BackTrack - If you accidentally issue a Delete statement without a Where clause (that is, delete all items) or drop a table, you can use Backtrack to quickly revert to the previous state. You can do the same thing with PITR, but it takes time to restore from an existing backup to a different cluster/instance.
upvoted 1 times
Hisayuki
1 year, 4 months ago
Sorry, I noticed the window is 8 hours. We have to use PITR not to lose the data of the 4 hours. The answer is B.
upvoted 1 times
...
...
Jrhp
1 year, 5 months ago
Selected Answer: A
Backtracking "rewinds" the DB cluster to the time you specify. Backtracking is not a replacement for backing up your DB cluster so that you can restore it to a point in time. However, backtracking provides the following advantages over traditional backup and restore: You can easily undo mistakes. If you mistakenly perform a destructive action, such as a DELETE without a WHERE clause, you can backtrack the DB cluster to a time before the destructive action with minimal interruption of service https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Managing.Backtrack.html#AuroraMySQL.Managing.Backtrack.Overview
upvoted 1 times
...
AmbrishK
1 year, 6 months ago
Selected Answer: D
This option combines the benefits of both Backtrack and data recovery by cloning the cluster and using Backtrack to recover lost data. After that, you can copy the missing rows back into the original database. It allows for minimal data loss. Based on the goal of minimizing data loss and ensuring a quick recovery, option D seems like the best choice. It leverages Backtrack, provides a way to recover the deleted data, and then copy it back into the original database. However, option B is also a valid choice if Backtrack is not an option or if the deleted data is outside the backtrack window.
upvoted 1 times
...
Germaneli
1 year, 8 months ago
Selected Answer: A
A is correct, because backtrack is the fastest way to "[return] the database to the correct state as quickly as possible", as the questions asks. There is no mention or requirement of retaining potentially lost user input. Additionally, restoring the deleted rows while keeping actual user input from the last 4 hours after the loss might infringe foreign key constraints within the database, making the data inconsistent.
upvoted 2 times
...
aqiao
1 year, 8 months ago
Selected Answer: B
A x: It will cause 4 hours data loss after release B yes C x: It will cause 4 hours data loss after release and involve additional change D x: You can't backtrack a database clone to a time before that database clone was created from the backtrack limitation here :https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Managing.Backtrack.html
upvoted 2 times
...
SamDDD
1 year, 10 months ago
Selected Answer: A
You can't backtrack a database clone to a time before that database clone was created. However, you can use the original database to backtrack to a time before the clone was created https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Managing.Backtrack.html
upvoted 1 times
...
mraronsimon
1 year, 10 months ago
Selected Answer: B
A & C (incorrect) - dataloss! D (incorrect) - "You can't backtrack a database clone to a time before that database clone was created. However, you can use the original database to backtrack to a time before the clone was created." The correct answer is B. However, D could be better with a little change: You should use the clone db as new production and you should rewind on the original. Copy deleted rows from original to the clone.
upvoted 2 times
mraronsimon
1 year, 10 months ago
Reference: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Managing.Backtrack.html
upvoted 1 times
...
...
MrAliMohsan
1 year, 11 months ago
Selected Answer: B
Option D would have been correct if it has suggested to rewind the DB cluster not the cloned cluster. Since you cannot rewind the cloned cluster before the time it was created. https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Managing.Backtrack.html#:~:text=You%20can%27t%20backtrack%20a%20database%20clone
upvoted 1 times
...
aviathor
1 year, 11 months ago
Selected Answer: B
xA. Rewinding the database means restoring the deleted data, but also undoing all other changes to the database => data loss B. Perform a point-in-time recovery (PITR) of the DB cluster to a time before the release and copy the deleted rows from the restored database to the original database. => This is the best course of action. xC. This also entails losing all of the changes made after the deletion event. xD. This does not work because you cannot rewind a clone to a time before the clone was created.
upvoted 3 times
...
aviathor
1 year, 11 months ago
xA. Rewinding the database means restoring the deleted data, but also undoing all other changes to the database => data loss B. Perform a point-in-time recovery (PITR) of the DB cluster to a time before the release and copy the deleted rows from the restored database to the original database. => This is the best course of action. xC. This also entails losing all of the changes made after the deletion event. xD. This does not work because you cannot rewind a clone to a time before the clone was created.
upvoted 1 times
...
backbencher2022
2 years, 2 months ago
D is right - https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Managing.Backtrack.html
upvoted 1 times
...
sk1974
2 years, 2 months ago
https://aws.amazon.com/getting-started/hands-on/aurora-cloning-backtracking/ <--- D is the answer
upvoted 1 times
...
Load full discussion...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago