A single Virtual Service is configured to listen on multiple TCP service ports with a single server pool. The administrator would like to use the simplest configuration to keep the VS port and pool…

Question

Options

• ABuild a Policy to map VS port to pool server port
• BDisable Port Translation in the VS configuration
• CBuild a Data Script to map VS port to pool server port
• DDisable Port Translation in the Pool configuration

• A
  6% (2)
• B
  3% (1)
• C
  78% (25)
• D
  13% (4)

Explanation

When a Virtual Service listens on multiple ports with a single pool, a DataScript is the simplest solution because it can dynamically read the incoming VS port at runtime (e.g., avi.pool.server_port(avi.vs.port())) and forward traffic to the pool server on that exact same port - a single line of logic handles every port the VS serves, automatically.

Why the distractors fail:

• A (Policy): A policy requires you to write an explicit rule for each VS port-to-server-port mapping, making it more verbose and harder to maintain as ports change.
• B (Disable Port Translation in VS): Toggling port translation at the VS level doesn't provide intelligent per-port mapping when multiple ports are in play - the pool's statically defined server port still takes precedence.
• D (Disable Port Translation in Pool): Pool-level port translation settings control how pool members handle ports internally, but they don't contain the logic to dynamically mirror an arbitrary incoming VS port.

Memory tip: Think of it this way - Policies are static rulebooks (one rule per port), while a DataScript is a smart forwarder that reads "whatever port the client used" and sends it straight through. One script, any number of ports.

No community discussion yet for this question.