Examice

Exam 1z0-908 All QuestionsBrowse all questions from this exam

Go to Exam

Question 7

Examine the modified output:

Seconds_Behind_ Master value is steadily growing.

What are two possible causes? (Choose two.)

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

One or more large tables do not have primary keys.

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

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

The parallel slave threads are experiencing lock contention.

Correct Answer: A, D

When the 'Seconds_Behind_Master' value is steadily growing, it indicates that the slave is unable to keep up with the master for some reason. One possible cause is that the master is too busy to transmit data quickly enough, resulting in the slave waiting for more data (option A). Another possibility is that the master is producing a large volume of events in parallel, but the slave processes them serially, causing it to fall behind (option D). These scenarios can both lead to an increase in the 'Seconds_Behind_Master' value.

Discussion

nkanike1Options: AD

Yes I agree, A & D

FelipeKOptions: AD

The correct answers are: A. 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. Explanation: A. When the "Seconds_Behind_Master" value is steadily growing, it indicates that the slave is falling behind the master because it's waiting for data from the master. This can happen if the master is busy and cannot transmit data to the slave as quickly as the slave can process it. D. If the master is producing a large volume of events (changes) in parallel, but the slave is processing them serially (one by one), it can lead to a situation where the slave falls behind the master. The slave might not be able to keep up with the incoming changes, causing the "Seconds_Behind_Master" value to increase.

MOHAMEDMOIDEEN

Read_Master_Log_Pos: Master Slave is connected.

marklvOptions: BD

Not A. The thread is normally very fast and a master can have multiple slaves. Tables not having primary keys can cause replication slowness. I have seen a master execute many queries in parallel but a slave executes them serially.

marklv

B & D, I think C may be a possible answer, but I have to think about it.