Question 780
At fictional Alder Community, a storage integration engineer supporting public services is evaluating customer storage sizing and solution requirements during a SAN change (HPE-HPE0-J83-PLAN-195). The observed storage integration issue is: A procurement decision is based only on advertised throughput and ignores the vendor's platform support lifecycle. Which storage architecture or operating principle best explains the appropriate response?
Explanation
Correct Answer
The technical principle is: Long-lived infrastructure design must consider release and service lifecycle risk. The reported fault is: A procurement decision is based only on advertised throughput and ignores the vendor's platform support lifecycle. A suitable action is: Compare product release maturity compatibility service lifespan and refresh trajectory. A successful check would show: The selected stack has supported upgrade paths throughout the planned business horizon.
Incorrect Answers
“Operational responsibility is a core part of disaster recovery design.” would examine another storage topic: Assign recovery ownership and escalation paths across storage backup and application teams. That does not resolve the stated failure: a procurement decision is based only on advertised throughput and ignores the vendor's platform support lifecycle. Long-lived infrastructure design must consider release and service lifecycle risk.
This option tests a separate storage control: Confirm rack units weight feed redundancy cooling and cable reach for the full design. The reported gap is that a procurement decision is based only on advertised throughput and ignores the vendor's platform support lifecycle. Long-lived infrastructure design must consider release and service lifecycle risk.
The HPE measure “Data-at-rest encryption needs durable key custody and access governance.” concerns another storage task: Define keys lifecycle responsibilities and supported encryption or external KMS integration. The actual acceptance gap is that a procurement decision is based only on advertised throughput and ignores the vendor's platform support lifecycle. Long-lived infrastructure design must consider release and service lifecycle risk.