Which characteristics define Layer 7 (L7) load balancing? (Choose Two)

Question

Options

• AContent-based routing
• BEncryption of data payloads
• CApplication-aware health checks
• DTCP handshake optimizations

• A
  88% (14)
• B
  6% (1)
• D
  6% (1)

Explanation

Layer 7 (application-layer) load balancers operate with full visibility into HTTP/HTTPS traffic, enabling content-based routing (A) - directing requests based on URLs, headers, cookies, or request body - and application-aware health checks (C), which probe actual app endpoints (e.g., /health) rather than just checking if a port is open.

B is wrong because encryption/decryption (TLS termination) is a feature that can be co-located with an L7 load balancer, but it's not a defining characteristic of L7 - it's a separate concern handled at the transport layer. D is wrong because TCP handshake optimizations (e.g., connection multiplexing, SYN cookies) are Layer 4 concerns; L7 load balancers sit above the TCP layer and don't define themselves by manipulating it.

Memory tip: Think of L7 as the load balancer that can read the menu - it understands the application protocol well enough to make smart routing decisions ("send all /api traffic here, all /images traffic there") and verify that the app is actually serving correctly, not just accepting connections.

No community discussion yet for this question.