1Z0-908 · Question #68
Which two statements are true about using backups of the binary log? (Choose two.)
The correct answer is D. Binary logs can always be used to unapply unwanted schema changes. E. They allow for point-in-time recovery of the data. Important note: The provided answer key (D, E) appears to contain an error. Based on standard database behavior, the correct answers should be A and E. Here's why: Why A and E are correct: A is true - point-in-time recovery typically requires applying multiple sequential binary…
Question
Which two statements are true about using backups of the binary log? (Choose two.)
Options
- AMultiple binary logs can be used to restore data.
- BMultiple binary logs can be applied in parallel for faster data restoration.
- CBinary logs are relatively small, and therefore, excellent for long-term storage and disaster
- DBinary logs can always be used to unapply unwanted schema changes.
- EThey allow for point-in-time recovery of the data.
How the community answered
(33 responses)- A6% (2)
- C3% (1)
- D91% (30)
Explanation
Important note: The provided answer key (D, E) appears to contain an error. Based on standard database behavior, the correct answers should be A and E. Here's why:
Why A and E are correct:
- A is true - point-in-time recovery typically requires applying multiple sequential binary log files (e.g.,
binlog.000001,binlog.000002) after restoring a base backup. - E is true - binary logs are the foundation of point-in-time recovery (PITR), letting you replay transactions up to any specific timestamp or log position after restoring a full backup.
Why the distractors are wrong:
- B is false - binary logs must be applied sequentially, not in parallel, because they record ordered transactions; parallel application would corrupt data.
- C is false - binary logs can grow very large on busy systems and are not designed for long-term storage.
- D is false (and should NOT be a correct answer) - the word "always" makes this wrong. Binary logs record changes going forward, but you cannot reliably unapply DDL changes (e.g.,
DROP TABLE) using only binary logs. You need a prior backup.
Memory tip: Think of binary logs as a transaction tape recorder - you can fast-forward (replay) but not rewind (unapply). PITR = full backup + sequential binary log replay.
If this is from an official exam, double-check the source - A and E is the defensible answer.
Topics
Community Discussion
No community discussion yet for this question.