Data Backup and Recovery Quiz

Practice status

Build a practice round

Practise backup and recovery decisions with 24 original scenarios across eight lifecycle topics. This curated practice does not certify compliance or prove that your systems can recover.

Context:

Lifecycle topic:

Difficulty:

Feedback timing:

Question count:

Source release: 11 September 2026. NIST SP 800-34 Rev. 1 (2010 update), with Australian Cyber Security Centre backup guidance. General learning; no jurisdiction-specific compliance assessment.

Scope and sources

Uniform selection from the chosen pool; small filters may contain one question. Difficulty labels describe scenarios, not validated ability levels. No vendor procedures, exam blueprint or guaranteed recovery outcome.

{{ source.reference }} — {{ source.version }}

Replay seed:

Optional: leave blank for the default seed, or use 1–128 characters to reproduce a round.

{{ answeredCount }} of {{ questionCount }} answered · {{ displayProgressPercent }}%

Question {{ quizCursor + 1 }} of {{ questionCount }}

Source: {{ currentResultRow.source.reference }} · {{ currentResultRow.source.version }} · {{ currentResultRow.source.license }}

Answer recorded. Corrections appear at the end of the round.

Review what to practice next

Missed answer review

{{ item.prompt }}

Your answer: {{ item.selected_answer_label }}

Correct answer: {{ item.correct_answer_label }}

{{ item.explanation }}

Source: {{ item.source.label }} · {{ item.source.version }} · {{ item.source.license }}

Lifecycle performance

Which backup lifecycle topics need review? Counts describe only the questions in this round; untested topics are omitted.

Loading topic-performance chart…

Answer ledger

Question ID	Prompt	Topic	Your answer	Correct answer	Outcome	Explanation	Source	Copy
{{ row.question_id }}	{{ row.prompt }}	{{ row.category_label }}	{{ row.selected_answer_label }}	{{ row.correct_answer_label }}	{{ row.outcome_label }}	{{ row.explanation }}	{{ row.source ? `${row.source.label} · ${row.source.version} · ${row.source.license}` : '—' }}

A synchronized folder with no retained versions can copy an accidental deletion to every connected device. Several matching copies may therefore leave no usable copy to restore. A backup preserves data for later restoration, while recovery is the work needed to make the required files or service usable again.

For a household, recovering family videos may depend on data stored only on phones, outside a desktop-only backup. An ordering service needs more than its sales records. Its application, configuration and supporting services may also be necessary. The recovery goal determines what belongs in a backup. Backing up more often cannot repair a gap in what was included.

Keeping a protected copy at another location can prevent one theft or damaging event from removing every copy. Access restrictions address a different risk. Disconnecting removable backup media after use reduces its exposure to malicious software on the working computer. Disk mirroring can help with some hardware failures, but does not by itself preserve a directory from before it was deleted. Retaining earlier versions matters when corruption or an unwanted edit is discovered after newer backups have already captured it.

Recovery planning also separates three time-related decisions that are often confused.

Recovery point objective (RPO): How far back the recovered data may be relative to the disruption, commonly expressed as an acceptable window of lost changes.
Recovery time objective (RTO): The target limit on time from disruption to restoring the specified system or service.
Retention: How long backup versions remain available, including older versions that may be needed after delayed discovery of a problem.

A short data-loss allowance calls for sufficiently recent, usable recovery points. A long retention period serves a different purpose by preserving history. Neither setting tells you how quickly a service can be rebuilt. Appropriate choices depend on the importance of the data, how it changes, the effects of an outage and the recovery resources available. A schedule alone provides no assurance that its jobs finished successfully.

During a restore exercise, a recovered document can be opened and its contents inspected. That checks more of the recovery process than reading a success notification. Recovering a service also tests its dependencies, access arrangements and operating instructions. Tests need a controlled scope that avoids unintended changes to live records, with findings used to correct problems and retest the affected steps.

Loss of the original machine must not leave authorized people unable to reach recovery instructions or decryption keys. After a security incident, restoring files also does not remove an unresolved route of compromise. Understanding backup principles supports planning and learning, but cannot establish that a particular system is ready to recover or safe to reconnect.

How to Use This Tool:

Build a broad practice round or concentrate on one backup decision. The question set contains 24 original text scenarios across eight lifecycle topics, with three scenarios per topic and eight in each of the three contexts. The eligible pool is the intersection of context, topic and difficulty. Selection gives those questions equal weight, and no question repeats within a round.

