You have just executed a manual backup by using this command: mysqldump -u root -P --socket=/tmp/my.sock --backup-dir=/my/backup/ backup The operation completed without error. What is the state of…

Question

Options

• ABackup State = Compressed Backup Operation = copy-back
• BBackup State = Raw Backup Operation = apply-log
• CBackup State = Prepared Backup Operation = validate
• DBackup State = Prepared Backup Operation = apply-log
• EBackup State = Raw Backup Operation = backupdir-to-image

• A
  8% (1)
• C
  8% (1)
• E
  85% (11)

Explanation

Option E is correct because the mysqlbackup backup command (note: the question's command syntax indicates MySQL Enterprise Backup, not mysqldump) creates a raw backup - the backup data is captured in directory format but InnoDB redo logs have not yet been applied, leaving the data files in an inconsistent state. Since the backup was written to a --backup-dir, the required next operation is backupdir-to-image, which converts the directory-based raw backup into a single portable image file (.mbi) that can then be processed and restored.

Why the distractors are wrong:

• A is wrong because no --compress flag was used (ruling out Compressed), and copy-back restores a prepared backup - not a raw one.
• B is wrong on the operation: apply-log transitions the backup from Raw to Prepared - it doesn't prepare the directory-format backup for restoration; backupdir-to-image must come first in this workflow.
• C is wrong because the backup is Raw, not Prepared, and validate only verifies integrity - it does not make a backup restorable.
• D is wrong because calling the backup "Prepared" is incorrect - apply-log has not been run yet.

Memory tip: Think of the backup workflow as a pipeline - Raw → Image → Prepared → Restored. A --backup-dir backup is "Raw in a box"; backupdir-to-image gets it out of the box before any further processing can happen.

No community discussion yet for this question.