Question 660
At fictional Keystone Hospitality, an HPE edge-to-cloud solution architect supporting guest-service systems is assessing business outcomes and technical discovery during an architecture discovery workshop (HPE-HPE0-V27-REQUIRE-165). The reported customer challenge is: A business requests a five-year compute plan but provides only today's CPU utilization. Which repeatable review, test, or governance safeguard would best prevent this problem from recurring?
Explanation
Correct Answer
The best ongoing safeguard is: Review forecasts and utilization baselines at each planning checkpoint. It specifically reduces recurrence of: A business requests a five-year compute plan but provides only today's CPU utilization. The relevant correction is: Collect growth drivers, refresh cycles, memory trends and planned application migrations. Proof of the corrected state is: Resource forecast includes credible expansion and headroom across the planning period.
Incorrect Answers
“Require representative restore proof as a requirement acceptance criterion” concerns the alternative task “Gather retention, audit and successful restore evidence rather than relying on job status”, but the stated failure is that a business requests a five-year compute plan but provides only today's CPU utilization. The required measure is to collect growth drivers, refresh cycles, memory trends and planned application migrations.
The proposed “Document outage budget and rollback dependencies before selecting migration tools” tests a different control: collect business change constraints and application recovery acceptance priorities. The reported condition is that a business requests a five-year compute plan but provides only today's CPU utilization; the more direct action is to collect growth drivers, refresh cycles, memory trends and planned application migrations.
“Establish path health as a prerequisite in change requirements” supports the separate task “Collect pre-change redundancy and maintenance windows before promising non-disruption”, not the reported problem: a business requests a five-year compute plan but provides only today's CPU utilization. This case instead calls for “Collect growth drivers, refresh cycles, memory trends and planned application migrations”.