One of the limitations in deploying Check Point CloudGuard Cluster High Availability is that:

Question

Options

• AState synchronization is required and must be done ONLY on a dedicated link
• BHigh Availability configurations support only two Security Gateway Members
• CHigh Availability configurations support only three Security Gateway members
• DVMAC mode is mandatory for all cluster interfaces

• A
  3% (1)
• B
  86% (30)
• C
  3% (1)
• D
  9% (3)

Explanation

Check Point CloudGuard Cluster High Availability is architecturally limited to two Security Gateway members - an active and a standby node. This is a fundamental design constraint of the HA (as opposed to Load Sharing) clustering mode, which is built around a simple active/passive failover model.

Why the distractors are wrong:

• A is incorrect because state synchronization can run over a dedicated link or a shared interface - a dedicated sync link is recommended best practice but not mandatory.
• C is wrong on the number; HA supports two members, not three (three-member clusters are associated with Load Sharing configurations in some contexts, but even then the architecture differs).
• D is incorrect because VMAC mode is optional, not mandatory - it's a feature that assigns a virtual MAC address to cluster interfaces to simplify failover, but clusters can operate without it.

Memory tip: Think "HA = a pair" - High Availability implies exactly one backup for one active node, giving you a pair (two) members. If you need more than two, you're moving into Load Sharing territory, not pure HA.

No community discussion yet for this question.