An administrator wants to configure HTTP to HTTPS redirect policies but the HTTP policies tab is not displayed. Why did this occur?

Question

Options

• AThe TCP 80 and TCP 443 needs to be configured in the Service Port list.
• BThe Application Profile is configured as System-L4-Application.
• CA WAF policy needs to be configured.
• DThe SSL checkbox needs to be ticked in the Service Port list.

• A
  4% (1)
• B
  77% (20)
• C
  12% (3)
• D
  8% (2)

Explanation

Option B is correct because System-L4-Application is a Layer 4 (TCP/UDP) profile, which has no visibility into HTTP traffic. HTTP redirect policies are a Layer 7 feature - the system must understand the HTTP protocol to offer them, and when operating in L4 mode, the HTTP policies tab simply does not render in the UI because those options are irrelevant at that layer. To enable the HTTP policies tab, the administrator must switch to an HTTP application profile (L7), which unlocks HTTP-aware features like redirect rules.

Why the distractors are wrong:

• A - Port configuration (TCP 80/443) affects which ports the virtual service listens on, but does not control tab visibility in the UI; the profile type does.
• C - WAF policies are a separate security feature and are not a prerequisite for accessing or displaying HTTP redirect policy options.
• D - Ticking the SSL checkbox enables HTTPS on a port, but tab visibility is governed by the application profile type, not the SSL setting on the port.

Memory tip: Layer determines features - "L4 = TCP only, L7 = HTTP aware." If the profile is L4, the UI hides all HTTP-specific tabs because they literally cannot apply. When you see a missing HTTP tab, think profile type first.

No community discussion yet for this question.