Check_Point
156-115.77 · Question #280
You run the command fw tab -t connections -s on both members in the cluster. Both members report differing values for "vals" and "peaks". Which may NOT be a reason for this difference?
The correct answer is D. Standby member does not synchronize until a failover is needed. See the full explanation below for the reasoning.
Question
You run the command fw tab -t connections -s on both members in the cluster. Both members report differing values for "vals" and "peaks". Which may NOT be a reason for this difference?
Options
- ASynchronization is not working between the two members
- BSGMs in a 61k environment only sync selective parts of the connections table.
- CHeavily used short-lived services have had synchronization disabled for performance
- DStandby member does not synchronize until a failover is needed.
How the community answered
(56 responses)- A11% (6)
- B5% (3)
- C4% (2)
- D80% (45)
Community Discussion
No community discussion yet for this question.