Explanation could be improved

[Privat33r]

Question: “A web application, which is hosted in your on-premises data center and uses a MySQL database, must be migrated to AWS Cloud. You need to ensure that the network traffic”

Incorrect answer variant: “Launch a new RDS database instance with the Backtrack feature enabled.”

TD’s Explanation: “The option that says: Launch a new RDS database instance with the Backtrack feature enabled is incorrect because the Backtrack feature simply “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, you can easily undo mistakes using the backtrack feature if you mistakenly perform a destructive action, such as a DELETE without a WHERE clause.“

Backtracking feature[2] is available only for Aurora[3]. I think that it’s important to mention. Even though Aurora might technically be a part of the RDS (debatable), it kind of stands aside, even in documentation[1].

1 – https://docs.aws.amazon.com/rds/

2 – https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Managing.Backtrack.html

3 – https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_BacktrackDBCluster.html

[JR-TutorialsDojo]

Hello Privat33r,

Thank you for bringing this to our attention. You’re correct that the Backtrack feature is only available on the Aurora engine type. As you requested, we will make the necessary updates to mention the Aurora engine type in the explanation and the option.

If you have any further suggestions or feedback, feel free to share them with us. We are committed to improving our practice tests based on user input.

Best regards,
JR @ Tutorials Dojo