Which three options can be configured via the HTTP Application Profile? (Choose three.)

Question

Options

• AX-Forwarded-For header
• BPROXY Protocol
• CHTTP cookie persistence
• DCaching
• ERate limiting
• FWeb Application Firewall

• A
  80% (35)
• B
  7% (3)
• E
  11% (5)
• F
  2% (1)

Explanation

An HTTP Application Profile controls how a load balancer or proxy processes HTTP-layer traffic, making it the natural home for X-Forwarded-For header insertion (A), which preserves the client's original IP as requests pass through the proxy; HTTP cookie persistence (C), which uses cookies to pin clients to specific backend servers for session continuity; and caching (D), which stores and reuses HTTP responses at the proxy layer to reduce backend load-all three are HTTP-native behaviors.

The distractors are wrong because they belong to different profile types or constructs: PROXY Protocol (B) operates at the TCP/transport layer and is configured in a network or TCP profile, not an HTTP profile. Rate limiting (E) is handled by a dedicated rate-limiting policy or separate security construct. Web Application Firewall (F) is its own independent policy object that gets attached to a virtual service, not embedded in an HTTP Application Profile.

Memory tip: Think "XCC" - the HTTP Application Profile owns the three features that are purely HTTP in nature: X-Forwarded-For, Cookie persistence, and Caching. Anything that touches TCP, security enforcement, or traffic shaping lives elsewhere.

No community discussion yet for this question.