Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.

Unlimited Access

Get Unlimited Contributor Access to the all ExamTopics Exams!
Take advantage of PDF Files for 1000+ Exams along with community discussions and pass IT Certification Exams Easily.

Exam AWS Certified Database - Specialty topic 1 question 25 discussion

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

A company is using Amazon RDS for MySQL to redesign its business application. A Database Specialist has noticed that the Development team is restoring their
MySQL database multiple times a day when Developers make mistakes in their schema updates. The Developers sometimes need to wait hours for the restores to complete.
Multiple team members are working on the project, making it difficult to find the correct restore point for each mistake.
Which approach should the Database Specialist take to reduce downtime?

  • A. Deploy multiple read replicas and have the team members make changes to separate replica instances
  • B. Migrate to Amazon RDS for SQL Server, take a snapshot, and restore from the snapshot
  • C. Migrate to Amazon Aurora MySQL and enable the Aurora Backtrack feature
  • D. Enable the Amazon RDS for MySQL Backtrack feature
Show Suggested Answer Hide Answer
Suggested Answer: A 🗳️

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
Amogh77
Highly Voted 2 years, 5 months ago
Answer is : A,Backtrack feature is only available with Aurora. each developer can perform DDL operations for the schema changes on the MySQL read replica once the read replica is in sync with its primary DB instance. Then the developer can promote the read replica and direct the application to use the promoted instance during the development phase. This solution isolates the schema changes done by each developer to their own promoted instance. This also avoids the problem of keeping track of the "correct restore point" that the team faced while using the same DB instance.
upvoted 17 times
saryu
2 years, 5 months ago
Correct
upvoted 2 times
...
TiredDad
9 months, 2 weeks ago
Developers would still need to wait hours for the restore to complete, in case of mistakes in their schema updates. But if we try to avoid this, the other option C requires migration to Aurora! and even then "Multiple team members are working on the project, making it difficult to find the correct restore point for each mistake." It is a tough call. https://serverfault.com/questions/791359/how-do-i-make-an-aws-rds-mysql-read-replica-have-a-different-schema this shows how read replica can be used for writes.. with some limitations..
upvoted 1 times
...
Germaneli
6 months, 2 weeks ago
That's why C is correct: Migrate to Aurora MySQL, there you can use the BackTrack functionality which is not available in RDS MySQL.
upvoted 1 times
...
...
[Removed]
Highly Voted 2 years, 6 months ago
I don't see how it can be A. These are read replicas, so by definition you cannot make changes to them. C sounds right to me
upvoted 17 times
chicagomassageseeker
2 years, 6 months ago
yes C is the answer.
upvoted 3 times
BillyMadison
2 years, 6 months ago
C agree https://aws.amazon.com/blogs/aws/amazon-aurora-backtrack-turn-back-time/
upvoted 2 times
...
...
Khasta
2 years, 2 months ago
Yes you can write to MYSQL readable replicas as mentioned here https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ReadRepl.html
upvoted 3 times
...
Jiang_aws1
1 year, 5 months ago
if using clone then will be OK but not Replicas - Read only
upvoted 1 times
...
...
MultiAZ
Most Recent 2 months, 2 weeks ago
Selected Answer: C
Answer is C. You cannot make changes on a read replica, which makes A invalid.
upvoted 1 times
...
Sathish_dbs
5 months, 3 weeks ago
the key is 'unable to find the correct restore point', so backtrack won't as you don't know which point it needs backing to as many people making many changes, so first thing is isolate each changes by allocating their own instances
upvoted 1 times
...
roymunson
6 months ago
Selected Answer: C
With RDS MySQL it's true to that you can make changes on read replica when setting read_only=0 to make read replica writable, but the use cases are recommended for indexing tables and small maintancae action because other action could break the replication. In addition the option read_only=0 works only for engines like InnoDB and with MyISAM u break the replication. In the question is nothing written about the engine type and that's why C is the right answer in my opinion.
upvoted 1 times
roymunson
6 months ago
Mmmhh now I saw the exact same question in an Udemy Exam Course and the authors are saying it is indeed Answer A with the following explaination: "For the given use-case, each developer can perform DDL operations for the schema changes on the MySQL read replica once the read replica is in sync with its primary DB instance. Then the developer can promote the read replica and direct the application to use the promoted instance during the development phase. This solution isolates the schema changes done by each developer to their own promoted instance. This also avoids the problem of keeping track of the "correct restore point" that the team faced while using the same DB instance. If you need to make changes to the MySQL or MariaDB read replica, you must set the read_only parameter to 0 in the DB parameter group for the read replica. You can then perform all needed DDL operations, such as creating indexes, on the read replica. Actions taken on the read replica don't affect the performance of the primary DB instance."
upvoted 1 times
...
...
aqiao
6 months, 4 weeks ago
Selected Answer: C
Although you can enable updates by setting the read_only parameter to 0 in the DB parameter group for the read replica, we recommend that you don't do so because it can cause problems if the read replica becomes incompatible with the source DB instance https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_MySQL.Replication.ReadReplicas.html#USER_MySQL.Replication.ReadReplicas.DelayReplication.ExistingReplica Beside, how to find the restore point with replica after mistake
upvoted 2 times
...
IhorK
8 months ago
Selected Answer: A
A is the answer. "...have the team members make changes to separate replica instances..." - we can make MySQL read replica writable. This will destroy replication, but for our purposes it is not critical. C - "Aurora Backtrack feature" doesn't suite because of "Multiple team members are working on the project, making it difficult to find the correct restore point for each mistake."
upvoted 1 times
...
Monknil
8 months, 1 week ago
Tricky one, is it C or A ? What is the Final answer some say A some C. Both seem plausible, but which is the better option
upvoted 2 times
...
mraronsimon
8 months, 4 weeks ago
Selected Answer: A
A (correct) B - incorrect - Migration to SQL server needs a high impact on the application code. Restoring from a snapshot is much slower than using a prepared read replica. C - incorrect - I think there was a good reason why the company use RDS instead of Aurora. But if you migrate to Aurora better to use the Clone feature instead of Backtrack in that case. D - incorrect - Backtrack is an Aurora (MySQL only) feature, not for RDS.
upvoted 1 times
...
megramlak
10 months, 1 week ago
Answer is A because this involves minimum effort
upvoted 1 times
...
Kodoma
10 months, 1 week ago
Selected Answer: A
As stated by others, PITR is not a good option since it is "difficult to find the correct restore point for each mistake", and PITR is also a feature only available on Aurora
upvoted 1 times
...
MrAliMohsan
10 months, 1 week ago
Selected Answer: A
The answer is A: Since MySQL Read replicas can be made writeable as per below documentation link. Previously, I was also thinking of C as a correct answer but this is wrong because of the statement "Multiple team members are involved in the project, which makes it difficult to identify the right restoration point for each error" https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ReadRepl.html#:~:text=Yes.%C2%A0You%20can%20enable%20the%20MySQL%20or%20MariaDB%20read%20replica%20to%20be%20writable.
upvoted 2 times
...
ken_test1234
1 year ago
Selected Answer: C
How is it possible to update or modify a read replica ?
upvoted 2 times
...
Theprince_Sree
1 year, 1 month ago
Selected Answer: C
Answer is C: Migrate to Aurora & use back track feature.
upvoted 2 times
...
Theprince_Sree
1 year, 1 month ago
Answer is C: Solution is to migrate the RDS to Aurora and enable backtrack. Folks who are saying A needs to explain on how they can apply changes on Read replicas and rollback them!!??
upvoted 1 times
...
im_not_robot
1 year, 1 month ago
Selected Answer: C
A is incorrect because 2 reasons: the first reason is read replica is read-only. The second reason is you need to modify the app to use different read replica instance endpoint for each team. If they have only one business app connects to a database, it is nightmare to connect to multiple read replica for each team B is incorrect because it is more expensive and can not solve the problem C is correct at backtrack is in-place restore D is incorrect because rds mysql doesn't support backtrack sorry for my english
upvoted 2 times
...
awsexams
1 year, 4 months ago
Selected Answer: A
I will go with A as well, mainly because of the wording on "correct restore point"
upvoted 3 times
...
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
Loading ...