MidStorage

What does a solid backup strategy look like?

What they are really testing: Whether you know the 3-2-1 rule, that backups must be tested by restoring, and that immutable/offsite backups protect against ransomware. The classic failure is untested backups that do not restore.

A real interview question

What does a solid backup strategy look like?

What most people say

drag me

I would schedule regular backups of the database to cloud storage.

Scheduling backups is necessary but not sufficient. Without testing restores you may find they are unusable in a disaster; without offsite/immutable copies, one event (or ransomware) takes out both prod and backups. The 3-2-1 rule and restore testing are the point.

The follow-ups they ask next

  • Why is testing restores the most important part?

    Backups fail silently (corrupt, incomplete, misconfigured). If you never restore, you only find out during a real disaster, when it is too late. Regular test restores prove they work and measure your true RTO.

  • How do immutable backups protect against ransomware?

    WORM/air-gapped backups cannot be deleted or encrypted, even by a compromised account, so the attacker cannot destroy your recovery path along with production. Reachable, mutable backups can be encrypted in the same attack.

What the interviewer is listening for

  • Knows 3-2-1 rule
  • Insists on testing restores
  • Immutable/offsite + automate + align to RPO/RTO

What sinks the answer

  • Just "schedule backups"
  • Never tests restores
  • Backups reachable/mutable from prod access

If you genuinely do not know

Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.

A solid strategy: [3-2-1, three copies, two media types, one offsite] so no single failure takes out prod and backups. Critically [test restores regularly, an untested backup is not a backup, and it measures real RTO]. Make backups [immutable/air-gapped so ransomware cannot delete/encrypt them]. [Automate and monitor success, and set frequency/retention to meet RPO/RTO].

Keep going with storage

All 336 cloud engineer questions

Knowing the answer is not the same as recalling it under pressure

Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.

Start free