MENU
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?
Suggested Answer: A
Get Premium ACSCA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
29 comments · newest first
JO
Jolanda
11 months ago
I disagree with D, disabling authentication seems risky.
AM
Amber
11 months ago
E sounds right, cookie-based sessions are the way to go!
VA
Van
11 months ago
Wait, can you really bypass the load balancer like in B?
RE
Ressie
12 months ago
I think A is a bit overkill, honestly.
RO
Rose
12 months ago
Option C is definitely a must for sticky sessions!
BL
Blondell
1 year ago
I feel like option E is definitely related to SSO and cookie-based sessions, but I can't recall if that's the only way to achieve sticky routing.
KR
Kris
1 year ago
I’m a bit confused about the difference between hard-wiring instances and using the load balancer. Wasn't there a question about that in our review?
WE
Wenona
1 year ago
I think option C sounds familiar because we discussed load balancers needing to support sticky sessions in our last practice exam.
WE
Wendell
1 year ago
I remember something about sticky sessions being important for maintaining user state, but I'm not sure which options specifically enable that.
DA
Darci
1 year ago
Based on my understanding, Option E seems like the best solution. Enabling NTLM or Kerberos authentication with SSO will allow Share to use cookie-based sessions, which the load balancer can then use for sticky routing.
RE
Renea
1 year ago
I think the key here is that the load balancer needs to support 'sticky' sessions, so that each client always connects to the same server during their session. Option C looks like the best choice for that.
IV
Ivette
1 year ago
Okay, let's think this through step-by-step. The question is asking about enabling 'sticky' routing for HTTP requests from the Share tier to the repository tier.
HO
Hobert
1 year ago
This question seems straightforward, but I want to make sure I understand the key concepts before selecting my answers.
TE
Temeka
1 year ago
I'm a bit confused about the difference between hard-wiring instances versus using the load balancer. Can someone clarify which approach is better?
LO
Lou
1 year ago
Option D looks promising - using analogies and anecdotes to guarantee student understanding. That could be a really effective strategy, but I'll need to make sure I understand the question fully before committing to an answer.
WA
Wade
1 year ago
This is a good opportunity to demonstrate my troubleshooting skills. I'll need to consider factors like network segmentation, firewall rules, and potential misconfigurations.
AN
Annice
1 year ago
I'm leaning towards C and E as well. Disabling authentication won't solve the problem, and hard-wiring instances doesn't sound like a great solution either.
BL
Blondell
1 year ago
Haha, option D is a good way to disable authentication, but that's not going to help with sticky routing! We need to keep authentication in place.
DE
Denise
1 year ago
Option B doesn't make sense to me. Hard-wiring each Share instance to its own Alfresco instance would bypass the load balancer, which is the opposite of what we want.
MI
Millie
1 year ago
Another way is hard-wiring each /alfresco instance to its own /solr instance and using the load balancer.
JA
Jamal
1 year ago
We can enable sticky routing by configuring the load balancer to use the JSESSIONID cookie.
FA
Fausto
1 year ago
You're right. We need to ensure that the load balancer supports 'sticky' sessions.
RI
Rima
1 year ago
Option B doesn't make sense because it bypasses the load balancer.
CH
Cherrie
1 year ago
I think options C and E are the correct ways to enable sticky routing. The load balancer needs to support sticky sessions, and enabling NTLM or Kerberos authentication with SSO will allow Share to use cookie-based sessions.
CR
Crista
1 year ago
E) 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.
CR
Cristal
1 year ago
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.
RE
Reena
2 years ago
I'm not sure about the other options, but C and E make sense to me. Sticky routing is crucial for maintaining session consistency.
TA
Tamra
2 years ago
I agree with Dominque. Option E also seems like a good choice, enabling cookie-based sessions for sticky routing.
DO
Dominque
2 years ago
I think option C is the way to go. The load balancer needs to support 'sticky' sessions for consistent routing.