Question 830
A team has corrected this HPE compute solution issue: A technician changes server BIOS settings from an untracked manual note and later cannot explain the configuration drift. Which continuing practice would best prevent the same problem?
Explanation
Correct Answer
Track HPE hardware configurations under versioned change control. This recurring assurance measure is tied to the diagnosed risk: Configuration changes were not recorded against the approved baseline. For the active incident, the corrective action remains: Use supported HPE configuration management and audit workflows for BIOS changes.
Incorrect Answers
This control protects against a condition in which unprotected local storage exposes workloads to a single-device failure. The issue to prevent here is: Configuration changes were not recorded against the approved baseline. Track HPE hardware configurations under versioned change control.
Configuration changes were not recorded against the approved baseline. The proposed safeguard is intended for another failure mechanism: Out-of-band privileged management is exposed beyond the authorized operator boundary. Track HPE hardware configurations under versioned change control.
The prevention measure is relevant to this condition: Infrastructure management and application authorization have different control scopes. Here the recurring weakness is: Configuration changes were not recorded against the approved baseline. Track HPE hardware configurations under versioned change control.