156-315.81.20 ClusterXL and VRRP High Availability Practice Question
A security administrator is deploying a new ClusterXL High Availability cluster with two members. The administrator wants to ensure that if the standby member takes over as Active, it will automatically return to Standby once the original active member recovers. Which ClusterXL feature must be enabled?
⚠ Common exam trap
The trap here is assuming that state synchronization alone will cause the original active member to reclaim its role, when preemption is the setting that governs failback.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Preemption
Preemption enables a recovering member to take back the Active role based on its configured priority. In a High Availability cluster, the member with the highest priority becomes Active when it is available. If preemption is enabled, the standby member that assumed Active will step down once the original member recovers and rejoins the cluster, restoring the intended active/standby arrangement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Preemption
Why this is correct
Preemption is the ClusterXL feature that allows a recovering member with a higher priority to reclaim the Active role. When enabled, the standby member that took over will yield back to the original active member once it is healthy again. Without preemption, the new active member would continue to serve as Active even after the original member recovers.
- ✗
Load Sharing
Why it's wrong here
Load Sharing is a ClusterXL mode where multiple members actively process traffic simultaneously. It is not a feature that controls failback after a failover. Enabling Load Sharing would change the cluster's operating mode but would not cause a recovering member to automatically regain the Active role in an HA configuration.
- ✗
Delayed Failover
Why it's wrong here
Delayed Failover is not a standard ClusterXL feature. ClusterXL provides failover mechanisms, but there is no setting called Delayed Failover that controls the return of the Active role. The correct feature for automatic failback is preemption, which is configured in the cluster object properties.
- ✗
State Synchronization
Why it's wrong here
State Synchronization ensures that kernel tables and connection states are replicated to standby members. It is essential for seamless failover but does not dictate which member becomes Active after recovery. Even with synchronization enabled, the recovering member will not automatically reclaim the Active role unless preemption is configured.
About these practice questions
This 156-315.81.20 question is part of Courseiva's 210-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Check Point exam blueprint
This 156-315.81.20 practice question is part of Courseiva's free Check Point certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 156-315.81.20 exam.