A team applies a firmware patch in a data center and then sees discrepancies during boot on multiple servers. Logs show that what was expected no longer aligns with values in a secure hardware component. Which approach resolves these anomalies?
Disable integrity checks to avoid future warnings
Perform multiple system restarts until logs no longer indicate a discrepancy
Refresh the references in the secure hardware component so it aligns with the updated firmware
Reset the operating system credentials so old keys are replaced with new ones
When a system undergoes a firmware update, entries in the device’s trust anchor may no longer match. Updating that anchor ensures new measurements are recognized. Resetting operating system keys, repeatedly rebooting, or turning off checks will not correct data stored at a hardware level, which causes these discrepancies.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a secure hardware component in this context?
Open an interactive chat with Bash
How does refreshing references in a secure hardware component resolve anomalies?
Open an interactive chat with Bash
Why can't operations like resetting credentials or disabling integrity checks fix the problem?