101 · Question #51
A virtual server is listening at 10.10.1.100:80 and has the following iRule associated with it: when HTTP_REQUEST { if {[HTTP::uri] ends_with "txt" } { pool pool1 } elseif {[HTTP::uri] receive the req
The correct answer is D. Unknown. The pool cannot be determined from the information provided.. The iRule text provided in the question is truncated and incomplete, so the full branching logic cannot be evaluated to determine which pool handles the request.
Question
A virtual server is listening at 10.10.1.100:80 and has the following iRule associated with it:
when HTTP_REQUEST { if {[HTTP::uri] ends_with "txt" } { pool pool1 } elseif {[HTTP::uri] receive the request.
Options
- Apool1
- Bpool2
- CNone. The request will be dropped.
- DUnknown. The pool cannot be determined from the information provided.
How the community answered
(34 responses)- A15% (5)
- B29% (10)
- C9% (3)
- D47% (16)
Why each option
The iRule text provided in the question is truncated and incomplete, so the full branching logic cannot be evaluated to determine which pool handles the request.
pool1 can only be confirmed if the URI ends with 'txt', but the truncated iRule does not reveal whether the test URI meets that or any other condition.
pool2 would only be selected if the URI matches the elseif condition, which is not shown in the truncated iRule text.
Dropping the request assumes no default pool is set on the virtual server and no iRule branch matches, but neither fact can be confirmed from the incomplete information given.
The iRule as presented is cut off mid-statement after the elseif condition, meaning the complete logic, including any default pool fallback or additional conditions, is unknown. Without the full iRule and without knowing whether the virtual server itself has a default pool configured, it is impossible to determine which pool, if any, will receive a given request.
Concept tested: HTTP_REQUEST iRule URI-based pool selection logic
Source: https://clouddocs.f5.com/api/irules/HTTP__uri.html
Topics
Community Discussion
No community discussion yet for this question.