Examine this list of MySQL data directory binary logs: binlog.000001 binlog.000002 ..... binlog.000289 binlog.000300 binlog.000301 binlog.index Now examine this command, which executes successfully…

Question

Options

• AAll databases are backed up to the output file.
• BAll non-active binary logs are removed from the master.
• CAll binary logs are deleted from the master.
• DAll binary logs are backed up and then deleted.
• EAll databases, excluding master metadata, are backed up to the output file.
• FAll details regarding deleted logs and master metadata are captured in the output file.

• A
  5% (2)
• B
  15% (6)
• C
  71% (29)
• D
  2% (1)
• F
  7% (3)

Explanation

--delete-master-logs works by first flushing the binary logs (creating a new active log), then issuing a PURGE BINARY LOGS command that deletes all prior logs - so C is correct because the flush-then-purge sequence eliminates every log in the list, not just the inactive ones (eliminating B). E is correct because --all-databases dumps all database content but excludes master metadata such as replication status and binary log position info from the output file - A is wrong precisely because it omits this distinction. D is wrong because binary logs are never written to the output file - only SQL database dump data is - and F is wrong because neither deleted log details nor master metadata are captured in the dump output.

Memory tip: Associate --delete-master-logs with "scorched earth" - it flushes first, then purges everything. And remember "all-databases ≠ all master metadata" - replication housekeeping data stays off the backup.

No community discussion yet for this question.