Which statement is true in relation to native scale out?

Question

Options

• AScaling out has no impact on SSL/TLS processing capacity because SSL processing is handled
• BA large volume of client uploads is not a good use case for Scale Out because of packet-per-
• CThe scaling out process is disruptive to existing connections because existing flows are
• DLoad will be evenly balanced across all Service Engines because traffic is balanced on a per-

• B
  4% (1)
• C
  87% (20)
• D
  9% (2)

Explanation

Option C is correct because when native scale out occurs - adding a new Service Engine (SE) to handle increased load - the redistribution of traffic across SEs forces existing flows/connections to be reset or reestablished, making the process inherently disruptive to in-flight sessions.

Why the distractors are wrong:

• A is wrong: Scaling out does increase SSL/TLS capacity, because each additional SE independently handles SSL processing - so more SEs means more SSL throughput.
• B is wrong: High-volume client uploads are actually a good use case for scale out, since distributing upload traffic across multiple SEs reduces per-SE load and increases aggregate throughput.
• D is wrong: Traffic is not evenly distributed across all SEs; Avi's native scale out uses flow-based (connection hash) distribution, which can result in uneven load across SEs depending on traffic patterns.

Memory tip: Think "Scale Out = Session Ouch" - the trade-off of gaining capacity by adding SEs is that existing connections take the hit and must be re-established.

No community discussion yet for this question.