Question 60
At fictional Uplands Retail, an HPE edge-to-cloud solution architect supporting commerce applications is assessing HPE end-to-end architecture and integration during an architecture discovery workshop (HPE-HPE0-V27-DESIGN-015). The reported customer challenge is: A project chooses a rack server with maximum CPU count but inadequate memory for its virtualization density. Which repeatable review, test, or governance safeguard would best prevent this problem from recurring?
Explanation
Correct Answer
The best ongoing safeguard is: Collect CPU contention and memory utilization during pilot load. It specifically reduces recurrence of: A project chooses a rack server with maximum CPU count but inadequate memory for its virtualization density. The relevant correction is: Size CPU cores, RAM, storage I/O and networking against actual virtual machine profiles. Proof of the corrected state is: Consolidated hosts run representative peak workloads without excessive swapping or CPU ready time.
Incorrect Answers
“Check current compatibility listings and support expiration before quoting” concerns the alternative task “Compare hardware modernization and compatible virtualization options before final architecture”, but the stated failure is that a project chooses a rack server with maximum CPU count but inadequate memory for its virtualization density. The required measure is to size CPU cores, RAM, storage I/O and networking against actual virtual machine profiles.
The proposed “Test denied routes between all tenant roles after policy changes” tests a different control: design VRFs and policy-controlled intertenant route exchange. The reported condition is that a project chooses a rack server with maximum CPU count but inadequate memory for its virtualization density; the more direct action is to size CPU cores, RAM, storage I/O and networking against actual virtual machine profiles.
“Use application owner acceptance as a disaster recovery success gate” supports the separate task “Include identity, network, database recovery and application transactions in the recovery workflow”, not the reported problem: a project chooses a rack server with maximum CPU count but inadequate memory for its virtualization density. This case instead calls for “Size CPU cores, RAM, storage I/O and networking against actual virtual machine profiles”.