Question 890
A team has corrected this HPE compute solution issue: A fleet policy changes BIOS settings on every production host without testing one representative system. Which continuing practice would best prevent the same problem?
Explanation
Correct Answer
Use progressive deployment for compute configuration automation. This recurring assurance measure is tied to the diagnosed risk: Configuration deployment lacks staged validation and compatibility checks. For the active incident, the corrective action remains: Test supported configuration changes on a controlled subset before broad rollout.
Incorrect Answers
Configuration deployment lacks staged validation and compatibility checks. The proposed safeguard is intended for another failure mechanism: Image format, driver and migration dependencies may differ between platforms. Use progressive deployment for compute configuration automation.
The chosen placement offers no validated alternate capacity for service recovery. The option addresses that risk, not the one responsible for the present issue. Configuration deployment lacks staged validation and compatibility checks. Use progressive deployment for compute configuration automation.
The prevention measure is relevant to this condition: Successful data copying alone does not guarantee application-level recovery. Here the recurring weakness is: Configuration deployment lacks staged validation and compatibility checks. Use progressive deployment for compute configuration automation.