Question 710
At fictional Vista Research, an HPE edge-to-cloud solution architect supporting analytical datasets is assessing postdeployment modernization and growth during a migration readiness review (HPE-HPE0-V27-ENHANCE-178). The reported customer challenge is: A GreenLake organization creates resources rapidly but unowned instances accumulate cost. Which customer-focused architecture or engineering action most directly addresses the situation?
Explanation
Correct Answer
The most directly responsive action is: Add cost-center ownership, expiration and quota automation with approval boundaries. The specific customer situation is: A GreenLake organization creates resources rapidly but unowned instances accumulate cost. The expected validation is: Unused instances are retired after owner review while needed resources remain. The governing architecture or business principle is: Cloud governance must include lifecycle and waste controls.
Incorrect Answers
“Propose scoped data placement and retention changes under governance approval” supports the separate task “Propose scoped data placement and retention changes under governance approval”, not the reported problem: a GreenLake organization creates resources rapidly but unowned instances accumulate cost. This case instead calls for “Add cost-center ownership, expiration and quota automation with approval boundaries”.
“Propose staged connectivity, address isolation and identity alignment before full integration” concerns the alternative task “Propose staged connectivity, address isolation and identity alignment before full integration”, but the stated failure is that a GreenLake organization creates resources rapidly but unowned instances accumulate cost. The required measure is to add cost-center ownership, expiration and quota automation with approval boundaries.
The proposed “Stage supported compute refresh waves with validated migration and rollback procedures” tests a different control: stage supported compute refresh waves with validated migration and rollback procedures. The reported condition is that a GreenLake organization creates resources rapidly but unowned instances accumulate cost; the more direct action is to add cost-center ownership, expiration and quota automation with approval boundaries.