Your customer uses Aruba Central and ClearPass in their Aruba-powered campus network. The company is rapidly deploying branches and the CIO wants to ensure enterprise scalability for these networks…

Question

Options

• Asmart rate ports for future-proofing
• Brouting through the data center for better security
• Cmachine learning and AI-powered security assurance
• Dsingle policy enforcement point at branches

• A
  13% (4)
• B
  3% (1)
• C
  6% (2)
• D
  77% (24)

Explanation

D is correct because the Aruba Branch Gateway acts as a single policy enforcement point at each branch, pushing centrally-defined policies from Aruba Central and ClearPass out to every location automatically. As new branches are deployed, they inherit the same policy framework without requiring additional management infrastructure or licensing, directly addressing the CIO's scalability-without-extra-cost concern.

Why the distractors are wrong:

• A (smart rate ports) addresses future hardware bandwidth needs, not management scalability - it's a nice-to-have, not a solution to the CIO's operational challenge.
• B (routing through the data center) describes "hair-pinning," which increases cost and latency by backhauling branch traffic - the opposite of a scalable, cost-efficient branch model.
• C (ML/AI security assurance) is a legitimate Aruba capability (AIOps in Central), but it's not the defining Branch Gateway feature, and it doesn't specifically solve the "enterprise scalability without extra spend" requirement.

Memory tip: Match the constraint to the feature - the CIO wants scale without cost. "Single policy enforcement point" = one policy engine feeds all branches centrally, so adding branch #50 costs no more management effort than branch #5.

No community discussion yet for this question.