Home » Cisco » 350-080 » What is the reason for this issue?
A Cisco Application Control Engine Appliance (ACE) non-admin context does not support “sticky” configuration. What is the reason for this issue?
A. ACE sticky license is not installed
B. ACE stickiness is not supported in a non-admin context
C. ACE stickiness resources are not defined in an admin context
D. Stickiness is configured properly in the CCIE virtual context
Correct Answer: C
Explanation/Reference:
Explanation:
Stickiness is an ACE feature that allows the same client to maintain multiple simultaneous or subsequent TCP or IP connections with the same real server for the duration of a session. A session is defined as a series of transactions between a client and a server over some finite period of time (from several minutes to several hours). This feature is particularly useful for e-commerce applications where a client needs to maintain multiple connections with the same server while shopping online, especially while building a shopping cart and during the checkout process.
Depending on the configured SLB policy, the ACE “sticks” a client to an appropriate server after the ACE has determined which load-balancing method to use. If the ACE determines that a client is already stuck to a particular server, then the ACE sends that client request to that server, regardless of the load-balancing criteria specified by the matched policy. If the ACE determines that the client is not stuck to a particular server, it applies the normal loadbalancing rules to the content request
Reference: http://www.cisco.com/c/en/us/td/docs/interfaces_modules/services_modules/ace/vA4_2_0/configuration/slb/guide/slbcfggd/sticky.pdf
