Question 540
At fictional Keystone Hospitality, an HPE edge-to-cloud solution architect supporting guest-service systems is assessing HPE end-to-end architecture and integration during an architecture discovery workshop (HPE-HPE0-V27-DESIGN-135). The reported customer challenge is: An enterprise wants low-cost capacity with no backup retention model for deleted customer records. Which underlying edge-to-cloud design or business principle best explains the appropriate response?
Explanation
Correct Answer
The governing principle is: Protection design balances recoverability and required deletion lifecycle. For this problem, An enterprise wants low-cost capacity with no backup retention model for deleted customer records, a suitable response is: Classify retention and recovery classes and size protection capacity accordingly. The expected result is: A restore and expiry test both satisfy approved timelines.
Incorrect Answers
“Application path placement should follow business intent and transport reliability” concerns the alternative task “Design appropriate local breakout and application-specific SD-WAN routing policies”, but the stated failure is that an enterprise wants low-cost capacity with no backup retention model for deleted customer records. The required measure is to classify retention and recovery classes and size protection capacity accordingly.
The proposed “Hosting location and operations ownership are separate architectural decisions” tests a different control: clarify managed service change boundaries and design customer-approved maintenance control. The reported condition is that an enterprise wants low-cost capacity with no backup retention model for deleted customer records; the more direct action is to classify retention and recovery classes and size protection capacity accordingly.
“Resilience must remove end-to-end shared dependencies rather than duplicate only hosts” supports the separate task “Design two independent fabric paths and compatible host bonding or multipathing mechanisms”, not the reported problem: an enterprise wants low-cost capacity with no backup retention model for deleted customer records. This case instead calls for “Classify retention and recovery classes and size protection capacity accordingly”.