Question 760
At fictional Uplands Retail, an HPE edge-to-cloud solution architect supporting commerce applications is assessing HPE end-to-end architecture and integration during a security and compliance assessment (HPE-HPE0-V27-DESIGN-190). The reported customer challenge is: A branch rollout chooses an oversized central appliance though each site has different performance needs. Which underlying edge-to-cloud design or business principle best explains the appropriate response?
Explanation
Correct Answer
The governing principle is: Standard templates should be right-sized to site classes rather than uniform maximum. For this problem, A branch rollout chooses an oversized central appliance though each site has different performance needs, a suitable response is: Build a few validated scalable branch profiles by bandwidth, users and critical services. The expected result is: Each pilot profile satisfies its branch workload and cost boundaries.
Incorrect Answers
The proposed “Remote operations cannot replace missing physical redundancy by itself” tests a different control: define local redundancy, backup or remote recovery based on branch criticality. The reported condition is that a branch rollout chooses an oversized central appliance though each site has different performance needs; the more direct action is to build a few validated scalable branch profiles by bandwidth, users and critical services.
“Accelerator performance can be limited by data I/O rather than compute arithmetic” supports the separate task “Design the data and network pipeline for simultaneous accelerator workers”, not the reported problem: a branch rollout chooses an oversized central appliance though each site has different performance needs. This case instead calls for “Build a few validated scalable branch profiles by bandwidth, users and critical services”.
“Resilience requires separating workload data paths from management-plane dependencies” concerns the separate step “Select an approved management model with tested local operation under disconnected conditions”. The reported issue is that a branch rollout chooses an oversized central appliance though each site has different performance needs, so the direct response is to build a few validated scalable branch profiles by bandwidth, users and critical services.