Recovery time objective is how long you may take to restore service; recovery point objective is how much data you can afford to lose. They pick the strategy: backup and restore is cheapest with a recovery time of hours, a pilot light keeps core pieces running for faster recovery, a warm standby runs a scaled down copy, and active in multiple regions is near instant and most expensive. Both numbers come from the business, not from engineering.
Why interviewers ask this
The interviewer is checking that you can translate a business requirement into an architecture and a budget, rather than proposing the most redundant design available. They want the four tier ladder and the honest cost curve. They also usually probe whether you test recovery, since a disaster recovery plan that has never been exercised has a recovery time of unknown rather than the number written down.
How to structure your answer
- Define both terms in plain language with units of time.
- Map the strategy ladder to the numbers and the cost.
- Insist the numbers come from the business per workload.
- Cover testing, because untested recovery is not recovery.
Example answer
Recovery time objective is how long the business can be down; recovery point objective is how much recent data it can lose. Both are business decisions, and my job is to translate them into a design and a price so someone can make an informed choice. If they say four hours down and one hour of data loss, that is backup and restore with frequent snapshots, which is cheap. If it is thirty minutes and near zero data loss, we are into a warm standby with continuous replication, which costs real money. Near instant with no loss means active in two regions and a very different application design, and that is a conversation about whether an hour of downtime genuinely costs more than the architecture. The important nuance is that the numbers differ per workload; checkout and the internal reporting tool do not deserve the same investment. And I insist on testing, a scheduled restore into a clean environment where we time it end to end, because the first time I did that the documented four hour recovery turned out to be eleven, mostly spent finding credentials.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- How do you verify a backup is actually restorable?
- What is your plan when the recovery depends on a service that is also down?
- How often would you run a full recovery exercise?
Related cloud engineer questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions