MYSQL MySQL 5.0 Database Administrator Certified Professional Exam, Part I Sample Questions:

1. Which of the following package types are provided specifically for UNIX-style OS installations?

A) Essentials
B) Source
C) tar-packaged binary
D) RPM

2. LOCK IN SHARE MODE should be used...

A) When you need a lock that allows other transactions to read, update and delete the same locked data.
B) When you need a lock that allows other transactions to read the same data, but not update or delete until released.
C) When you need a lock that does not allow other transactions to read, update or delete the same data until released.

3. Which of the following correctly defines dirty reads, non-repeatable reads and phantom row?

A) A phantom is a read by one transaction of uncommitted changes made by another transaction.
B) A phantom is a row that appears where it was not visible before.
C) A non-repeatable read occurs when a transaction performs the same retrieval twice but gets a differentresult each time.
D) A dirty read is a read by one transaction of uncommitted changes made by another transaction.
E) A dirty read is a read by one transaction of its uncommitted changes.
F) A non-repeatable read is a row that appears where it was not visible before.

4. Which of the following statements is true for mysqldump?

A) It can dump data on both local and remote servers.
B) It can dump data only on the local server.
C) It can dump data only on remote servers.

5. Which of the following statements are true for MyISAM tables?

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

Solutions: