nerdexam
F5

101 · Question #73

Which action CANNOT be performed by an iRule?

The correct answer is C. Chang the virtual server's default pool.. iRules can influence traffic dynamically at runtime but cannot modify a virtual server's static configuration properties such as its default pool assignment.

Section 2: F5 Solutions and Technology

Question

Which action CANNOT be performed by an iRule?

Options

  • ADirect a connection request to a specific pool.
  • BSubstitute a server's response with alternate data.
  • CChang the virtual server's default pool.
  • DDirect a client's request to a pool based on the client's browser's language.
  • ELimit a given client to a set amount of bandwidth.
  • FDiscard a client before connecting to a server.

How the community answered

(21 responses)
  • A
    5% (1)
  • C
    71% (15)
  • D
    14% (3)
  • E
    10% (2)

Why each option

iRules can influence traffic dynamically at runtime but cannot modify a virtual server's static configuration properties such as its default pool assignment.

ADirect a connection request to a specific pool.

iRules use the 'pool' command within events like HTTP_REQUEST to direct individual connections to a specific pool.

BSubstitute a server's response with alternate data.

iRules use HTTP::respond to intercept a server response and replace it with alternate content before it reaches the client.

CChang the virtual server's default pool.Correct

iRules operate at the event and traffic level using commands like 'pool' to select a pool for a specific connection, but this selection is ephemeral and per-connection only. Permanently changing the virtual server's configured default pool is a static configuration action that must be performed through tmsh or the GUI, not through runtime iRule scripting.

DDirect a client's request to a pool based on the client's browser's language.

iRules can inspect the HTTP Accept-Language header during HTTP_REQUEST events to route requests based on the client browser's configured language.

ELimit a given client to a set amount of bandwidth.

iRules can reference and apply bandwidth policies to a flow, allowing per-client throughput limits to be enforced at runtime.

FDiscard a client before connecting to a server.

iRules use the 'reject' or 'drop' commands within CLIENT_ACCEPTED or HTTP_REQUEST events to discard client connections before any server-side connection is established.

Concept tested: F5 iRule capabilities and limitations

Source: https://techdocs.f5.com/en-us/bigip-17-1-0/irules-reference.html

Topics

#iRules#limitations#default pool#virtual server

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 101 Practice