What is firmware baseline compliance?

• A. Ensuring firmware is updated to the latest version for performance.
• B. Sticking to a fixed hardware configuration for compatibility.
• C. Keeping all components at approved firmware versions for stability/security.
• D. Recording firmware versions for inventory purposes.

Answer: (C)

Baseline compliance means keeping every device’s firmware within a documented, approved set of versions so the system remains stable, secure, and supported. It’s about controlled, tested configurations rather than chasing the newest release or changing hardware alone. By staying within approved firmware versions, you ensure compatibility across components, predictable behavior, and a clear path for audits and vendor support. Updates are managed through a change process, so any new versions are tested and authorized before deployment.

Choosing the option that talks about always updating to the latest version misses the point: baselines are about approved, tested versions, not just the freshest release. The idea of a fixed hardware configuration addresses hardware, not firmware baseline. Recording firmware versions for inventory is useful, but it doesn’t capture the active requirement to run only approved versions.