Question 700
At fictional Alder Municipality, an HPE edge-to-cloud solution architect supporting public services is assessing postdeployment modernization and growth during an HPE solution proposal revision (HPE-HPE0-V27-ENHANCE-175). The reported customer challenge is: A customer doubles protected data but retains old backup repository and throughput forecasts. Which underlying edge-to-cloud design or business principle best explains the appropriate response?
Explanation
Correct Answer
The governing principle is: Data protection infrastructure must scale with change rate and recovery requirements. For this problem, A customer doubles protected data but retains old backup repository and throughput forecasts, a suitable response is: Recalculate protection capacity, ingestion rate, retention and restore-window requirements. The expected result is: Expanded protection still meets backup completion and recovery objectives.
Incorrect Answers
“Monitoring enhancements require integration compatibility and action responsibility” concerns the alternative task “Expand an HPE OpsRamp or appropriate observable integration after verifying approved connectors”, but the stated failure is that a customer doubles protected data but retains old backup repository and throughput forecasts. The required measure is to recalculate protection capacity, ingestion rate, retention and restore-window requirements.
The proposed “Expansion planning should use observed bottleneck data rather than blanket replacement” tests a different control: measure actual link, PoE and client load before selecting targeted access upgrades. The reported condition is that a customer doubles protected data but retains old backup repository and throughput forecasts; the more direct action is to recalculate protection capacity, ingestion rate, retention and restore-window requirements.
“Solution lifecycle changes may be triggered by legal or business obligations” supports the separate task “Propose scoped data placement and retention changes under governance approval”, not the reported problem: a customer doubles protected data but retains old backup repository and throughput forecasts. This case instead calls for “Recalculate protection capacity, ingestion rate, retention and restore-window requirements”.