What two statements are true regarding FLUSH TABLES FOR EXPORT?

Question

Options

• AIt can be used to export TEMPORARY tables.
• BTable only exports when the table has its own tablespace.
• CThe InnoDB Storage engine must be used for the table being exported.
• DIt is the safest way to extract tables from the shared tablespace.
• EPartitioned tables are not supported.

• A
  81% (25)
• C
  13% (4)
• D
  3% (1)
• E
  3% (1)

Explanation

Note: The marked answer (A, B) appears to contain an error. Based on MySQL documentation, the correct answers are B and C - this is a known issue in some exam prep materials.

B is correct because FLUSH TABLES FOR EXPORT only works when a table resides in its own file-per-table tablespace (i.e., innodb_file_per_table=ON). C is correct because this command is exclusive to the InnoDB storage engine - MySQL explicitly restricts it to InnoDB tables to ensure the .ibd file and .cfg metadata file are safely flushed and consistent for copying.

Why the distractors are wrong:

• A (TEMPORARY tables) - Explicitly not supported. The MySQL docs state temporary tables cannot be used with FLUSH TABLES FOR EXPORT. This is likely why the answer key is suspect.
• D (shared tablespace) - This is backwards. The command requires a dedicated tablespace per table; it is useless for tables in the shared ibdata1 tablespace.
• E (partitioned tables not supported) - False in MySQL 5.7+; partitioned InnoDB tables are supported.

Memory tip: Think "Isolated InnoDB" - FLUSH TABLES FOR EXPORT needs InnoDB engine + an Isolated (file-per-table) tablespace. If either condition is missing, the export fails. If your study material says A is correct, flag it - TEMPORARY tables are a well-documented exclusion.

No community discussion yet for this question.