Question 240
A stack's standby control member cannot take over after a failover drill because the new member has incompatible firmware. Which failure mechanism best explains the observed behavior?
Explanation
Correct Answer
The symptoms fit this mechanism. A targeted response is to align software versions through the vendor-supported stack upgrade and member compatibility process, followed by verification that all members join the stack and leadership failover completes without losing the remaining access members.
Incorrect Answers
That explanation fits a different case, such as when a campus uses VRRP on an SVI but hosts keep targeting a physical gateway address rather than the shared virtual address. The symptoms here are better explained by control-member version mismatch prevents stable participation in the intended logical stack.
That explanation fits a different case, such as when a VSF stack has members connected in a line, so one intermember cable failure isolates the last unit. The symptoms here are better explained by control-member version mismatch prevents stable participation in the intended logical stack.
That explanation fits a different case, such as when a core switch keeps forwarding after a power supply is removed, but a maintenance exercise shows no power fault alarm reaches operations. The symptoms here are better explained by control-member version mismatch prevents stable participation in the intended logical stack.