SK0-003 · Question #163
Which of the following backup methodologies is MOST time efficient for restoring data?
The correct answer is C. Full. A full backup methodology is the most time-efficient for restoring data because all necessary data is contained within a single backup set. This eliminates the need to combine multiple backup sets or calculate changes from various points in time, streamlining the recovery…
Question
Which of the following backup methodologies is MOST time efficient for restoring data?
Options
- AIncremental
- BDifferential
- CFull
- DGFS
How the community answered
(35 responses)- A3% (1)
- C94% (33)
- D3% (1)
Why each option
A full backup methodology is the most time-efficient for restoring data because all necessary data is contained within a single backup set. This eliminates the need to combine multiple backup sets or calculate changes from various points in time, streamlining the recovery process.
Incremental backups require the original full backup and all subsequent incremental backups up to the restore point, making the restore process complex and time-consuming.
Differential backups require the original full backup and the latest differential backup, which is less complex than incremental but still involves two backup sets and potentially more data than a full restore.
A full backup is the most time-efficient for restoring data because it contains an entire copy of all data from a specific point in time in a single backup set. When a restore is needed, only this one backup set needs to be accessed, minimizing the steps and time required to recover the data compared to methodologies that require combining multiple backup files.
GFS (Grandfather-Father-Son) is a backup rotation scheme, not a backup methodology that defines what data is backed up, so it's not directly comparable in terms of restore efficiency.
Concept tested: Backup methodologies restore efficiency
Source: https://www.ibm.com/docs/en/spss-analytic-server/3.4.0?topic=backups-planning
Topics
Community Discussion
No community discussion yet for this question.