Consider the CHECK TABLE command. In which two situations should this command be used? (Choose two.)

Question

Options

• Ato find out why a query takes a long time to execute on a given table
• Bto make sure a table has no structural problems
• Cto improve performance by updating index distributing statistics on InnoDB tables
• Dto repair table structure problem
• Eto make sure that no table indexes are corrupted

• A
  11% (2)
• B
  78% (14)
• C
  6% (1)
• D
  6% (1)

Explanation

CHECK TABLE is a diagnostic command that inspects a table's internal structure and verifies the integrity of its indexes - making B and E correct. When run, it reports whether the table's structure is valid and whether any indexes have become corrupted (e.g., after a crash or hardware failure).

Why the distractors are wrong:

• A is wrong - slow query analysis belongs to EXPLAIN or the slow query log, not CHECK TABLE.
• C is wrong - updating index distribution statistics is the job of ANALYZE TABLE, not CHECK TABLE.
• D is wrong - CHECK TABLE only identifies problems; fixing them requires REPAIR TABLE (MyISAM) or restoring from backup (InnoDB).

Memory tip: Think of CHECK TABLE as a doctor's checkup - it diagnoses but does not treat. Pair it mentally with its action counterparts: ANALYZE updates stats, REPAIR fixes damage, OPTIMIZE reclaims space. CHECK just reports.

No community discussion yet for this question.