Question 300
At the Westhaven public agency storage infrastructure department, inactive data remains on expensive local SSD media while a supported object tier is available. Which ongoing control best prevents this failure from recurring?
Explanation
Correct Answer
The continuing safeguard is to monitor object-tier availability and read activity after tiering policy changes. It helps avoid the original condition: cold blocks can be placed on an object tier under policy but hot data access and networking still matter. This result addresses the stated challenge at the Westhaven public agency storage infrastructure department.
Incorrect Answers
“Measure savings and CPU or latency impact after data composition changes” checks a different ongoing risk rather than the reported failure: at the Westhaven public agency storage infrastructure department, inactive data remains on expensive local SSD media while a supported object tier is available. The relevant mechanism is cold blocks can be placed on an object tier under policy but hot data access and networking still matter. The directly matched preventive control is “Monitor object-tier availability and read activity after tiering policy changes”.
Audit junction path and mount status after volume moves is not the primary recurring safeguard for this problem. The team should monitor object-tier availability and read activity after tiering policy changes. For the Westhaven public agency storage infrastructure department, the direct corrective action is to configure a suitable FabricPool tiering policy with validated capacity and recall needs.
“Monitor snapshot growth against retention and aggregate headroom” checks a different ongoing risk rather than the reported failure: at the Westhaven public agency storage infrastructure department, inactive data remains on expensive local SSD media while a supported object tier is available. The relevant mechanism is cold blocks can be placed on an object tier under policy but hot data access and networking still matter. The directly matched preventive control is “Monitor object-tier availability and read activity after tiering policy changes”.