156-915.71 · Question #165
The following is cphaprob state command output from one New Mode High Availability ClusterXL cluster member:Which member will be active after member 192.168.1.2 fails over and is rebooted? Check…
The correct answer is B. 192.168.1.1. See the full explanation below for the reasoning.
Question
The following is cphaprob state command output from one New Mode High Availability ClusterXL cluster member:Which member will be active after member 192.168.1.2 fails over and is rebooted? Check Point 156-915.71 Exam
Exhibit
Options
- ABoth members' state will be collision.
- B192.168.1.1
- C192.168.1.2
- DBoth members' state will be active.
How the community answered
(47 responses)- A4% (2)
- B74% (35)
- C9% (4)
- D13% (6)
Community Discussion
5
Hiroshi T.Apr 6, 2026The correct answer is B, 192.168.1.1. In ClusterXL New Mode High Availability, the Check Point ClusterXL Administration Guide is explicit that when a failed member recovers and rejoins the cluster after a reboot, it comes back in standby state and does not preempt the member that took over during the outage. So once 192.168.1.2 fails and 192.168.1.1 assumes the active role, 192.168.1.1 holds that role even after 192.168.1.2 finishes rebooting and rejoins. Options A and D describe collision and dual-active states, which only occur under specific misconfiguration or split-brain conditions, not a normal failover-and-recovery cycle. Option C would require preemption behavior, which is a feature of Load Sharing mode, not New Mode HA.
Orla P.Apr 7, 2026Hiroshi nailed the core of it, though it is worth noting that if you have sticky decision enabled and the original active member comes back, some older gateway versions have surprised people with a brief negotiation window where the cluster mask flickers before settling, so always worth confirming your CCP timeout values in cphaconf are where you expect them after any failover drill.
Viktor S.Apr 24, 2026Look at the cphaprob output and stop guessing. When 192.168.1.2 reboots, it comes back and sees itself as the higher-priority member, so it preempts 192.168.1.1 and reclaims the active role, that is exactly what New Mode HA is designed to do when priority-based preemption is in play. People keep picking B because they think the surviving member just stays active forever, but that logic belongs to Legacy mode, not New Mode, and conflating the two on this exam will cost you. The whole point of knowing which member has higher weight in the cluster is to understand who wins when they both come back healthy, and if the output shows 192.168.1.2 with the higher number, it is taking back active on reboot, full stop. Stop memorizing "failover goes to standby" as a universal rule and actually read what the state table is telling you.
Hiroshi T.Apr 26, 2026Viktor, the Check Point ClusterXL Administration Guide specifies that in New Mode, the recovering member rejoins as standby by default and does not preempt the current active member unless you have explicitly enabled the Priority Based Preemption setting, so 192.168.1.1 stays active and B is correct.
Orla P.Apr 14, 2026That "collision" trap is classic misdirection, 192.168.1.1 holds active after the reboot.