A cross-functional leadership team met to review and approve a disaster recovery plan (DRP) that was recently updated due to changes in business processes and underlying system architectures. Which of

Question

Options

• AContact details for hardware providers are incorrect.
• BRecovery procedures for one of the support utilities are not included.
• CVersion numbers of key systems are incorrect.
• DRecovery procedures for the master databases are not included.

• A
  25% (13)
• B
  6% (3)
• C
  10% (5)
• D
  59% (30)

Explanation

Recovery procedures for master databases represent the most critical concern because master databases typically contain the core transactional and reference data that the entire organization depends on - without them, business operations cannot resume, making their absence a showstopper for any viable recovery.

Why the distractors fall short:

• A (incorrect contact details): Outdated vendor contacts are a gap, but contacts can be improvised or sourced quickly during an incident; this doesn't prevent recovery itself.
• B (missing support utility procedures): Support utilities are secondary systems - their absence causes inconvenience but won't halt core business recovery the way missing database procedures would.
• C (incorrect version numbers): Inaccurate version info is a documentation quality issue and could cause confusion, but it doesn't eliminate the ability to recover - technicians can verify versions at recovery time.

Memory tip: Think in terms of dependency hierarchy - ask "what breaks everything else if it's missing?" Master databases sit at the foundation; applications, utilities, and integrations all depend on them. In DRP questions, always prioritize the component whose absence makes recovery impossible, not merely harder.

No community discussion yet for this question.