Question 580
At fictional Fairport Manufacturing, an HPE edge-to-cloud solution architect supporting factory operations is assessing HPE end-to-end architecture and integration during an HPE solution proposal revision (HPE-HPE0-V27-DESIGN-145). The reported customer challenge is: A regulated database requires data-at-rest encryption but no external key custody policy exists. Which repeatable review, test, or governance safeguard would best prevent this problem from recurring?
Explanation
Correct Answer
The best ongoing safeguard is: Test break-glass key recovery under least-privilege procedures. It specifically reduces recurrence of: A regulated database requires data-at-rest encryption but no external key custody policy exists. The relevant correction is: Design storage encryption and KMS integration with ownership and recoverable key backup. Proof of the corrected state is: A simulated key rotation and disaster restore meet authorized access controls.
Incorrect Answers
“Validate tier policy mappings with representative production and test workloads” concerns the alternative task “Create service classes with appropriate protection, capacity and deployment policies”, but the stated failure is that a regulated database requires data-at-rest encryption but no external key custody policy exists. The required measure is to design storage encryption and KMS integration with ownership and recoverable key backup.
The proposed “Add cross-business-unit negative authorization checks to acceptance” tests a different control: design separate project scopes, roles and data policies with controlled shared services. The reported condition is that a regulated database requires data-at-rest encryption but no external key custody policy exists; the more direct action is to design storage encryption and KMS integration with ownership and recoverable key backup.
“Validate service responsibilities with both customer and HPE delivery owners” supports the separate task “Clarify managed service change boundaries and design customer-approved maintenance control”, not the reported problem: a regulated database requires data-at-rest encryption but no external key custody policy exists. This case instead calls for “Design storage encryption and KMS integration with ownership and recoverable key backup”.