156-915.77 · Question #159
(Topic 14) In the following cluster configuration; if you reboot sglondon_1 which device will be active when sglondon_1 is back up and running? Why?
The correct answer is D. sglondon_2 because it has highest priority. See the full explanation below for the reasoning.
Question
- (Topic 14)
In the following cluster configuration; if you reboot sglondon_1 which device will be active when sglondon_1 is back up and running? Why?
Options
- Asglondon_1 because it the first configured object with the lowest IP.
- Bsglondon_2 because sglondon_1 has highest IP.
- Csglondon_1, because it is up again, sglondon_2 took over during reboot.
- Dsglondon_2 because it has highest priority.
How the community answered
(47 responses)- A4% (2)
- B9% (4)
- C15% (7)
- D72% (34)
Community Discussion
3
Bahar F.Nov 13, 2025D is correct. In a Maestro Security Group, priority determines which member holds the active role, and the member with the highest configured priority wins, so sglondon_2 remains active even after sglondon_1 recovers from the reboot because priority does not automatically yield back to a rejoining member.
Brenda K.Nov 16, 2025Saw this exact setup on my sitting, flagged it fast, D all day, priority wins over reboot order every time. Saved two minutes for the nastier policy questions at the end.
Carlos M.Nov 20, 2025D is correct. In ClusterXL, priority is what drives the active election, not IP address or which member came up first, so sglondon_2 stays active after sglondon_1 rejoins because it holds the higher priority value. The key detail that trips people up here is that a recovered member does not automatically reclaim active status just because it is healthy again, it only becomes active if no higher-priority peer is available. Remember that for the exam, IP address is a tiebreaker only when priorities are equal.