Which three techniques can an operator use to scale data plane performance? (Choose three.)

Question

Options

• ABGP-based horizontal scaling of SES in an SE Group
• BNative horizontal scaling of an individual SE
• CIncrease the maximum number of Virtual Services in an SE Group.
• DVertical scaling of an individual SE's resources
• ENative horizontal scaling of SES in an SE Group
• FOSPF-based horizontal scaling of SEs in an SE Group

• A
  75% (21)
• B
  7% (2)
• D
  4% (1)
• F
  14% (4)

Explanation

In VMware NSX Advanced Load Balancer (Avi), the data plane runs on Service Engines (SEs) grouped into SE Groups. Operators scale performance through BGP-based horizontal scaling (A), which leverages BGP ECMP to distribute traffic across multiple SEs using routing; native horizontal scaling of SEs in an SE Group (E), which adds more SE instances to share the load; and increasing the maximum number of Virtual Services in an SE Group (C), which expands how many workloads the group can handle without bottlenecking. Together, these three techniques distribute and grow capacity at the group level.

The distractors fail for specific reasons: B is wrong because horizontal scaling applies to the SE Group, not to a single SE - you can't natively scale one SE "out" by itself. D (vertical scaling) adds resources like vCPUs to an individual SE, which is a valid operation but not classified as a data plane scaling technique in this context - it's resource tuning, not architectural scaling. F is wrong because Avi uses BGP, not OSPF, for routing-based horizontal scaling; OSPF has no role in SE scaling.

Memory tip: Think "BGP and Native = scale Out (horizontal); Max VSes = scale Capacity - all at the Group level, never the individual SE." If the answer involves a single SE or OSPF, eliminate it.

No community discussion yet for this question.