At which stage during query processing does MySQL create a query's execution plan?

• A.Optimizing
• B.Parsing
• C.Executing
• D.Authorizing

Comment: *

Name: *

Email: *

Verification: *

Consider the key buffer in a MySQL server. Which two statements are true about this feature?

• A.It caches index blocks for MyISAM tables only.
• B.It caches index blocks for all storage engine tables.
• C.It is a global buffer.
• D.It is set on a per-connection basis.
• E.It caches index blocks for InnoDB tables only.

Comment: *

Name: *

Email: *

Verification: *

You are looking at these details:

Why does the message "Waiting for an event from Coordinator" show up on the slave_worker threads?

• A.The Event Schedular is not enabled on the slave host.
• B.The slave is waiting for an event to come into the relay log.
• C.The slave thread is waiting for another event to finish in another slave thread.
• D.The binary log on the master is not being updated.

Comment: *

Name: *

Email: *

Verification: *

An existing master-slave setup is currently using a delayed replication of one hour. The master has crashed and the slave must be "rolled forward" to provide all the latest data.
The SHOW SLAVE STATUSindicates these values:
RELAY_LOG_FILE=hostname-relay-bin.00004

RELAY_LOG_POS=1383

Which command set would make the slave current?

• A.STOP SLAVE; CHANGE MASTER TO RELAY_LOG_FILE = 'hostname-relay-bin.00004', RELAY_LOG_POS = 1383;
• B.STOP SLAVE; CHANGE MASTER TO MASTER_DELAY=0; START SLAVE;
• C.STOP SLAVE; SET GLOBAL master_delay=0; START SLAVE;
• D.STOP SLAVE; CHANGE MASTER TO MASTER_DELAY=0; RELAY_LOG_FILE = 'hostname- relay-bin.00004', RELAY_LOG_POS = 1383;

Comment: *

Name: *

Email: *

Verification: *

You have a MySQL replication setup and you intentionally stop the SQL thread on the slave.

What are two reasons that you may stop the SQL thread on the slave while keeping the I/O thread running?
(Choose two.)

• A.to allow a backup to be created under reduced load
• B.to prevent any transaction experiencing a deadlock
• C.to prevent schema changes from propagating to the slave before they are validated
• D.to allow for point-in-time recovery on the slave
• E.to allow the remaining events to be processed on the slave while not receiving new events from the master

Comment: *

Name: *

Email: *

Verification: *