Covering Index — Concept Check
Questions on Covering Index. A covering index includes all columns needed for a query, eliminating the secondary lookup to the clustered index; MySQL shows "Using index" in EXPLAIN for covered queries.
Questions in this quiz
7 questions on Covering Index — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A query on the 'orders' table uses an index on (status, created_at) and selects id, status, created_at, and total. What will MySQL's EXPLAIN show?
- AExtra: Using index
- BExtra: NULL
- CExtra: Using where
- DExtra: Using filesort
2.You create an index on (customer_id, created_at, total) for a query filtering on customer_id and ordering by created_at. Why might writes slow down?
- AThe index is too wide
- BThe index is too narrow
- CThe order of columns is incorrect
- DIndexes do not affect write speed
3.A query on the 'orders' table is covered by an index, but performance is still poor. What might be the issue?
- AThe index is too narrow
- BThe data is read sequentially
- CThe query is not optimized
- DThe index is not used
4.Why would a query with 'Extra: Using index' in EXPLAIN be faster than one without it?
- AIt avoids random I/O
- BIt uses more CPU
- CIt uses less memory
- DIt skips the WHERE clause
5.A query on 'orders' uses an index on (status, created_at) but also selects 'total'. What is the consequence?
- AThe query will fail
- BThe index is ignored
- CA row lookup is needed
- DThe query is fully covered
6.What is a covering index's main advantage over a regular secondary index?
- AIt reduces index size
- BIt speeds up writes
- CIt simplifies queries
- DIt eliminates row lookups
7.A query on 'orders' uses an index on (status, created_at, total). Which part of the index design is crucial for performance?
- AColumn data types
- BOrder of columns
- CNumber of columns
- DIndex name