Selected Answer: D Active and Standby Switch Election and Reelection All stack members are eligible to be the active switch or the standby switch. If the active switch becomes unavailable, the standby switch becomes the active switch. An active switch keeps its role unless one of these events happens: The switch stack is reset. The active switch is removed from the switch stack. The active switch is reset or powered off. The active switch fails. The switch stack membership is increased by adding powered-on standalone switches or switch stacks. The active switch is elected or reelected based on one of these factors and in the order listed: The switch that is currently the active switch. The switch with the highest stack member priority value

Selected Answer: D even if you adjust the priority or add a higher priority member to the stack you still need to reboot the stack to change the election, so the correct answer is D.

Jason, it looks like based on this answer it could also be A and D

Selected Answer: A I think it should be A, based on https://www.cisco.com/c/en/us/support/docs/switches/catalyst-3750-series-switches/71925-cat3750-create-switch-stks.html#anc16 So, in D by default when it is reseted it meand that election will be and there is a chance for the primary be elected again or not, but if you add a new node with higher priority it means 2 things: 1)it will be rebooted anyway 2)based on priority value the new memeber will be primary

Thank you Jason

Selected Answer: A Let's see what happens after A and after D. A. when a switch with a higher priority is added to the stack => election is triggered, and the stack member with the higher priority becomes the new primary D. when the stack primary is reset => election is triggered, and the current stack primary gets to be reelected https://www.cisco.com/c/en/us/support/docs/switches/catalyst-3750-series-switches/71925-cat3750-create-switch-stks.html#anc16 https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3850/software/release/3se/ha_stack_manager/configuration_guide/b_hastck_3se_3850_cg/b_hastck_3se_3850_cg_chapter_010.html The primary is only change after answer A), otherwise the current primary keeps its role.

Selected Answer: A I am having trouble with answer D, everyone seems to prefer it but by resetting the stack, the same master could be re-elected, leaving no change. A definitely makes the current master/active switch lose its master role. A reboot may happen on certain models when a higher priority switch is added to the stack. Why are Cisco putting in so many tricky questions, it all depends on certain circumstances. In this case, I go with A.

Selected Answer: D No preemption so no active change without the primary being reset.

answer C

Adding a new member with higher priority is definite. The current active will lose that role permanently. In D, after the reboot, the active will take back its role after reelection. I believe it's A too, but it's one of those questions...

If you reset/reboot only the primary switch in a switch stack, then, while the primary switch is rebooting, the remaining switches in the stack will have to elect a new primary switch, which would most likely be the switch that is serving as the standby switch.

B. When a stack member fails. In a Cisco StackWise stack, the StackWise primary switch is the designated master switch that handles certain control plane functions and provides stack-wide coordination. If the StackWise primary switch fails or becomes unreachable, the stack will automatically elect a new StackWise primary switch from the remaining stack members. This keeps the stack operation continuous and resilient. Therefore, option B is the correct answer. The StackWise primary switch loses its role when a stack member fails.

Selected Answer: A As per Cisco documentation: Note: If you reset the stack primary, it would reset the whole stack. Which means the original stack primary would more than likely be elected as the primary again. To add a switch, as a primary, to a stack, complete these steps: Change the priority value of the switch to be added to a value greater than the highest priority of the stack. With the new switch powered on, connect the StackWise ports of the switch to the stack. The election for the stack primary occurs, and the new switch is elected as the primary since it has the highest priority value. The members of the previous stack reboot themselves to join the new stack. So D could be true, but I think based on the documentation that A is the best answer.

https://community.cisco.com/t5/switching/stack-priority/td-p/1783919 D is the correct.

The re-election of a primary switch in a Cisco StackWise stack follows a specific sequence of events that make the switch lose its primary role. Here’s the usual order: 1. **When the stack primary is reset** (D): This is the most direct event that makes the primary switch lose its role, because it takes the primary switch offline. 2. **When a switch with a higher priority is added to the stack** (A): Adding a new switch with a higher priority can start the re-election process. However, the new switch has to be integrated into the stack and recognized before it can take over the primary role. 3. **When the priority value of a stack member is changed to a higher value** (C): Changing the priority value of an existing stack member to a higher value can make it the primary switch. This change takes effect after the next stack election process, which may happen immediately or during the next stack event.

Selected Answer: D When we add another switch to the stack with higher priority, it will not take effect until we reload the switch, so that's why the answer is D

Selected Answer: D In Cisco StackWise, the primary (active) switch keeps its role unless a specific event forces a re-election. A role change happens when the primary switch is rebooted or reset, which triggers a new election among the other switches in the stack.