Question 900
A server operations team encounters the following situation: A DNS issue is reported by one user, but the engineer changes the organization's authoritative zone before confirming whether another client can resolve the name. Which sustained operational control best reduces the likelihood of this same issue recurring?
Explanation
Correct Answer
This control targets the underlying recurrence risk: The assumed organization-wide fault was not established by a single report. It builds validation into the affected workflow and supports the expected recovery result: Testing isolates the problem to local cache, hosts file or central DNS as appropriate.
Incorrect Answers
This control addresses a different scenario: A server stops responding to users, and an engineer reboots it repeatedly before preserving volatile diagnostic logs or attempting a safe reproduction. That event's root mechanism was premature resets erase evidence and interrupt service without confirming cause. The described incident instead arises from: The assumed organization-wide fault was not established by a single report.
This control addresses a different scenario: An emergency fix makes a web service reachable but fails to document command changes, leaving the on-call team unable to repeat or undo them. That event's root mechanism was undocumented repairs create repeat failures and operational drift. The described incident instead arises from: The assumed organization-wide fault was not established by a single report.
This control addresses a different scenario: A severe outage affects 50 servers, but first-line support spends an hour guessing rather than escalating to the specialized storage team. That event's root mechanism was incident magnitude exceeds the available support scope and authority. The described incident instead arises from: The assumed organization-wide fault was not established by a single report.