Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Alfresco Exam ACSCA Topic 1 Question 49 Discussion

Actual exam question for Alfresco's ACSCA exam
Question #: 49
Topic #: 1
[All ACSCA Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Annice
14 days 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.
upvoted 0 times
...
Blondell
15 days 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.
upvoted 0 times
...
Denise
16 days 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.
upvoted 0 times
...
Cherrie
22 days 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.
upvoted 0 times
...
Reena
2 months 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.
upvoted 0 times
...
Tamra
2 months ago
I agree with Dominque. Option E also seems like a good choice, enabling cookie-based sessions for sticky routing.
upvoted 0 times
...
Dominque
2 months ago
I think option C is the way to go. The load balancer needs to support 'sticky' sessions for consistent routing.
upvoted 0 times
...

Save Cancel