You must run multiple instances of MySQL Server on a single host. Which three methods are supported? (Choose three.)

Question

Options

• ARun MySQL Server docker containers.
• BUse systemd with different settings for each instance.
• CUse system tools to lock each instance to its own CPU.
• DStart mysqld or mysqld_safe using different option files for each instance.
• ERun mysqld with --datadir defined for each instance.
• FUse resource groups to lock different instances on separate CPUs.

• A
  12% (5)
• B
  81% (34)
• C
  5% (2)
• F
  2% (1)

Explanation

Running multiple MySQL instances on a single host is officially supported through three native mechanisms: systemd (B) allows you to create separate unit files with distinct port, socket, and datadir settings per instance; different option files (D) let you launch mysqld or mysqld_safe with --defaults-file=/path/to/my_instanceN.cnf, each defining unique ports and directories; and --datadir (E) is the minimum required differentiator - each instance must have its own data directory to avoid conflicts, and this flag sets it at startup.

Distractors explained:

• A (Docker) is excluded because the exam tests MySQL's built-in multi-instance support as documented in the MySQL manual - Docker is a third-party containerization layer, not a MySQL Server feature.
• C (CPU locking via system tools) is irrelevant to running multiple instances - CPU affinity doesn't create or isolate MySQL instances, it just controls scheduling.
• F (Resource groups) operate within a single MySQL instance to allocate CPU threads to workloads; they cannot separate distinct server instances.

Memory tip: Think "DOE" - Different option files, Own data directory (--datadir), and systemd Entries - these are MySQL's three native, documented ways to run parallel instances without virtualization.

No community discussion yet for this question.