1Z0-908 · Question #7
You are upgrading a MySQL instance to the latest 8.0 version. Examine this output: You plan to add this parameter to the configuration: innodb_directories='/innodb_extras' Which statement is true?
The correct answer is B. It is not necessary because innodb_data_home_dir is already defined. Option B is correct because MySQL automatically scans directories defined by innodb_data_home_dir, innodb_undo_directory, and datadir for InnoDB tablespace files at startup - so if innodb_data_home_dir is already pointing to (or covers) /innodb_extras, adding…
Question
You are upgrading a MySQL instance to the latest 8.0 version. Examine this output:
You plan to add this parameter to the configuration: innodb_directories='/innodb_extras' Which statement is true?
Exhibit
Options
- AIt defines all innodb tablespace options relative to a starting parent directory.
- BIt is not necessary because innodb_data_home_dir is already defined.
- CIt allows scanning of other locations to discover more innodb tablespaces.
- DIt moves all innodb tablespaces to the /innodb_extras directory to enable a new
- EIt adds more temporary workspace in addition to the innodb_tmpdir location.
How the community answered
(30 responses)- B93% (28)
- C3% (1)
- D3% (1)
Explanation
Option B is correct because MySQL automatically scans directories defined by innodb_data_home_dir, innodb_undo_directory, and datadir for InnoDB tablespace files at startup - so if innodb_data_home_dir is already pointing to (or covers) /innodb_extras, adding innodb_directories='/innodb_extras' is redundant. Option A incorrectly describes innodb_data_home_dir, which is the parameter that sets a common parent path for data file locations. Option C describes what innodb_directories generally does (scanning additional locations for tablespaces), but it's wrong here because the directory is already covered by the existing configuration. Option D is wrong because innodb_directories never moves files - it only tells the server where to look. Option E is wrong because temporary tablespace workspace is controlled by innodb_tmpdir, not innodb_directories.
Memory tip: Think of innodb_directories as a "breadcrumb list" you hand MySQL so it can find tablespace files in unusual locations - but MySQL already follows crumbs left by innodb_data_home_dir, so dropping the same crumb twice does nothing.
Topics
Community Discussion
No community discussion yet for this question.