Choose a Context, Lifecycle topic and Difficulty. The starting selection is All contexts, All lifecycle topics and Mixed difficulty. Contexts include Home & home lab, Small business and System administration. Unavailable difficulty choices are disabled; changing scope can return the difficulty to Mixed difficulty.
Choose the Question count from the available options. The default broad round has six questions, with 1, 3, 6, 12 or 24 available for the whole bank. Filtered rounds use the presets 1, 3, 6 and 12 that fit, plus the full pool size. A narrow selection can contain just one question, and a count that no longer fits is adjusted after a scope change.
Choose Feedback timing. Learn — feedback after each answer is the default and reveals the explanation before you advance. Review — feedback at the end records each choice without revealing its correctness during the questions. If Start practice is disabled, reselect an available scope, feedback timing and question count.
Under Advanced, an optional Replay seed accepts 1 to 128 characters. Leaving it blank uses a fixed default seed, not a fresh random draw. If a seed notice appears, enter a custom seed within that limit; the default is used otherwise. The same settings and seed reproduce the question and option order while the quiz version remains unchanged.
Select Start practice, then choose one of the four answers to each scenario. Selecting an answer records and locks it immediately in either feedback mode. There is no separate submission step for confirming or changing that choice.
Advance with Next question after each recorded answer. After answering the final question, select View results and begin with Missed answer review. Every selected question must be answered before a completed result is available; questions cannot be skipped to finish early.

Interpreting Results:

During a round, Practice status and the progress percentage describe how many questions you have answered, not how many you got right. At completion, the main fraction changes to correct answers out of the round's question count. Perfect round means there were no misses in that attempt.

Lifecycle performance shows counts of Correct and Missed answers for the topics actually sampled. A short round is not guaranteed to balance topics, and untested topics are omitted rather than rated. Suggested review focus points to a topic with the most misses, not a validated estimate of your weakest skill. Use the explanations and sources in the Answer ledger to identify the specific decisions to revisit.

Retry missed starts a new attempt containing only wrong answers from the completed round. It is absent after a perfect round. Replay same seed repeats the current round's questions and option order. Try a new seed changes the seed, but questions can recur within the finite pool. Compare scores cautiously when the scope or question count changes, or when you have already seen the explanations.

The question set is dated 11 September 2026 and offers curated learning, not exhaustive coverage, official questions or an endorsed certification assessment. Foundations and Applied decisions describe the scenarios, not validated ability levels. A high score does not demonstrate professional competence, successful recovery or jurisdiction-specific compliance. Actual confidence requires reviewing the relevant backup coverage and conducting authorized recovery checks.

Technical Details:

Recoverability requires a complete route from retained data to a usable result. An archive may be readable while the application remains unavailable because its settings, decryption key or supporting services are missing. Backup decisions therefore need evidence that addresses the particular failure being considered.

Lifecycle decision rules

Backup lifecycle decisions and the evidence needed to evaluate them
Lifecycle topic	Governing principle	Useful evidence
Backup scope	Recovery cannot supply excluded data or missing application dependencies. Priorities follow business impact and service dependencies.	An inventory of important data, required software and settings, with a justified recovery order.
Copies & locations	Copies in one place can share a physical loss. Live mirrors can share deletion or corruption.	A protected copy outside the affected location and recoverable versions independent of the unwanted change.
Isolation & access	A backup remains exposed to accounts that can modify or delete it. Retention protection needs actual enforcement.	Checks of permitted access and deletion, including relevant privileged accounts during the retention period.
Retention & monitoring	The latest copy may already contain damage. A failed scheduled job is not a new recovery point.	Usable historical versions, completed-job records and an owner who receives and acts on failure alerts.
Restore verification	A successful backup operation does not exercise every restoration dependency.	Recovered contents that can be opened, or a working service restored in a controlled test, including required key access.
Recovery objectives	Data recency and service recovery duration are separate requirements. File transfer may finish before service recovery.	The recovered data's point in time and elapsed time to the specified usable service, checked against their respective targets.
Recovery planning	Recovery depends on people, authority, reachable instructions and supporting services, not only backup files.	Current contacts, named responsibilities and documented dependency order available during the relevant outage.
Lessons & maintenance	A previous exercise describes the configuration it tested. Changed data locations, contacts or security conditions need follow-up.	Updated procedures and repeat checks of corrected steps, coordinated with incident response where compromise is involved.

