In which case is a Sticky Decision Function relevant?
A.
Load Balancing – Forward
B.
High Availability
C.
Load Sharing – Multicast
D.
Load Sharing – Unicast
In which case is a Sticky Decision Function relevant?
In which case is a Sticky Decision Function relevant?
A.
Load Balancing – Forward
B.
High Availability
C.
Load Sharing – Multicast
D.
Load Sharing – Unicast
Again: Older discussions conclude that C) Load Sharing – MC is the right answer.
Yeah, looks like C
I agree its C – sk42359
No, the answer really is B.
From CP_R77_ClusterXL_AdminGuide, chapter 4:
“A connection is considered sticky when all of its packets are handled, in either direction, by a single cluster member. This is the case in High Availability mode, where all connections are routed through the same cluster member, and hence, sticky.”
if we continue that paragraph… “In Load Sharing mode, however, there are cases where it is necessary to ensure that a connection that starts on a specific cluster member will continue to be processed by the same cluster member in both
directions. To that end, certain connections can be made sticky by enabling the Sticky Decision Function.”
Sticky decisions are only relevant when there is more than one path, its function is to ensure a single path. I’m confident its not HA, definitely load-sharing – not sure which but MC seems to make the most sense.
Since I could not find reference to it I would say that this question should be either “NOT relevant” or this is multiple answer question where C and D would be selected.
Sticky decision seems to be valid for both Unicast and Multicast.
Im almost agree with you Vlad, but, Maybe is “relevant” in LS Multicast mode, Why, because when you have LS Unicast , the pivot is the one which will manage and assing the connections but, LS MC it doesnt have a “master”, only the algorithm.
Thats an opinion.
Saludos.
We don’t care about sticky in HA, it’s already there. Of course should be LS MC. Maybe the question is translated to English from another language 😀 Question is what we should choose on exam?
As with all tests when no answer seems to stand out, the correct test answer is the one that is referenced in the vendors documentation. On the exam, I will therefore choose B (same as Pacman).
B. High Availability
I agree with jason, in https://sc1.checkpoint.com/documents/R76/CP_R76_ClusterXL_AdminGuide/7290.htm says:
Introduction to Sticky Connections
A connection is considered sticky when all of its packets are handled, in either direction, by a single cluster member. This is the case in High Availability mode, where all connections are routed through the same cluster member, and hence, sticky. This is also the case in Load Sharing mode when there are no VPN peers, static NAT rules or SIP.
In Load Sharing mode, however, there are cases where it is necessary to ensure that a connection that starts on a specific cluster member will continue to be processed by the same cluster member in both directions. To that end, certain connections can be made sticky by enabling the Sticky Decision Function.
HA mode is stick by itself, only one cluster member is active, you really don’t need a SDF. Only for LS a SDF is needed.
The question was not in wich case you’ll have to configure, the question is where the technology is relevant. So, it is MORE relevant in HA or LS? Think.
It’s more relevant where it’s more necessary, as to HA it’s already configured, it’s more relevant in LS MC.
Do you agree?
I would go for C
Load Sharing – Multi Cast