What is a typical risk of not performing integrity checks on backups?

What is a typical risk of not performing integrity checks on backups?

• A. Larger storage usage
• B. Potential data corruption going unnoticed
• C. Faster backup
• D. No risk

Answer: (B)

Integrity checks on backups verify that the data stored in backups matches what was written, by checking hashes, checksums, or other validation methods. If you skip these checks, a backup can become corrupted during write, transfer, or storage, and you may not notice that problem until you need to restore. When a restore is attempted, the corrupted backup can fail or yield incomplete, unusable data, leading to downtime and potential data loss. That’s why the typical risk is data corruption going unnoticed. The other options don’t reflect the main danger: integrity checks don’t inherently cause larger storage usage, they don’t make backups faster, and saying there’s no risk ignores the real possibility of undetected corruption.

Integrity checks on backups verify that the data stored in backups matches what was written, by checking hashes, checksums, or other validation methods. If you skip these checks, a backup can become corrupted during write, transfer, or storage, and you may not notice that problem until you need to restore. When a restore is attempted, the corrupted backup can fail or yield incomplete, unusable data, leading to downtime and potential data loss. That’s why the typical risk is data corruption going unnoticed. The other options don’t reflect the main danger: integrity checks don’t inherently cause larger storage usage, they don’t make backups faster, and saying there’s no risk ignores the real possibility of undetected corruption.