when a slave receives a change from the master, it is processed first, and then recorded in the relay log.

It maintains a record of available master binary logs and the current executed log position.

It stores changes on the master, and relays them to the slave.

When a slave receives a change from the master, it is recorded in the relay log first and processed later.

When ‘erika’@’localhost’ tries to log in with the MySQL command-line client, the user will have to change the password before seeing the mysql > prompt.

When ‘erika’@’localhost’ tries to log in with the MySQL command-line client, the user will not be permitted to log in because the password is expired.

When ‘erika’@’localhost’ tries to log in with the MySQL command-line client, the user will be permitted to log in but will not be able to issue ant statements until the user changes the password.

You receive a syntax error that indicates that you cannot set a password and expire it at the same time.

The ‘adam’ user must also have SINGLE TRANSACTION global grant to take a consistent backup.

The ‘adam’ user needs the PROCESS privilege to be able to take a consistent backup while other users are connected.

The ‘adam’ user must have the SUPER privilege in order to take data backups.

The ‘adam’ user must also have SELECT on the football database for backup to work.

The slave has two intermediate relay slaves connected to it.

The slave is configured with slave_parallel_workers = 4

At most, two schemas are being updates concurrently.

THREAD_ID 21 has stopped running.

The slave cannot process the relay log fast enough to use all threads.

The server needs more cores to use all slave threads.

Both the affected transactions will be rolled back.

The affected transactions wait for innodb_lock_wait_timeout seconds, and then roll back.

One of the affected transactions will be rolled back, the other is allowed to proceed.

The transaction isolation level determines which transaction is rolled back.

The innodb_locks_unsafe_for_binlog setting determines which transaction is rolled back.

whether a new password is rejected if it contains a word found in a dictionary file.

whether a new password is rejected if it contains the current user’s username.

the amount of delay after an incorrect password is entered

the length of time before a newly created password expires

InnoDB never uses table-level locks.

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

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

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

Some settings for innodb_autoinc_lock_mode can help reduce locking.