The /myfolder/my.cnf file has option set: [mysqld] skip-log-bin /myfolder2/my.cnf has this option set: [mysqld] log-bin = /valid/path/to/mysqlbinlog All mentioned paths are accessible to the account…

Question

Options

• AMySQL starts and Binary Logging is enabled.
• BMySQL fails to start due to the conflicting options in the configuration files.
• CMySQL fails to start due to conflicting options on the command line.
• DMySQL starts but Binary Logging is disabled.

• A
  31% (8)
• B
  19% (5)
• C
  42% (11)
• D
  8% (2)

Explanation

Using both --defaults-file and --defaults-extra-file on the same command line is illegal in MySQL - these two options are mutually exclusive, and MySQL will throw an error and refuse to start before it ever reads either configuration file. The content of the files (skip-log-bin vs. log-bin) is irrelevant because the process never gets that far.

Why the distractors fail:

• A & D are wrong because MySQL never starts at all - no binary logging state (enabled or disabled) is reached.
• B is the tricky one: the failure is not caused by conflicting settings inside the files. The two files, taken individually, contain perfectly valid options. The problem is entirely on the command line, not in the file contents.

Memory tip: Think of --defaults-file as "exclusive mode" - it tells MySQL "use only this file, nothing else." Pairing it with --defaults-extra-file ("also read this extra file") is a direct contradiction that MySQL rejects at startup. If you need multiple config files, use --defaults-file for one and include the second via !include or !includedir directives inside that file.

No community discussion yet for this question.