Skip to main content
RunBook Academy

← All assessments

Final assessment · advanced · ~90 min · pass ≥ 80%

Backup, Restore & Disaster Recovery for Production Infrastructure — Final Theory Assessment

Objectives

  • Reason about a recovery failure from evidence rather than from the symptom that was reported
  • Distinguish a control that is enforced from one that depends on an administrator behaving
  • Predict what a backup estate does in the situations where the intuitive answer is wrong
  • Derive an RPO and an RTO from an architecture instead of quoting one from a product
  • Identify the monitoring gap that let a given loss of recovery capability go unnoticed

25 graded questions · last verified 2026-08-28

Assessment questions

Objective questions are scored automatically. Scenario answers use a second-stage rubric for evidence, remediation, and rollback.

Knowledge check · 25 questions

  1. Q1. A nightly integrity check on a deduplicating repository has reported success every night for six months. What does that establish about the stored data?

  2. Q2. Ten bytes are overwritten in the middle of an existing repository data file. Which observation would reveal the damage without reading and re-hashing the contents?

  3. Q3. A service is backed up nightly at 01:00 with no continuous mechanism. It fails at 20:00. What is the honest RPO statement for this architecture?

  4. Q4. A team quotes a four-hour RTO. Their only offsite copy is in an archive tier whose documented retrieval latency is measured in hours before any transfer begins. What is the correct characterisation?

  5. Q5. A file-level copy of a running database directory is taken under write load. It starts, completes crash recovery, and returns every expected row. What has been demonstrated?

  6. Q6. Production data lives on one storage array with hourly snapshots retained for two weeks. The array is destroyed. What recovery capability do the snapshots provide?

  7. Q7. A fixed-size copy-on-write snapshot is taken of a busy volume and the volume is then heavily rewritten. What consumes the snapshot space?

  8. Q8. An organisation stores its backup repository passphrase in a file on the server being backed up, so the nightly job can run unattended. The site is destroyed and the offsite repository is intact. What is the recovery position?

  9. Q9. A backup object is protected by a retention mode that an administrator can override by passing a bypass permission. Which threat does that protect against?

  10. Q10. An estate mirrors production to a second site every night with deletion propagation enabled. An operator deletes a directory at 14:00. What is the state of the mirror at 02:00?

  11. Q11. A cluster-state snapshot is restored after a control-plane loss. A workload that was scaled up after the snapshot returns at its earlier replica count, and a configuration object created after the snapshot is absent. What has happened?

  12. Q12. A team keeps every application manifest in version control and treats that repository as their cluster backup. The cluster and its storage are lost. What comes back from the manifests?

  13. Q13. A repository is damaged and a restore of a listed recovery point reports a non-zero exit status while writing most of the expected files. What is the correct interpretation?

  14. Q14. A recovery has completed and the database accepts connections. Which observation would justify declaring the recovery successful?

  15. Q15. Which of these are established by a backup job that exits zero? Select all that apply.

  16. Q16. Two copies of a dataset are held. Which conditions would make them NOT independent? Select all that apply.

  17. Q17. A retention mode that refuses deletion for a fixed window still leaves which risks open? Select all that apply.

  18. Q18. Which items are commonly absent from an estate inventory and stop a recovery when they are? Select all that apply.

  19. Q19. A restore that writes files to disk and exits non-zero can leave corrupt files whose names and sizes look entirely correct.

  20. Q20. Enabling deletion-refusing retention on a bucket that already holds a year of backups is a configuration change that can be applied at any time.

  21. Q21. A backup mechanism whose repository is append-only necessarily refuses commands that delete recovery points.

  22. Q22. Measuring how long a backup takes gives a useful estimate of how long the corresponding restore will take.

  23. Q23. An estate holds three copies of its data. State the single test that determines whether the copy count means anything, and name the axis of independence that estates most often fail to model.

  24. Q24. A ransomware event is confirmed. Explain why the newest recovery point is usually the wrong one to restore, and what has to be established before any recovery point is chosen.

  25. Q25. Produce the evidence you would gather, the remediation you would apply, and the rollback you would hold in reserve.

    A service has been backed up nightly for two years to a repository on a NAS, using credentials stored on the application server. The dashboard shows 99.8% job success. The team has never performed a restore. The repository is also synchronised each morning to a second NAS in another building using a mirroring tool with deletion propagation enabled. The encryption passphrase is in a file on the application server so the job can run unattended. A director asks whether the service could be recovered after a ransomware event.

Passing score: 80%. Answers are checked in this browser.

Backup, Restore & Disaster Recovery — Final Theory Assessment

This assessment grades reasoning, not recall. Almost every question puts you in front of a situation that a real estate produces and asks what you would conclude from it. It is weighted deliberately toward the cases where the intuitive answer is wrong, because those are the cases that produce unrecoverable estates — and because an engineer who gets them right without the course would not have needed it.

The pass mark is 80% and the attempt is designed to fit ninety minutes. The questions are not evenly difficult, and several of them have a plausible answer that a competent engineer would give.

What is being measured

Six competencies run through the whole bank, and every question maps to at least one of them.

  • Claim discipline. You can say which claim a piece of evidence actually supports, and you refuse to let a job result stand in for a statement about data, keys or elapsed time.
  • Independence reasoning. Given a set of copies, you can name the single event that destroys more than one of them, and you treat the security domain as an axis rather than an afterthought.
  • Objective derivation. You derive an RPO from a schedule and a failure model and an RTO from a stage-by-stage budget, rather than quoting either from a product datasheet.
  • Consistency literacy. You can distinguish crash-consistent from application-consistent, and you recognise the third case that neither term covers and that usually appears to work.
  • Enforcement over vocabulary. You can say what a retention control enforces, against which caller, and for how long, and you name its boundaries in the same breath.
  • Recovery sequencing. You derive an order from a dependency graph rather than from business preference, and you recognise a cycle before an incident does.

How to read the questions

Where a question describes a belief held by a team, a figure circulated to a business, or a result reported by a dashboard, that belief, figure or result is part of the material and may be wrong. Several questions are built on results the course measured rather than asserted: a structural check passing on a repository that cannot restore, a file-level copy of a live database that starts and returns every row, an append-only repository that permits deletion, and an object-lock configuration that a platform refuses on an existing bucket.

Two habits are worth carrying into the attempt. When an option is attractive because it names an action, check whether the action produces evidence or only activity. And when a question asks what a defect affects, check the headings it does not touch — an answer that makes everything urgent is not thorough, it is undiscriminating.