Question 590
At fictional Lakeshore Finance, an HPE edge-to-cloud solution architect supporting transaction services is assessing industry architectures and deployment-model tradeoffs during a campus deployment design (HPE-HPE0-V27-TRENDS-148). The reported customer challenge is: A company selects private cloud for bursty short-lived test workloads solely because hardware is already owned. Which underlying edge-to-cloud design or business principle best explains the appropriate response?
Explanation
Correct Answer
The governing principle is: Workload variability and service consumption patterns influence appropriate cloud delivery. For this problem, A company selects private cloud for bursty short-lived test workloads solely because hardware is already owned, a suitable response is: Compare utilization patterns and elasticity economics before selecting private, public or hybrid placement. The expected result is: A representative monthly demand model supports the intended deployment and cost choice.
Incorrect Answers
“Software-defined overlays depend on healthy physical forwarding infrastructure” supports the separate task “Design the underlay IP fabric and resilience required for overlay services”, not the reported problem: a company selects private cloud for bursty short-lived test workloads solely because hardware is already owned. This case instead calls for “Compare utilization patterns and elasticity economics before selecting private, public or hybrid placement”.
“Network segmentation limits the effect of compromised endpoints and diverse device trust levels” concerns the separate step “Introduce authenticated device roles and segmentation appropriate to trust and access requirements”. The reported issue is that a company selects private cloud for bursty short-lived test workloads solely because hardware is already owned, so the direct response is to compare utilization patterns and elasticity economics before selecting private, public or hybrid placement.
The proposed “Host replacement cannot protect against every shared-site dependency” tests a different control: distribute critical workloads across appropriately isolated fault domains with state protection. The reported condition is that a company selects private cloud for bursty short-lived test workloads solely because hardware is already owned; the more direct action is to compare utilization patterns and elasticity economics before selecting private, public or hybrid placement.