You have the following in your my.cnf configuration file:
[mysqld]
default_authentication_plugin=sha256_password
You want to create a new user who will be connecting from the IP address 192.0.2.10, and you want to use the authentication plug-in that implements SHA-256 hashing for user account passwords.
Which two statements would create a user named webdesign for this IP address with the password of imbatman using a SHA_256 password hash? (Choose two.)

• A.CREATE USER 'webdesign'@'192.0.2.10' IDENTIFIED WITH sha256_password BY 'imbatman';
• B.CREATE USER 'webdesign'@'192.0.2.10' IDENTIFIED BY SHA265 AS 'imbatman';
• C.CREATE USER 'webdesign'@'192.0.2.10' IDENTIFIED BY 'iambatman';
• D.CREATE USER 'webdesign'@'192.0.2.10' IDENTIFIED AS sha256_user WITH sha256_password
  'imbatman';
• E.CREATE USER WITH sha256_password 'sha256_user'@'192.0.2.10' IDENTIFIED AS 'webdesign' USING 'imbatman';
• F.CREATE USER 'webdesign'@'192.0.2.10' WITH mysql_native_password USING SHA265 BY
  'imbatman';

Comment: *

Name: *

Email: *

Verification: *

After analysis on the slow query log on a high-end OLTP service, the table identified in the slow queries is:

What are the two most likely reasons for the slowness given this output?

• A.The engine type is not appropriate to the application use.
• B.The User field is too long for most names.
• C.No indexes are defined.
• D.Using default values for DATETIME causes table scans.
• E.Date should be a TIMESTAMP field for better performance.

Comment: *

Name: *

Email: *

Verification: *

Examine the mydata table and SELECT statements:

You issue:
mysql> begin;
mysql> update mydata set a=0 where b=3;
How many rows are now protected by locks with the default InnoDB configuration?

• A.one row and a gap-lock
• B.five
• C.one
• D.one row and a next-key lock for supremum

Comment: *

Name: *

Email: *

Verification: *