What cannot be learned from the output of asg perf -v -p command?

Question

Options

• AAverage CPU usage on Appliances
• BReal-time throughput
• CAverage CPU usage on Orchestrators
• DPer-path distribution

• A
  4% (1)
• B
  8% (2)
• C
  88% (23)

Explanation

Option C is correct because asg perf -v -p is an appliance-side command - it runs locally on the appliance and reports metrics scoped to that device. Orchestrator CPU usage is stored and tracked on the Orchestrator itself, so it is simply not accessible from this command.

Why the distractors are wrong:

• A (Average CPU on Appliances) - This IS visible; the command runs on the appliance, so local CPU utilization is included in the output.
• B (Real-time throughput) - The -v (verbose) flag expands the output to include live throughput data, so this is available.
• D (Per-path distribution) - The -p flag specifically enables per-path breakdown, making this a key feature of this exact command syntax.

Memory tip: Think of the -p as "per-path on the appliance." The command lives on the appliance, dies on the appliance - anything that lives on the Orchestrator (like Orchestrator CPU) is out of reach. If a metric belongs to a different device, this command can't show it.

No community discussion yet for this question.