Examine this command, which executes successfully: cluster.addInstance(<user>@<host>:<port>', {recoveryMethod: clone'}) Which three statements are true? (Choose three.)

Question

Options

• AThe account used to perform this recovery needs the BACKUP_ADMIN privilege.
• BA target instance must exist, then it will be provisioned with data from an instance already in the
• CInnoDB tablespaces outside the datadir are able to be cloned.
• DIt is always slower than {recoveryMethod: `incremental'}.
• EA new instance is installed, initialized, and provisioned with data from an instance already in the
• FInnoDB redo logs must not rotate for the duration of the execution; otherwise, the recovery will fail.

• A
  63% (19)
• B
  7% (2)
• C
  10% (3)
• E
  20% (6)

Explanation

Note: The stated correct answers of A, D, F appear to be inaccurate based on MySQL Clone plugin documentation. Based on how addInstance with recoveryMethod: 'clone' actually works, the correct three statements are most likely A, B, and C.

A is correct: The clone plugin requires the BACKUP_ADMIN privilege on the donor instance. Without it, the clone operation cannot proceed.

B is correct: The target instance must already be a running MySQL server - addInstance doesn't install MySQL. Clone wipes and replaces the target's data with a physical snapshot from a donor already in the cluster. (B is cut off in the question but completes with "...in the cluster.")

C is correct: Since MySQL 8.0.17+, the clone plugin can copy InnoDB tablespaces stored outside the data directory (external tablespaces using absolute paths), making C true.

Why D is wrong: Clone is not always slower than incremental. For instances missing many transactions, clone (one full copy) can actually be faster than incremental (replaying a long binary log chain). "Always" makes this false.

Why E is wrong: Clone does not install a fresh MySQL instance. The target server must already exist and be running - clone only replaces the data, not the software.

Why F is wrong: InnoDB redo log rotation does not cause clone to fail. The clone plugin is designed to handle redo log rotation during execution. This statement confuses redo logs with binary logs (which are relevant to incremental recovery).

Memory tip: Think of clone as "photocopy the donor's entire filing cabinet into an existing empty cabinet." The cabinet (MySQL server) must already exist (B), you need admin rights to copy (A), and everything including off-site files gets copied (C).

No community discussion yet for this question.