1Z0-873 MySQL DBA Exam - Part I

Number: 1Z0-873 Passing Score: 800 Time Limit: 120 min File Version: 2.0 MySQL 5 Database Administrator Certified Professional Exam, Part I Exam Code: 1Z0-873 Unless another source is given, solution comments are quotes from: MySQL 5 Certification Study Guide By Paul DuBois, Stefan Hinz, Carsten Pedersen (Pub Date: August 24, 2005) In fact, virtually all correct answers are a paraphrase or even a quote of a statement made somewhere in the Certification Study Guide. Exam Topics Section 1: MySQL Architecture (10%) Client/Server Overview Communication Protocols The SQL Parser and Storage Engine Tiers How MySQL Uses Disk Space How MySQL Uses Memory Section 2: Starting, Stopping, and Configuring MySQL (20%) Types of MySQL Distributions Starting and Stopping MySQL Server on Windows Starting and Stopping MySQL Server on Unix Runtime MySQL Configuration Log and Status Files Loading Time Zone Tables Security-Related Configuration Setting the Default SQL Mode Upgrading MySQL Section 3: Client Programs for DBA Work (5%) Overview of Administrative Clients mysql mysqladmin mysqlimport mysqldump Client Program Limitations Section 4: Character Set Support (5%) Performance Issues Choosing Data Types for Character Columns Section 5: Locking (10%) Locking Concepts Explicit Table Locking Advisory Locking Section 6: Storage Engines (20%) MySQL Storage Engines The MyISAM Engine The MERGE Engine The InnoDB Engine The MEMORY Engine The FEDERATED Engine The Cluster Storage Engine Other Storage Engines Section 7: Data (Table) Maintenance (10%) Types of Table Maintenance Operations SQL Statements for Table Maintenance Client and Utility Programs for Table Maintenance Repairing InnoDB Tables

Enabling MyISAM Auto-Repair Section 8: The INFORMATION_SCHEMA Database (5%) INFORMATION_SCHEMA Access Syntax INFORMATION_SCHEMA Versus SHOW Limitations of INFORMATION_SCHEMA Section 9: Data Backup and Recovery Methods (15%) Introduction Binary Versus Textual Backups Making Binary Backups Making Text Backups Backing Up Log and Status Files Replication as an Aid to Backup MySQL Cluster as Disaster Prevention Data Recovery

Exam A QUESTION 1 Which one of the following statements can be used to start MySQL 5.0 manually from the command line on windows? A. C:\> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqladmin -u root start B. C:\> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld C. C:\> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysql_start Correct Answer: B Section: (none) Explanation Explanation/Reference: QUESTION 2 Another user has issued LOCK TABLES pets READ You can... A. B. C. D. Update table pets SELECT from table pets UPDATE and SELECT from table pets None of the above

Correct Answer: B Section: (none) Explanation Explanation/Reference: QUESTION 3 Which of the following statements are true for locks established by the InnoDB storage engine? A. B. C. D. It sometimes escalates locks to page level. It sometimes escalates locks to table level. It sometimes escalates locks to page or table level. It never escalates locks to page or table level.

Correct Answer: D Section: (none) Explanation Explanation/Reference: 29.4.4. During the course of a transaction, InnoDB may acquire row locks as it discovers them to be necessary. However, it never escalates a lock (for example, by converting it to a page lock or table lock). This keeps lock contention to a minimum and improves concurrency. QUESTION 4 Which of the following is true for how the InnoDB storage engine uses diskspace? A. It stores its data, index and undo information all in its own tablespace. B. It stores its data in .MYD files, in the respective database directory, and its index and undo information in its own tablespace. C. It stores its data and index in .MYD and .MYI files, in the respective database directory, and undo information in its own tablespace. D. It stores its data, index and undo information in .MYD and .MYI files, in the respective database directory.

Correct Answer: A Section: (none) Explanation Explanation/Reference: 29.2. The MyISAM Engine On disk, MySQL represents each MyISAM table using three files: a format file that stores the definition of the table structure, a data file that stores the contents of table rows, and an index file that stores any indexes on the table. These files are distinguished from one another by their suffixes. For example, the format, data, and index files for a table named mytable are called mytable.frm , mytable.MYD , and mytable.MYI . 29.4.1. The InnoDB Tablespace and Logs Each InnoDB table has a format ( .frm) file in the database directory of the database to which the table belongs. This is the same as tables managed by any other MySQL storage engine, such as MyISAM. However, InnoDB manages table contents (data rows and indexes) on disk differently than does the MyISAM engine. By default, InnoDB uses a shared "tablespace," which is one or more files that form a single logical storage area. All InnoDB tables are stored together within the tablespace. There are no table-specific data files or index files for InnoDB the way there are for MyISAM tables. The tablespace also contains a rollback segment. As transactions modify rows, undo log information is stored in the rollback segment. This information is used to roll back failed transactions. QUESTION 5 Which of the following is true for the command-line programs mysqlcheck and myisamchk? A. mysqlcheck must run on the server to perform checks and repairs and myisamchk can perform checks and repairs on a remote server. B. mysqlcheck can perform checks and repairs on a remote server, and myisamchk must run on the server. C. Both mysqlcheck and myisamchk can perform checks and repairs on a remote server. D. Neither mysqlcheck or myisamchk can perform checks and repairs on a remote server. Correct Answer: B Section: (none) Explanation Explanation/Reference: 30.3. The myisamchk utility for MyISAM tables also performs table maintenance. However, it takes a different approach from MySQL Administrator and mysqlcheck . Rather than sending SQL statements to the server, myisamchk directly reads and modified the table files. For this reason, it's necessary when using myisamchk to ensure that the server does not access the tables at the same time.