A database administrator should review the database disaster recovery documentation:

Question

Options

• Awhenever a new Chief Technical Officer joins the company.
• Bwhen the company's business requirements change.
• Cduring every first week of every month.
• Djust before an outside audit is scheduled.

• A
  3% (1)
• B
  91% (31)
• D
  6% (2)

Explanation

Disaster recovery documentation must stay aligned with the organization's actual business needs, so reviewing it whenever business requirements change ensures the recovery plan remains accurate and actionable - outdated DR docs can be as dangerous as having none at all.

Why the distractors fail:

• A - A new CTO is a personnel change, not a business requirements change; leadership transitions don't automatically alter recovery needs.
• C - Arbitrary calendar-based reviews (monthly first week) are bureaucratic and may miss critical changes between cycles or waste effort when nothing has changed.
• D - Reviewing only before an audit is reactive compliance theater; if a disaster strikes before the audit, the documentation may be dangerously stale.

Memory tip: Think of DR documentation like a map - you update a map when the terrain changes (business requirements), not on a fixed schedule or when someone asks to see it.

No community discussion yet for this question.