1Z0-908 · Question #49
You have a MySQL system with 500 GB of data that needs frequent backups. You use a mix of MyISAM and InnoDB storage engines for your data. Examine your backup requirement: - The MySQL system being…
The correct answer is C. Take a logical backup of the MySQL system. Logical backups (e.g., mysqldump) export data as portable SQL statements that can be restored on any MySQL system regardless of OS or version, directly satisfying requirement 2. They can be scheduled to run hourly to meet the 1-hour RPO (requirement 3), and while brief read…
Question
You have a MySQL system with 500 GB of data that needs frequent backups. You use a mix of MyISAM and InnoDB storage engines for your data. Examine your backup requirement:
- The MySQL system being backed up can never be unavailable or locked to the client
applications.
- The recovery from the backup must work on any system.
- Only 1 hour of data can be lost on recovery of the backup.
Which option fulfills all backup requirements?
Options
- ATake a physical backup of the MySQL system.
- BUse the Clone Plugin to copy the data to another MySQL system.
- CTake a logical backup of the MySQL system.
- DTake your backup from a slave of the MySQL system.
How the community answered
(23 responses)- A9% (2)
- B4% (1)
- C83% (19)
- D4% (1)
Explanation
Logical backups (e.g., mysqldump) export data as portable SQL statements that can be restored on any MySQL system regardless of OS or version, directly satisfying requirement 2. They can be scheduled to run hourly to meet the 1-hour RPO (requirement 3), and while brief read locks occur on MyISAM tables, the system remains available to clients - fulfilling requirement 1 better than the alternatives.
Why the distractors fail:
- A (Physical backup): Raw data-file copies are tied to the originating OS and MySQL version, failing the "any system" portability requirement; MyISAM also requires table locks, risking unavailability.
- B (Clone Plugin): The Clone Plugin only supports InnoDB - it cannot copy MyISAM tables, so it breaks immediately given the mixed-engine environment.
- D (Slave backup): Replication lag on a slave can grow beyond 1 hour during heavy write loads, making it impossible to guarantee the ≤1-hour data-loss limit.
Memory tip: Think "Logical = Language (SQL) = portable." If an exam question stresses portability across any system alongside a mixed-engine setup, logical backup is almost always the answer - physical backups are fast but system-specific, while SQL dumps travel anywhere.
Topics
Community Discussion
No community discussion yet for this question.