Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

F5 Networks Exam 301b Topic 7 Question 85 Discussion

Actual exam question for F5 Networks's 301b exam
Question #: 85
Topic #: 7
[All 301b Questions]

A virtual server for a set of web services is constructed on an LTM device. The LTM Specialist has created an iRule and applied this iRule to the virtual server:

when HTTP_REQUEST {

switch [HTTP::uri] {

"/ws1/ws.jsp" {

log local0. "[HTTP::uri]-Redirected to JSP Pool"

pool JSP

}

default { log local0. "[HTTP::uri]-Redirected to Non-JSP Pool"

pool NonJSP

}

}

}

However, the iRule is NOT behaving as expected. Below is a snapshot of the log:

/WS1/ws.jsp-Redirected to JSP Pool

/WS1/ws.jsp-Redirected to JSP Pool

/WS1/ws.jsp-Redirected to JSP Pool

/WS1/WS.jsp-Redirected to Non-JSP Pool

/ws1/WS.jsp-Redirected to Non-JSP Pool

/WS1/ws.jsp-Redirected to JSP Pool

/ws1/ws.jsp-Redirected to Non-JSP Pool

What should the LTM Specialist do to resolve this?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Sabra
1 months ago
Setting the 'Case Sensitivity' option to 'None' on each pool member seems like a simple solution. That way, the iRule can match the URIs correctly.
upvoted 0 times
Arminda
1 days ago
B) Use the followinG. switch [string tolower [HTTP::uri]]
upvoted 0 times
...
Emogene
5 days ago
A) Use the followinG. switch -lc [HTTP::uri]
upvoted 0 times
...
...
Alpha
2 months ago
Haha, the LTM Specialist is probably scratching their head trying to figure this out. They need to remember that HTTP is all about case-sensitivity!
upvoted 0 times
...
Brande
2 months ago
I think the LTM Specialist should use the 'switch [string tolower [HTTP::uri]]' option to make the matching case-insensitive.
upvoted 0 times
Rueben
13 days ago
C) Set the 'Case Sensitivity' option of each member to 'None'.
upvoted 0 times
...
Kindra
17 days ago
B) Use the followinG. switch [string tolower [HTTP::uri]]
upvoted 0 times
...
Lemuel
1 months ago
A) Use the followinG. switch [string tolower [HTTP::uri]]
upvoted 0 times
...
...
Casandra
2 months ago
Looks like the iRule is case-sensitive, which is causing the inconsistent behavior. The log shows different requests being redirected to different pools.
upvoted 0 times
Valentine
11 days ago
C) Set the \'Case Sensitivity\' option of each member to \'None\'.
upvoted 0 times
...
Cristen
16 days ago
Looks like the iRule is case-sensitive, which is causing the inconsistent behavior. The log shows different requests being redirected to different pools.
upvoted 0 times
...
Jaime
23 days ago
B) Use the followinG. switch [string tolower [HTTP::uri]]
upvoted 0 times
...
Lavera
1 months ago
A) Use the followinG. switch -lc [HTTP::uri]
upvoted 0 times
...
...
Joanne
2 months ago
I'm not sure, but I think option D might also work by selecting the 'Process Case-Insensitivity' option.
upvoted 0 times
...
Ettie
2 months ago
I agree with Shawnda, using switch [string tolower [HTTP::uri]] should fix the issue.
upvoted 0 times
...
Shawnda
2 months ago
I think the LTM Specialist should choose option B.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77