Question 310
At fictional Granite Logistics, a storage integration engineer supporting distribution infrastructure is evaluating storage provisioning, lifecycle and access controls during an application migration (HPE-HPE0-J83-ADMIN-078). The observed storage integration issue is: A performance optimization change is applied directly to every HPE array instead of a targeted workload. Which recurring preventive or detective control would most directly reduce recurrence?
Explanation
Correct Answer
The specific preventive or detective safeguard is: Require targeted rollback and change-impact comparisons. It reduces the risk of: A performance optimization change is applied directly to every HPE array instead of a targeted workload. The associated correction is: Stage supported QoS or storage policy changes against an approved pilot subset. Successful implementation would show: Pilot metrics improve without unexpected interference for unrelated applications.
Incorrect Answers
The HPE measure “Review overdue firmware and host interoperability drift monthly.” concerns another storage task: Create a joint schedule and escalation path with application network and storage owners. The actual acceptance gap is that a performance optimization change is applied directly to every HPE array instead of a targeted workload. Stage supported QoS or storage policy changes against an approved pilot subset.
“Reconcile volume exports and current initiator inventory after every change.” would examine another storage topic: Correct the volume export and initiator group membership before enabling production. That does not resolve the stated failure: a performance optimization change is applied directly to every HPE array instead of a targeted workload. Stage supported QoS or storage policy changes against an approved pilot subset.
This option tests a separate storage control: Retire unnecessary fabric access and array mapping under an approved offboarding workflow. The reported gap is that a performance optimization change is applied directly to every HPE array instead of a targeted workload. Stage supported QoS or storage policy changes against an approved pilot subset.