Which two statements are true about InnoDB auto-increment locking?

A. The auto-increment lock can be a table-level lock.

B. InnoDB never uses table-level locks.

C. Some settings for innodb_autoinc_lock_mode can help reduce locking.

D. InnoDB always protects auto-increment updates with a table-level lock.

E. InnoDB does not use locks to enforce auto-increment uniqueness.

Consider the query:

Mysql> SET @run = 15;

Mysql> EXPLAIN SELECT objective, stage, COUNT (stage) FROM iteminformation

WHERE run=@run AND objective='7.1'

GROUP BY objective,stage

ORDER BY stage;

The iteminformation table has the following indexes; Mysql> SHOW INDEXES FROM iteminformation:

This query is run several times in an application with different values in the WHERE clause in a growing data set.

What is the primary improvement that can be made for this scenario?

A. Execute the run_2 index because it has caused a conflict in the choice of key for this query.

B. Drop the run_2 index because it has caused a conflict in the choice of key for this query.

C. Do not pass a user variable in the WHERE clause because it limits the ability of the optimizer to use indexes.

D. Add an index on the objective column so that is can be used in both the WHERE and GROUP BY operations.

E. Add a composite index on (run,objective,stage) to allow the query to fully utilize an index.

Consider typical High Availability (HA) solutions that do not use shared storage. Which three HA solutions do not use shared storage?

A. Mysql Replication

B. Distributed Replicated Block Device (DRBD) and Mysql

C. Windows Cluster and Mysql

D. Solaris Cluster and Mysql

E. Mysql NDB Cluster

Which three statements are characteristic of the MEMORY storage engine?

A. Each table is represented on disk as an.frm file.

B. Each table has a corresponding.MYI and .MYD file.

C. It can support foreign keys.

D. It cannot contain text or BLOB columns.

E. Table contents are not saved if the server is restarted.

F. It can support transactions

You are using CTIDS in replication. You need to skip a transaction with the CTID of aaa-bbb- ccc-ddd-eee : 3 on a slave.

Which command would you execute from a Mysql prompt?

A. STOP SLAVE; SETGTID_NEXT="aaa-bbb-ccc-ddd-eee: 3"; BEGIN; COMMIT; SET GTID_NEXT="AUTOMATIC"; START SLAVE

B. STOP SLAVE; SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE;

C. STOP SLAVE; BEGIN; SET GTID_IGNORE="aaa-bbb-ccc-ddd-eee: 3"; COMMIT; START SLAVE;

D. STOP SLAVE;

RESET SLAVE;

BEGIN;

SKIP NEXT GTID;

COMMIT;

START SLAVE;

The validate_password plugin is loaded and displays the following settings in global variables: Mysql> SHOW VARIABLES LIKE `validate_password%';

When attempting to set your password, you get the following error:

Mysql> SET PASSWORD = PASSWORD (`Hoverl@%');

ERROR 1819 (HY000): Your password does not satisfy the current policy requirements

What is the cause of the error?

A. The password is eight characters long, but needs to exceed validate_password_length to be valid.

B. All of the MEDIUM password policy requirements have not been honored.

C. The password matches a substring Hover as a dictionary word.

D. The password does not match the validate_passoword_number_count requirement.

E. There is no dictionary file defined, so password validation cannot work as expected.

Consider the three binary log files bin.00010, bin.00011, and bin.00012 from which you want to restore data.

Which method would use mysqlbinlog for greater consistency?

A. shell> mysqlbinlog bin.00010 | mysql shell> mysqlbinlog bin.00011 | mysql shell> mysqlbinlog bin.00012 | mysql

B. shell> mysqlbinlog bin.00010 bin.00011 bin.00012 | mysql

C. shell> mysqlbinlog restore bin.00010 bin.00011 bin.00012

D. shell> mysqlbinlog include-gtide=ALL bin.00010 bin.00011 bin.00012 | mysql

You want to create a temporary table named OLD_INVENTORY in the OLD_INVENTORY database on the master server. This table is not to be replicated to the slave server.

Which two changes would ensure that the temporary table does not propagate to the slave?

A. Use the replicate-do-db, -- replicate-do-table, or replicate-wild-do-table option with the value equal to OLD_INVENTORY.

B. Change the binlog_format option to ROW and restart mysqld before you create the OLD_INVENTORY table.

C. Stop SQL_THREAD on the slave until you have finished using the OLD_INVENTORY temporary table.

D. Set binlog_format=MIXED with the replicate-ignore-temp-table option.

E. Use the replicate-ignore-table option with the value equal to OLD_INENTORY.OLD_INVENTORY and restart mysqld before creating the temporary table.

What is true regarding InnoDB locking?

A. InnoDB row locks may be escalated to page or table-level locks.

B. InnoDB only uses row locks, not page or table-level locks,

C. InnoDB uses row and table-level locks, but row locks are not escalates,

D. InnoDB locks only those rows that are updated.

E. InnoDB uses row-level or table-level locks depending on the number of rows affected.

A general purpose MySQL instance is configured with the following options:

-- log-slow-queries -- long-query-time=,0001 -- log-slow-admin-queries -- general-log -- log-bin -- binlog-format=STATEMENT -- innodb-flush-log-at-trx-commit=1

Which three statements are true?

A. The General Query Log records more data than the Binary Log.

B. The binary Log records more data than the General Query Log.

C. The Slow Query Log records more data than the General Query Log.

D. The General Query Log records more data than the Slow Query Log.

E. The Slow Query Log records more data than the Binary Log.

F. The Binary Log records more data than the Slow Query Log.