A municipal tax database team wants Sunday to capture a complete copy of the system, then weekdays to capture only what changed since the previous backup job. Which backup pattern matches that plan?

A full backup copies the entire selected dataset at a point in time. Incremental backups then capture only changes since the most recent backup job, which matches a municipal tax database plan that takes a complete Sunday copy and then weekday jobs that record only what changed since the previous job. That weekly-full-plus-daily-incremental pattern balances restore completeness with weekday job duration and storage growth—important when county finance systems must remain recoverable without saturating backup windows every night.

Daily full backups with no incremental jobs at all ignore the weekday "changes only" requirement and inflate Sunday-style load into every night. Continuous synchronous mirroring with no scheduled backup points is a high-availability or replication technique, not the scheduled full-plus-incremental backup pattern described. Archive-only snapshots written once per fiscal year cannot support day-to-day recovery of mid-week tax posting errors.

Exam caveat: incremental means "since the last backup" (full or incremental), whereas differential means "since the last full." Mixing the terms is a common exam trap. Also remember restore chains: losing a middle incremental can break recoverability to a later point.

Operational check: confirm Sunday jobs are fulls, weekday jobs are incrementals chained correctly, run a restore drill that applies Sunday full plus subsequent incrementals into a test tax database, and record restore duration against the department's RTO. Store catalogs and media so the civic records team can prove the chain remains intact after retention purges.