Question 780
Fictional Fernhaven Services runs the contract processing workload at a primary cluster room storage site. While completing change preflight, the field handoff documents: The business case counts raw advertised flash capacity as if all of it were available for protected application data. The team requires a direct technical explanation and measured acceptance check. Which preventive control most directly reduces this failure risk?
Explanation
Correct Answer
The ongoing safeguard is: Publish raw effective and protected usable capacity separately in planning sheets. The recurring exposure to avoid is: The capacity design ignores system overhead and protection/reduction variability. A continuing effectiveness check is: The approved target reports sufficient safe free usable capacity under realistic workload assumptions.
Incorrect Answers
This option focuses on: Monitor hardware state throughout upgrades and record check results. That can be relevant to module state consistency before software change, but it does not establish the required case-specific result. The current case instead identifies: The capacity design ignores system overhead and protection/reduction variability. The more directly applicable prevention choice is: Publish raw effective and protected usable capacity separately in planning sheets.
This alternative concerns: Monitor remote management health and egress requirements before planned maintenance. It is associated with pure1 self-service upgrade readiness, rather than the question’s determining condition. The case instead turns on: The capacity design ignores system overhead and protection/reduction variability. The more directly applicable prevention choice is: Publish raw effective and protected usable capacity separately in planning sheets.
The offered choice addresses: Make multipath path-state evidence a mandatory upgrade go or no-go artifact. That concerns controller upgrade host path continuity, rather than the specific failure described here. The deciding issue in this scenario is: The capacity design ignores system overhead and protection/reduction variability. The more directly applicable prevention choice is: Publish raw effective and protected usable capacity separately in planning sheets.