Question 560
At fictional Uplands Retail, a storage integration engineer supporting commerce infrastructure is evaluating hybrid cloud delivery models and distributed data architecture during a cloud operations review (HPE-HPE0-J83-INDUSTRY-140). The observed storage integration issue is: A two-tier storage system moves blocks based only on capacity and not on observed access frequency. Which recurring preventive or detective control would most directly reduce recurrence?
Explanation
Correct Answer
The specific preventive or detective safeguard is: Review tier hit rates and latency after changes to placement rules. It reduces the risk of: A two-tier storage system moves blocks based only on capacity and not on observed access frequency. The associated correction is: Define supported tiering rules aligned with hot and cold workload profiles. Successful implementation would show: Frequently accessed blocks remain within response targets while cold storage is economical.
Incorrect Answers
“Monitor fabric drops and retransmit statistics during upgrades.” would examine another storage topic: Assess network congestion and supported flow-control or QoS behavior for storage traffic. That does not resolve the stated failure: a two-tier storage system moves blocks based only on capacity and not on observed access frequency. Define supported tiering rules aligned with hot and cold workload profiles.
This option tests a separate storage control: Map provider and customer operational responsibilities for the chosen IaaS service. The reported gap is that a two-tier storage system moves blocks based only on capacity and not on observed access frequency. Define supported tiering rules aligned with hot and cold workload profiles.
The choice “Exercise conflicting writes and failback before commissioning global namespaces.” evaluates another aspect of the storage design: Validate supported distributed file concurrency and conflict-resolution behavior. The current problem is that a two-tier storage system moves blocks based only on capacity and not on observed access frequency. Define supported tiering rules aligned with hot and cold workload profiles.