If you are using an HTTP load-balancing mechanism in front of a clustered installation, ‘sticky’ routing must be enabled for the HTTP requests made by the Share tier to the repository tier (the /alfresco application). Select two ways to enable sticky routing?

If you are using an HTTP load-balancing mechanism in front of a clustered installation, ‘sticky’ routing must be enabled for the HTTP requests made by the Share tier to the repository tier (the /alfresco application). Select two ways to enable sticky routing?
A . Hard-wiring each /alfresco instance to its own /solr instance, and using the load balancer.
B . Hard-wiring each /share instance to its own /alfresco instance, bypassing the load balancer.
C . Ensuring that the load balancer must support ‘sticky’ sessions so that none of the clients always connects to the same server during the session.
D . Disabling alfrescoNtlm, passthru, or Kerberos authentication with SS
F . Enabling NTLM or Kerberos authentication with SSO, then Share will use cookie-based sessions and you can configure your load balancer to use sticky routing using the JSESSIONID cookie.

View Answer

Answer: B,E