A company has several use cases for using its AOS-CX switches' HPE Aruba Networking Network Analytics Engine (NAE). What is one guideline to keep in mind as you plan?

Question

Options

• AEach switch model has a maximum number of supported monitors, and one agent might have
• BYou can install multiple scripts on a switch, but you can deploy only one agent per script.
• CThe switch will permit you to deploy as many NAE agents as you want, but they might degrade the
• DWhen you use custom scripts, you can create as many agents from each script as you want.

• A
  88% (22)
• C
  4% (1)
• D
  8% (2)

Explanation

Option A is correct because HPE Aruba AOS-CX switches enforce a per-model limit on the number of NAE monitors, and since a single agent can consume multiple monitor slots, you must plan your agent deployment carefully to avoid hitting that ceiling - this is a critical capacity-planning consideration before deploying NAE at scale.

Why the distractors are wrong:

• B reverses reality - you can deploy multiple agents from a single script; the one-agent-per-script restriction does not exist.
• C is wrong because the switch does not allow unlimited agent deployment; hard limits are enforced by the switch model, so it will refuse agents beyond the cap, not just degrade performance.
• D contradicts the same limits - custom scripts are subject to the same per-model monitor/agent caps as built-in scripts.

Memory tip: Think "Model = Maximum" - the switch model determines the maximum monitors you can run. Plan by checking your model's spec sheet first, then count how many monitors each agent needs before committing to a deployment design.

No community discussion yet for this question.