A team keeps database backups for seven days and runs a full database integrity check once a month. An auditor says this schedule could leave the team unable to recover a clean copy. What is the auditor's concern?
Select an answer to reveal the explanation.
Short Explanation
If you only inspect the milk once a month but throw out receipts after a week, you can't prove which carton went bad first or get a fresh one back. Your integrity checks have to run often enough that a clean backup still exists when you find a problem. And don't confuse a backup hash with a data check; the hash just proves the file wasn't altered.
Full Explanation
An integrity check detects corruption in the live database, and the backup retention period determines how far back a restore can reach. If corruption occurs shortly after a monthly check, it may go undetected for up to a month, while backups are retained for only seven days; by the time the next check finds it, every available backup was taken after the corruption began and may contain the damage. Running integrity checks more frequently than the retention window, or extending retention, ensures at least one backup predates any corruption the check discovers. Running checks only quarterly widens the gap further, and integrity checks read data, which consumes I/O but does not damage files. Validating a backup's hash confirms that the backup file is identical to what was written and has not been altered in storage; it says nothing about whether the database pages captured in that backup were consistent when the backup was taken. Shortening retention to one day would make the gap far worse, and older backups are routinely needed when problems are discovered late. Exam caveat: some teams run checks against restored backups on a separate server to reduce production load while still verifying both the backup and the data. Operational check: compare the integrity check interval with the shortest retention period, adjust one or both, and record the date of the last clean check alongside each retained backup.