1Z0-888 · Question #35
Which two statements describe how InnoDB recovery works?
The correct answer is B. InnoDB blocks some operations when innodb_force_recovery is set to greater than 0. F. It is always required to enable innodb_force_recovery to perform a crash recovery. Important note: The stated correct answers (B and F) appear to contain an error. F is factually incorrect, and the actual correct pair should be A and B. Here's why: Why A and B are correct: (A) InnoDB's crash recovery is largely automatic - on restart after a crash, InnoDB…
Question
Options
- AInnoDB handles most crash recoveries automatically.
- BInnoDB blocks some operations when innodb_force_recovery is set to greater than 0.
- CThere will in general be lost committed transactions after a crash using the default settings.
- DIt is required to enable binlog_gtid_simple_recovery to perform a crash recovery.
- EIt is recommended to set innodb_force_recovery = 1 as part of normal operations.
- FIt is always required to enable innodb_force_recovery to perform a crash recovery.
How the community answered
(60 responses)- A15% (9)
- B72% (43)
- C3% (2)
- D2% (1)
- E8% (5)
Explanation
Important note: The stated correct answers (B and F) appear to contain an error. F is factually incorrect, and the actual correct pair should be A and B. Here's why:
Why A and B are correct:
- (A) InnoDB's crash recovery is largely automatic - on restart after a crash, InnoDB replays its redo log and rolls back uncommitted transactions without administrator intervention.
- (B) When
innodb_force_recoveryis set to any value greater than 0, InnoDB prevents write operations (INSERT/UPDATE/DELETE) to protect data integrity during a forced-recovery session.
Why the distractors (and F) are wrong:
- (C) With default settings, InnoDB does not lose committed transactions - the redo log ensures durability (the D in ACID).
- (D)
binlog_gtid_simple_recoveryis a replication/GTID optimization, not a requirement for InnoDB crash recovery. - (E)
innodb_force_recovery = 1is a break-glass emergency tool - setting it in normal operations is actively harmful. - (F) This directly contradicts A;
innodb_force_recoveryis only needed when automatic recovery fails (e.g., severe corruption). It is never required for a standard crash recovery.
Memory tip: Think of innodb_force_recovery as a crowbar - you only reach for it when the normal automatic door (crash recovery) won't open. Using a crowbar every day damages the door.
If this question appeared on a practice exam or study guide, flag it - the answer key likely has a typo (B,F should be A,B).
Topics
Community Discussion
No community discussion yet for this question.