Question 870
A team has corrected this HPE compute solution issue: A fleet operator changes a firmware baseline for one group without reviewing whether it is supported by every server model. Which continuing practice would best prevent the same problem?
Explanation
Correct Answer
Review model compatibility before group baseline changes. This recurring assurance measure is tied to the diagnosed risk: A single group can contain hardware needing different approved release applicability. For the active incident, the corrective action remains: Separate compatible device groups or select a validated baseline per model.
Incorrect Answers
A single group can contain hardware needing different approved release applicability. Using the proposed safeguard would guard against a separate risk: The performance test does not represent the application's I/O pattern. Review model compatibility before group baseline changes.
Configuration changes were not recorded against the approved baseline. The selected safeguard helps with that exposure, but it leaves the recurrence risk here unaddressed. A single group can contain hardware needing different approved release applicability. Review model compatibility before group baseline changes.
This control protects against a condition in which the chosen server SKU may not accommodate the planned inference hardware. The issue to prevent here is: A single group can contain hardware needing different approved release applicability. Review model compatibility before group baseline changes.