Which backup strategy is described as a combination of a full backup and an incremental backup?

Which backup strategy is described as a combination of a full backup and an incremental backup?

• A. Full backup
• B. Differential backup
• C. Incremental backup
• D. Normal backup

Answer: (D)

The main idea here is using a baseline full backup and then keeping the rest of the data updated with incremental backups, so you can rebuild the current state by applying the incremental data to that baseline. This approach is efficient because you don’t have to run a fresh full backup every time; you reuse the original full backup and layer on the changes captured by increments. In practice, this is often described as a synthetic or logical full backup, created by combining the initial full backup with subsequent incremental backups to present a complete restore image. That pattern gives fast restores (since you can restore from a single consolidated set) while minimizing the workload and storage needed for full backups. So the described strategy centers on maintaining a complete, up-to-date restore set by starting with a full backup and then applying incremental changes over time. The other backup types don’t describe this exact pattern: a full backup by itself is only the base; a differential backup collects changes since the last full, not a chain of incrementals; an incremental backup captures changes since the last backup of any kind, not a running full image built from a base plus increments. The combination of a full baseline plus incremental updates is the essence of this approach.

The main idea here is using a baseline full backup and then keeping the rest of the data updated with incremental backups, so you can rebuild the current state by applying the incremental data to that baseline. This approach is efficient because you don’t have to run a fresh full backup every time; you reuse the original full backup and layer on the changes captured by increments. In practice, this is often described as a synthetic or logical full backup, created by combining the initial full backup with subsequent incremental backups to present a complete restore image. That pattern gives fast restores (since you can restore from a single consolidated set) while minimizing the workload and storage needed for full backups.

So the described strategy centers on maintaining a complete, up-to-date restore set by starting with a full backup and then applying incremental changes over time. The other backup types don’t describe this exact pattern: a full backup by itself is only the base; a differential backup collects changes since the last full, not a chain of incrementals; an incremental backup captures changes since the last backup of any kind, not a running full image built from a base plus increments. The combination of a full baseline plus incremental updates is the essence of this approach.