Question 600
At fictional Fairport Manufacturing, an HPE edge-to-cloud solution architect supporting factory operations is assessing business outcomes and technical discovery during a customer operating model review (HPE-HPE0-V27-REQUIRE-150). The reported customer challenge is: A customer says 'backup the data' while omitting how long records must remain accessible. Which repeatable review, test, or governance safeguard would best prevent this problem from recurring?
Explanation
Correct Answer
The best ongoing safeguard is: Maintain data class and retention approvals in requirements baseline. It specifically reduces recurrence of: A customer says 'backup the data' while omitting how long records must remain accessible. The relevant correction is: Elicit retention classes, legal holds, deletion exceptions and recovery point granularity. Proof of the corrected state is: Written backup policy demonstrates different durations for approved data classes.
Incorrect Answers
“Use a jointly approved discovery checklist before proposing hardware” concerns the alternative task “Interview application owners and measure CPU, memory, network and storage latency before selection”, but the stated failure is that a customer says 'backup the data' while omitting how long records must remain accessible. The required measure is to elicit retention classes, legal holds, deletion exceptions and recovery point granularity.
“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 customer says 'backup the data' while omitting how long records must remain accessible. This case instead calls for “Elicit retention classes, legal holds, deletion exceptions and recovery point granularity”.
“Document cutover gate approvals and recovery dependencies per wave” concerns the separate step “Gather service criticality, migration dependencies and accepted outage window”. The reported issue is that a customer says 'backup the data' while omitting how long records must remain accessible, so the direct response is to elicit retention classes, legal holds, deletion exceptions and recovery point granularity.