1Z0-888 · Question #73
Which statement is correct about how InnoDB storage engine uses disk space?
The correct answer is E. It stores data, index and undo information in tablespace file(s). E is correct because InnoDB is a tablespace-based storage engine - it consolidates data, indexes, and undo information together inside tablespace files (typically ibdata1 for the system tablespace and .ibd files per table when innodb_file_per_table is enabled). Options A, B…
Question
Options
- AIt stores data in .MYD files and its index and undo information in the common tablespace.
- BIt stores data in .MYD files, index information in .MYI files, and undo information in the common tablespace.
- CIt stores its data in tablespace file(s). Index and data dictionary details are stored in .FRM files.
- DIt stores its data, index and undo information in .MYD and .MYI files.
- EIt stores data, index and undo information in tablespace file(s).
How the community answered
(29 responses)- A3% (1)
- B7% (2)
- E90% (26)
Explanation
E is correct because InnoDB is a tablespace-based storage engine - it consolidates data, indexes, and undo information together inside tablespace files (typically ibdata1 for the system tablespace and .ibd files per table when innodb_file_per_table is enabled).
Options A, B, and D are wrong because .MYD (data) and .MYI (index) files belong to the MyISAM engine, not InnoDB - a common distractor since both are major MySQL storage engines. Option C is a partial trap: .FRM files historically stored table definitions (data dictionary metadata) in older MySQL versions, but InnoDB's actual data and indexes still live in tablespace files, not .FRM files.
Memory tip: Think of InnoDB as "everything in one house" (tablespace files), while MyISAM keeps data and indexes in separate files (.MYD and .MYI). If you see .MYD/.MYI in any answer about InnoDB, it's automatically wrong.
Topics
Community Discussion
No community discussion yet for this question.