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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Alfresco ACSCA Exam - 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

by Devorah at Dec 08, 2023, 05:01 AM

Limited Time Offer

25%

Off

Get Premium ACSCA Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Jolanda
5 months ago
I disagree with D, disabling authentication seems risky.
upvoted 0 times
...
Amber
5 months ago
E sounds right, cookie-based sessions are the way to go!
upvoted 0 times
...
Van
5 months ago
Wait, can you really bypass the load balancer like in B?
upvoted 0 times
...
Ressie
6 months ago
I think A is a bit overkill, honestly.
upvoted 0 times
...
Rose
6 months ago
Option C is definitely a must for sticky sessions!
upvoted 0 times
...
Blondell
6 months 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.
upvoted 0 times
...
Kris
6 months 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?
upvoted 0 times
...
Wenona
7 months ago
I think option C sounds familiar because we discussed load balancers needing to support sticky sessions in our last practice exam.
upvoted 0 times
...
Wendell
7 months ago
I remember something about sticky sessions being important for maintaining user state, but I'm not sure which options specifically enable that.
upvoted 0 times
...
Darci
7 months 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.
upvoted 0 times
...
Renea
7 months 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.
upvoted 0 times
...
Ivette
7 months 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.
upvoted 0 times
...
Hobert
7 months ago
This question seems straightforward, but I want to make sure I understand the key concepts before selecting my answers.
upvoted 0 times
...
Temeka
7 months 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?
upvoted 0 times
...
Lou
7 months 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.
upvoted 0 times
...
Wade
7 months 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.
upvoted 0 times
...
Annice
11 months 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
11 months 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
11 months 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
Millie
11 months ago
Another way is hard-wiring each /alfresco instance to its own /solr instance and using the load balancer.
upvoted 0 times
...
Jamal
11 months ago
We can enable sticky routing by configuring the load balancer to use the JSESSIONID cookie.
upvoted 0 times
...
Fausto
11 months ago
You're right. We need to ensure that the load balancer supports 'sticky' sessions.
upvoted 0 times
...
Rima
11 months ago
Option B doesn't make sense because it bypasses the load balancer.
upvoted 0 times
...
...
Cherrie
12 months 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
Crista
10 months 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.
upvoted 0 times
...
Cristal
10 months 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.
upvoted 0 times
...
...
Reena
1 year 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
1 year ago
I agree with Dominque. Option E also seems like a good choice, enabling cookie-based sessions for sticky routing.
upvoted 0 times
...
Dominque
1 year 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