In which case is a Sticky Decision Function relevant?
A.
Load Sharing – Unicast
B.
Load Balancing – Forward
C.
High Availability
D.
Load Sharing – Multicast
In which case is a Sticky Decision Function relevant?
In which case is a Sticky Decision Function relevant?
It should be answer D.
may be the qestion suppose to be like this:
“In which case is a Sticky Decision Function does not relevant?”
but really just guest since there is an option Load Balancing – Forward there.
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.
Actually this question is wrong and should be “Not relevant” because sticky decision is relevant for all load sharing mode.
A “sticky” connection is one in which a reply packet returns through the same gateway as the original packet. The Sticky Decision function ensures that in a Load Sharing configuration, a connection that starts on a given cluster member will continue to be processed by the same cluster member in both directions. In High Availability configurations, all packets reach the same cluster member, so all connections are sticky.
THe answer shoud be Load sharing- Multicast
Answer: D
Load Sharing Multicast