Immutability means preventing modification or deletion for a defined retention period. A product label or an ordinary user's denied access does not establish that all relevant privileged roles are constrained. Testing those permissions needs an authorized, controlled arrangement that does not endanger the only recovery copy. Encryption addresses confidentiality, while recoverable key access remains a separate requirement for reading encrypted backups.

Recovery targets also need a defined scope. For an application-service RTO, timing includes the work needed to make that application usable, not just moving its files. For RPO, the relevant point is the data that can actually be recovered. A nominal backup interval is not proof of that point when jobs have failed or required copies are inaccessible. Backup frequency and retention should follow continuity needs and applicable requirements; no universal retention period is prescribed here.

Practice score and progress

Each correct choice earns one point and each incorrect choice earns zero. Accuracy divides correct answers by all questions selected for the attempt. Progress instead divides recorded answers by that same question count.

\begin{array}{l} Score points = C \\ Accuracy (%) = 100 \times \frac{C}{N} \\ Progress (%) = 100 \times \frac{A}{N} \end{array}

N is the selected question count, A is the number answered and C is the number correct. All three are whole-number question counts, with N greater than zero and 0 ≤ C ≤ A ≤ N. The possible score is N points, with a range from zero to N. Questions have equal weight, with no partial credit, reverse scoring or negative marking.

How correct, incorrect and unanswered questions affect the practice score
Answer state	Points earned	Counting rule
Correct	1	Counts as answered and correct.
Incorrect	0	Counts as answered and missed.
Not answered	0	Remains in the selected total, but is neither an answered question nor a miss.

Completion requires A to equal N; a perfect round additionally requires C to equal N. Topic totals count the same correct and incorrect answers within each sampled topic. There is no official pass mark or proficiency band.

Accuracy and progress retain their unrounded values. Only visible progress is rounded to the nearest whole percent, with half-percent ties rounded upward. For example, answering two questions in a six-question round produces 33% displayed progress, regardless of whether either answer is correct. The completed score is presented as the exact correct-count fraction.

Privacy and Saved Attempts:

Answers are scored in your browser. No files, devices, backup jobs or restore targets are examined, and the quiz does not ask for backup credentials. The page address can retain the setup, seed, answers and current position, including an unfinished attempt. Someone receiving that address can restore the recorded choices. Saved responses are encoded, not encrypted, so sharing the link can disclose your answers.

Saved addresses may enter browser history or be transmitted when opened or shared. Chart display can also load third-party software. Browser scoring therefore does not imply that the page makes no network requests. Avoid putting passwords, recovery keys or sensitive information in a replay seed.

Change setup clears the current attempt and removes the saved attempt from the current page address, but cannot erase copies already shared or stored elsewhere. If Saved attempt unavailable appears, the attempt cannot be reopened, for example because the question set or saved-attempt format has changed. Choose the desired setup and start a new round. Saved links are not an account-based progress history.

Worked Examples:

Separating data loss from service recovery

Choose All contexts, Recovery objectives, Mixed difficulty, three questions and end-of-round feedback. Identify the one-day data-loss allowance as RPO, but incorrectly label the four-hour service target as RPO and choose 40 minutes rather than 95 minutes for the application-recovery scenario. The completed result is 1/3, with one correct and two missed answers under Recovery objectives. The explanations distinguish the RTO target from RPO and show why the usable-service time is 95 minutes: 40 minutes for transfer plus 55 minutes for the remaining recovery work. Retry missed then creates a separate two-question attempt, rather than adding points to the original result.

A perfect answer to a narrow scope question

Choose Home & home lab and Backup scope with mixed difficulty. Only one question is available. Selecting the answer that includes the phones' important data in the backup plan produces 1/1 when the round is completed. Only Backup scope is represented in the topic results. A new seed cannot add another scenario to this one-question pool. The learning action is to check whether the phone videos really are captured and restorable; the quiz answer has not inspected them.

References:

SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems, National Institute of Standards and Technology, May 2010, updated 11 November 2010.
Information Security Manual: Guidelines for system management — data backup and restoration, Australian Signals Directorate's Australian Cyber Security Centre, 7 September 2026.
Personal cyber security handbook: Secure your devices — backups and ransomware, Australian Signals Directorate's Australian Cyber Security Centre, 7 October 2026.