Question 260
A server operations team encounters the following situation: A server OS template includes an outdated network driver that crashes under modern 10GbE load despite successful boot. Which sustained operational control best reduces the likelihood of this same issue recurring?
Explanation
Correct Answer
This control targets the underlying recurrence risk: Initial boot success does not establish runtime driver compatibility under load. It builds validation into the affected workflow and supports the expected recovery result: Network stress testing completes without driver crashes or link errors.
Incorrect Answers
This control addresses a different scenario: A Linux production node uses a legacy MBR boot layout but a planned 6 TB volume must be partitioned as a single data disk. That event's root mechanism was mBR partitioning limits normal single-disk addressing beyond about 2 TiB. The described incident instead arises from: Initial boot success does not establish runtime driver compatibility under load.
This control addresses a different scenario: A new web host is provisioned with a GUI-heavy operating system even though the hardened baseline calls for a minimal core install. That event's root mechanism was the installation choice increases attack surface and management footprint beyond policy. The described incident instead arises from: Initial boot success does not establish runtime driver compatibility under load.
This control addresses a different scenario: A VM template contains embedded static IP addresses, and every newly created app server starts with an identical network configuration. That event's root mechanism was a golden image was reused with instance-specific configuration unchanged. The described incident instead arises from: Initial boot success does not establish runtime driver compatibility under load.