Which of the following should be done before applying a patch to a database?

Question

Options

• AMake backups.
• BTest the database.
• CVerify the logs.
• DRestart the database.

• A
  86% (18)
• B
  5% (1)
• C
  10% (2)

Explanation

Making a backup (A) is the essential first step before patching a database because patches can fail, corrupt data, or introduce unexpected behavior - a backup ensures you can restore the system to its pre-patch state if anything goes wrong. This is a fundamental principle of change management: never make irreversible changes without a recovery path.

Why the distractors are wrong:

• B (Test the database): Testing is important, but it's done after applying the patch in a non-production environment, not before patching production. It's also not the first thing to do.
• C (Verify the logs): Log review is useful for troubleshooting but is not a prerequisite step before patching - it doesn't protect you if the patch fails.
• D (Restart the database): A restart may be required after a patch is applied, not before it.

Memory tip: Think of patching like surgery - you always want a "rollback" plan before cutting. B-A-P (Backup → Apply → Post-check) keeps the order straight: backup before, test after.

No community discussion yet for this question.