In a level-triggered JK flip-flop, the "race-around condition" causes the output to toggle unpredictably. Under what specific conditions does this occur, and what is the standard architectural mitigation?
If the clock remains high longer than the time it takes for the output to change and feed back to the inputs, the flip-flop will continuously toggle (race around) while J=1 and K=1. A Master-Slave setup solves this by breaking the feedback loop, capturing data on one edge and updating the output on the other.