F5
101 · Question #47
101 Question #47: Real Exam Question with Answer & Explanation
The correct answer is B: pool2. The iRule routes requests to pool2 when the URI ends with 'xt', which matches a URI such as 'file.txt' because 'txt' ends with 'xt'.
Section 2: F5 Solutions and Technology
Question
A virtual server at 10.10.1.100:80 has the rule listed below applied. when HTTP_REQUEST { if {[HTTP::uri] ends_with "htm" } { pool pool1 } elseif {[HTTP::uri] ends_with "xt" } { pool pool2 } If a
Options
- Apool1
- Bpool2
- CNone. The request will be dropped.
- DUnknown. The pool cannot be determined from the information provided.
Explanation
The iRule routes requests to pool2 when the URI ends with 'xt', which matches a URI such as 'file.txt' because 'txt' ends with 'xt'.
Common mistakes.
- A. pool1 is only selected when the URI ends with 'htm'; a URI ending in 'xt' does not satisfy that first condition and therefore bypasses pool1.
- C. The request is not dropped because the second elseif condition matches a URI ending in 'xt' and provides an explicit pool assignment, so the connection is forwarded normally.
- D. The pool can be determined from the iRule logic - the 'xt' suffix match in the elseif branch unambiguously selects pool2 for the described request.
Concept tested. F5 iRule URI string matching and pool selection
Reference. https://clouddocs.f5.com/api/irules/HTTP__uri.html
Topics
#iRules#HTTP_REQUEST#URI matching#pool selection
Community Discussion
No community discussion yet for this question.