Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Oracle Exam 1Z0-908 Topic 11 Question 80 Discussion

Actual exam question for Oracle's 1Z0-908 exam
Question #: 80
Topic #: 11
[All 1Z0-908 Questions]

Your MySQL environment has asynchronous position based-replication with one master and one slave.

The slave instance had a disk I/O problem, so it was stopped.

You determined that the slave relay log files were corrupted and unusable, but no other files are damaged.

You restart MySQL Server.

How can replication be restored?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Lashonda
6 months ago
Ah, the joys of database administration. Option C is the way to go, for sure. Gotta love it when the solution is as simple as deleting and re-configuring.
upvoted 0 times
...
Gilberto
6 months ago
Heh, the slave had a 'disk I/O problem,' huh? Sounds like someone's been sneaking their coffee into the server room again. But in all seriousness, C is the clear winner here.
upvoted 0 times
Brittni
5 months ago
C) The slave relay logs should be deleted; execute CHANGE MASTER to adjust the replication relay log file name, then issue start SLAVE;
upvoted 0 times
...
Nenita
5 months ago
B) The relay logs from the master should be used to replace the corrupted relay logs.
upvoted 0 times
...
Jestine
5 months ago
A) The slave relay logs should be deleted; then execute START SLAVE;
upvoted 0 times
...
...
Nicholle
6 months ago
I'm not sure, but option B seems a bit risky. Using the master's relay logs to replace the corrupted ones? Sounds like a recipe for disaster. Maybe it's best to just start fresh with option C.
upvoted 0 times
...
Shaun
6 months ago
I disagree, I believe the correct answer is C) The slave relay logs should be deleted; execute CHANGE MASTER to adjust the replication relay log file name, then issue start SLAVE.
upvoted 0 times
...
Vilma
6 months ago
Hmm, I think option C is the way to go. Deleting the corrupted relay logs and adjusting the replication settings sounds like the most straightforward approach.
upvoted 0 times
Yun
5 months ago
Yeah, deleting the corrupted relay logs and adjusting the replication settings sounds like the right way to restore replication.
upvoted 0 times
...
Edwin
5 months ago
I agree, option C seems like the best solution in this situation.
upvoted 0 times
...
Lovetta
6 months ago
Let's go ahead and try that to see if it works.
upvoted 0 times
...
Dudley
6 months ago
Yeah, deleting the corrupted relay logs and adjusting the replication settings sounds like the right way to restore replication.
upvoted 0 times
...
Adolph
6 months ago
Yeah, deleting the corrupted relay logs and adjusting the replication settings sounds like the right way to restore replication.
upvoted 0 times
...
Rosann
6 months ago
I agree, option C seems like the best solution in this situation.
upvoted 0 times
...
Geoffrey
6 months ago
I agree, option C seems like the best solution.
upvoted 0 times
...
...
Gilma
7 months ago
I think the answer is A) The slave relay logs should be deleted; then execute START SLAVE.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77