Which three actions are effective in capacity planning? (Choose three.)

Question

Options

• Abuying more RAM
• Bmonitoring OS resources for patterns
• Cadding circular replication nodes for increased DML capability
• Dbuying more CPU
• Ebuying more disk
• Fbasing expected growth on an average of the last 3 years
• Gconsulting the application team about any future projects and use
• Hupgrading to the latest application version

• A
  9% (2)
• B
  82% (18)
• C
  5% (1)
• H
  5% (1)

Explanation

Effective capacity planning is proactive, not reactive. Options B, F, and G are correct because they represent the core methodology: observing current trends (B - monitoring OS resources reveals usage patterns and bottlenecks before they become crises), projecting from history (F - a 3-year average smooths anomalies and gives a statistically reliable growth baseline), and capturing planned demand (G - application teams know about upcoming projects that historical data cannot predict, so their input is essential for forward-looking planning).

The distractors (A, D, E - buying RAM/CPU/disk) are purchasing actions, not planning activities; they might result from a capacity plan, but they are not the plan itself. Option C (circular replication for DML) is an architectural solution targeting write throughput, which is unrelated to the capacity planning process. Option H (upgrading the application version) is a maintenance/patching task with no inherent connection to forecasting resource needs.

Memory tip: Think of the three correct answers as "Look Back, Look Around, Look Ahead" - monitor what's happening now (B), analyze historical averages (F), and ask stakeholders what's coming (G). Anything that skips straight to buying hardware or changing architecture is acting, not planning.

No community discussion yet for this question.