A.CPU utilization

B.MySQL Replication monitoring

C.MySQL Query Analysis data

D.operating system memory utilization

E.disk usage and disk characteristics including disk advisors warnings

F.network-related information and network characteristics

G.security-related advisor warnings

A.Execute SET GLOBAL log_error = '<new error log file>'.

B.Execute SET GLOBAL max_error_count = <number of messages at point to rotate>.

C.Execute SET GLOBAL expire_logs_days=0 to enforce a log rotation.

D.Rename the error log file on disk, and then execute FLUSH ERROR LOGS.

A.It connects to the master and asks it to send updates recorded in its binary logs.

B.It monitors and schedules the rotation/deletion of the binary logs.

C.It acquires a lock on the binary log for reading each event to be sent to the slave.

D.It reads the relay log and executes the events contained in them.

A.This value shows only I/O latency and is not indicative of the size of the transaction queue.

B.One or more large tables do not have primary keys.

C.The master is most probably too busy to transmit data and the slave needs to wait for more data.

D.The master is producing a large volume of events in parallel but the slave is processing them serially.

E.The parallel slave threads are experiencing lock contention.

A.Replication will fail because of inconsistent numbers in cccccccc-cccc-cccc-cccc-cccccccccccc GTIDs.

B.Replication will work.

C.Replication will fail because the slave has purged more aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa transactions than the master.

D.Replication will fail because the master has already purged transactions with cccccccc-cccc-cccc- cccc-cccccccccccc GTIDs.

E.Replication will fail because the master does not have the required transaction with bbbbbbbb-bbbb- bbbb-bbbb-bbbbbbbbbbbb GTIDs in its binary logs.