Oracle MySQL 5 Database Administrator Certified Professional

mysqld is the server; mysqld_safe is a shell script that invokes mysqld; mysql.server is a wrapper for
mysqld_safe. ✘ mysqld is a shell script that starts mysql.server; mysqld_safe is a shell script that invokes the server in safemode; mysql.server is the server. ✘ mysqld is the server; mysqld_safe is a shell script that invokes mysqld in safe mode, and mysql.server is awrapper for mysqld_safe. ✘ Nothing. They are symbloic links to the same file. ✔

mysqladmin shutdown ✘ mysqld_multi stop ✘ mysql shutdown ✘ mysql.server stop ✔ mysqld shutdown ✔

stdin ✘ stdout ✘ sakila.out ✘

Startup options can only be given in option files. ✘ Startup options can only be given on the command line. ✘ Startup options can only be given on the command line except for Windows Services. ✘ Startup options can be given either in option files, or as parameters on the command line. ✔ Startup options can be given either in option files, or as parameters on the command line, except forWindows services. ✔

Location of important directories and files ✘ Logging settings ✘ Backup intervals ✘ Storage Engine dependent options ✔ Performance related settings ✔

Options will not need to be specified every time the server starts. ✘ All options can be consolidated to one file and a single point of reference. ✘ Certain options can be specified only in options files but not on the command line ✘

By default, write requests (such as UPDATE and DELETE statements) take priority over read requests (such as SELECT statements). By default, read requests (such as SELECT statements) take priority over write requests (such asUPDATE and DELETE statements). With the LOW_PRIORITY option, a write request will wait for any other read request to finish. With the LOW_PRIORITY option, a read request will wait for any other write request to finish. With the HIGH_PRIORITY option, a read request will be moved ahead of other requests waiting to beexecuted.

The server will crash. ✘ An error message will be returned to the client. ✘ The server suspends that INSERT operation until space becomes available. ✘ The server suspends operations on all MyISAM tables until space becomes available. ✔

Deadlocks are possible because of the MyISAM-specific method of table-level locking. ✘ Deadlocks are not possible because of the MyISAM-specific method of table-level locking. ✘ Deadlocks are possible because of the MyISAM-specific method of row-level locking. ✘ Deadlocks are not possible because of the MyISAM-specific method of row-level locking. ✔

All rows have the same size. Rows take varying amounts of space. Rows are easy to look up. Rows cannot be looked up as efficiently. Row data usually takes up more space on disk and in memory.