For an application experiencing variable load patterns, which monitoring capabilities would provide the most insight into scaling needs?

Question

Options

• ACPU and memory utilization trends
• BWeekly summary reports
• CDisk I/O operations
• DNetwork ingress and egress traffic patterns

• A
  75% (50)
• B
  25% (17)

Explanation

CPU and memory utilization trends (A), disk I/O operations (C), and network ingress/egress traffic patterns (D) together form a complete picture of resource consumption under variable load - they reveal where bottlenecks form as traffic spikes and help predict when to scale up or down. CPU and memory trends show compute saturation; disk I/O exposes storage throughput limits that slow applications under heavy read/write load; and network traffic patterns reveal bandwidth constraints and help forecast capacity needs as user demand shifts. Weekly summary reports (B) are too coarse and delayed to respond to variable load - they smooth out the spikes you most need to see, making them useless for real-time or near-real-time scaling decisions.

Memory tip: Think of the three correct answers as covering the three resource "lanes" a server uses - compute (CPU/RAM), storage (disk I/O), and connectivity (network) - all of which must be monitored to understand scaling needs holistically.

No community discussion yet for this question.