What is the best method for monitoring Group Replication conflict resolution?

• A.the PERFORMANCE_SCHEMA tables
• B.the SHOW PROCESSLIST command
• C.the INNODB Lock Monitor details
• D.the SHOW STATUS command
• E.the INFORMATION_SCHEMA tables

Comment: *

Name: *

Email: *

Verification: *

You have installed the validate_passwordplug-in and set the validate_password_policyvariable.
Which validation is affected by the validate_password_policy setting?

• A.whether a new password is rejected if it contains a word found in a dictionary file.
• B.whether a new password is rejected if it contains the current user's username.
• C.the amount of delay after an incorrect password is entered
• D.the length of time before a newly created password expires

Comment: *

Name: *

Email: *

Verification: *

A simple master-to-slave replication is currently being used. This information is extracted from the SHOW SLAVE STATUSoutput:

You execute a 'SHOW CREATE TABLE mytable" on the slave:

The table mytable on the slave contains:

You have issued a STOP SLAVEcommand. You have determined that it is safe to skip the transaction in this case. One or more statements are required before you can issue a START SLAVEcommand to resolve the duplicate key error. Which statement should be used?

• A.SET GTID_NEXT="CONSISTENCY";
  BEGIN; COMMIT;
  SET GTID_NEXT="AUTOMATIC";
• B.SET GTID_NEXT="5da6b4f5-6f60-11e8-b2d6-0010e05f3e06:8";
  BEGIN; COMMIT;
  SET GTID_NEXT="AUTOMATIC";
• C.SET GLOBAL SQL_SKIP_SLAVE_COUNTER=1
• D.SET GLOBAL enforce_gtid_consistency=ON
• E.SET GTID_EXECUTED="5da6b4f5-6f60-11e8-b2d6-0010e05f3e06:8";

Comment: *

Name: *

Email: *

Verification: *

What is the best method for monitoring Group Replication conflict resolution?

• A.the PERFORMANCE_SCHEMA tables
• B.the SHOW PROCESSLIST command
• C.the INNODB Lock Monitor details
• D.the SHOW STATUS command
• E.the INFORMATION_SCHEMA tables

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.Date should be a TIMESTAMP field for better performance.
• C.No indexes are defined.
• D.Using default values for DATETIME causes table scans.
• E.The User field is too long for most names.

Comment: *

Name: *

Email: *

Verification: *