MENU
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?
Suggested Answer: C
Get Premium 301b Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
37 comments · newest first
GA
Galen
11 months ago
Not sure about that, seems like a workaround rather than a solution.
TO
Tora
11 months ago
I think changing the member options is a better fix.
AR
Arlean
11 months ago
Surprised the iRule didn't account for case variations.
LO
Lourdes
12 months ago
Definitely agree, using tolower would fix that!
AD
Adell
12 months ago
Looks like a case sensitivity issue with the URIs.
TH
Theresia
12 months ago
I wonder if setting the 'Case Sensitivity' option for the members would actually resolve this. It seems like a straightforward fix, but I need to double-check our notes.
DE
Desiree
1 year ago
I feel like the `switch [string tolower [HTTP::uri]]` option could be a good solution, but I can't recall if it would affect performance or not.
SO
Sommer
1 year ago
I think using `switch -lc` could help, but I'm not entirely sure if that's the best approach. We might have covered similar questions in our review.
ST
Stevie
1 year ago
I remember we discussed case sensitivity in iRules during our last practice session. It seems like the issue here might be related to that.
EL
Elise
1 year ago
Okay, I've got a few ideas on how to approach this. I'll need to experiment with the different options and see which one works best for this scenario.
LA
Latricia
1 year ago
This is a good example of why it's important to consider case-sensitivity when working with URIs. I'll need to carefully review the options and choose the best solution to ensure the iRule behaves as expected.
VA
Van
1 year ago
Ah, I think I know what the problem is. The URI matching is case-sensitive, and the requests are coming in with different casing. I'll need to find a way to make the matching case-insensitive.
VE
Verlene
1 year ago
Okay, let's see. The iRule seems to be handling the URI matching correctly, but the log output is showing some inconsistencies. I'll need to think about how to address the case-sensitivity issue.
JA
Janine
1 year ago
Hmm, this looks like a tricky one. I'll need to carefully analyze the iRule and the log output to figure out what's going on.
JA
Jackie
1 year ago
I've got this! The answer is clearly an Azure function. Functions are a great way to run small, event-driven tasks without the overhead of a full virtual machine or web app. Plus, you only pay for the compute time you use, which should help keep the costs down for this maintenance task.
FE
Fernanda
1 year ago
This seems like a straightforward question. The vendor selection is crucial for a custom-developed product, so I'll go with A - True.
RI
Rickie
1 year ago
I'm a bit confused, but I think criminal penalties are usually for laws, not governance codes... so that might not be right.
MA
Maryrose
1 year ago
I remember there being a question about automation tools in DNA Center during practice, and I think I chose Identity Services Engine then too. Not sure if that's correct though.
BE
Bernardine
1 year ago
Hmm, I'm a bit unsure about this. I'll need to review my notes on IT governance best practices.
HA
Harrison
1 year ago
I practiced questions about covenants before, and I recall that restrictive covenants limit certain company actions unless the lender approves them.
SA
Sabra
1 year 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.
TH
Thaddeus
1 year ago
C) Set the 'Case Sensitivity' option of each member to 'None'.
AR
Arminda
1 year ago
B) Use the followinG. switch [string tolower [HTTP::uri]]
EM
Emogene
1 year ago
A) Use the followinG. switch -lc [HTTP::uri]
AL
Alpha
1 year 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!
BR
Brande
1 year ago
I think the LTM Specialist should use the 'switch [string tolower [HTTP::uri]]' option to make the matching case-insensitive.
RU
Rueben
1 year ago
C) Set the 'Case Sensitivity' option of each member to 'None'.
KI
Kindra
1 year ago
B) Use the followinG. switch [string tolower [HTTP::uri]]
LE
Lemuel
1 year ago
A) Use the followinG. switch [string tolower [HTTP::uri]]
CA
Casandra
2 years ago
Looks like the iRule is case-sensitive, which is causing the inconsistent behavior. The log shows different requests being redirected to different pools.
VA
Valentine
1 year ago
C) Set the \'Case Sensitivity\' option of each member to \'None\'.
CR
Cristen
1 year ago
Looks like the iRule is case-sensitive, which is causing the inconsistent behavior. The log shows different requests being redirected to different pools.
JA
Jaime
1 year ago
B) Use the followinG. switch [string tolower [HTTP::uri]]
LA
Lavera
1 year ago
A) Use the followinG. switch -lc [HTTP::uri]
JO
Joanne
2 years ago
I'm not sure, but I think option D might also work by selecting the 'Process Case-Insensitivity' option.
ET
Ettie
2 years ago
I agree with Shawnda, using switch [string tolower [HTTP::uri]] should fix the issue.
SH
Shawnda
2 years ago
I think the LTM Specialist should choose option B.