Question 20
At fictional Fairport Manufacturing, an HPE edge-to-cloud solution architect supporting factory operations is assessing customer proof of value and delivery planning during a hybrid-cloud adoption planning meeting (HPE-HPE0-V27-PRESENT-005). The reported customer challenge is: A PoC success report states 'fast enough' without comparing agreed latency targets. Which repeatable review, test, or governance safeguard would best prevent this problem from recurring?
Explanation
Correct Answer
The best ongoing safeguard is: Define test metrics and evidence format before executing pilot. It specifically reduces recurrence of: A PoC success report states 'fast enough' without comparing agreed latency targets. The relevant correction is: Present measured IOPS, latency percentiles and concurrency against customer thresholds. Proof of the corrected state is: Stakeholders can verify each pass/fail condition from test evidence.
Incorrect Answers
“Capture customer facilities meter readings before finalizing calculations” concerns the alternative task “Present measured existing consumption and comparable projected hardware energy use”, but the stated failure is that a PoC success report states 'fast enough' without comparing agreed latency targets. The required measure is to present measured IOPS, latency percentiles and concurrency against customer thresholds.
“Add policy violation cases to the demo script” supports the separate task “Test intentional unauthorized east-west and guest access attempts”, not the reported problem: a PoC success report states 'fast enough' without comparing agreed latency targets. This case instead calls for “Present measured IOPS, latency percentiles and concurrency against customer thresholds”.
“Include controlled fault cases for each advertised protection mechanism” concerns the separate step “Demonstrate one expected network or storage path fault under representative I/O”. The reported issue is that a PoC success report states 'fast enough' without comparing agreed latency targets, so the direct response is to present measured IOPS, latency percentiles and concurrency against customer thresholds.