mediummultiple choiceObjective-mapped

Exhibit

Disaster recovery review for the customer billing platform

Current backup design:
- Full backup once per day at 23:00
- Backups stored on the same storage cluster as production VM snapshots
- Backup administrator account is shared by the operations team
- Restore test cadence: none in the last 12 months
- Current measured restore time from bare metal: 7 hours

Business recovery targets:
- RTO: 2 hours
- RPO: 15 minutes

Based on the exhibit, which improvement best aligns the current backup design with the stated recovery targets?

Question 1mediummultiple choice
Full question →

Based on the exhibit, which improvement best aligns the current backup design with the stated recovery targets?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Share the backup administrator password in a team chat so any engineer can restore data during an outage.

Credential sharing weakens accountability and increases the chance of unauthorized changes. It does not improve the backup architecture itself.

B

Distractor review

Keep the same design but extend backup retention from 30 days to 90 days.

Longer retention supports archival needs, but it does not improve restore speed or reduce data loss between backups.

C

Best answer

Switch to frequent incremental or snapshot backups stored in a separate, immutable location with routine restore tests.

The business needs a much smaller RPO and a faster RTO than the current design can deliver. More frequent backups reduce the amount of data lost, while a separate immutable repository improves resilience against ransomware and storage failures. Regular restore tests confirm that the chosen method actually meets the recovery objective in practice, not just on paper.

D

Distractor review

Remove backup encryption so restores run faster during an emergency.

Removing encryption creates unnecessary data exposure and does not solve the main issue of backup frequency and repository isolation.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Related practice questions

Related SY0-701 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SY0-701 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Switch to frequent incremental or snapshot backups stored in a separate, immutable location with routine restore tests. — The best improvement is to move to frequent incremental or snapshot-based backups stored in a separate, immutable location, and to validate recovery through regular restore tests. The current design stores backups too close to production and backs them up only once per day, which cannot meet a 15-minute RPO. Restore testing is also missing, so the team has no evidence that the 2-hour RTO is achievable. Why others are wrong: Increasing retention does not make the system recover faster or reduce the amount of data lost between backups. Sharing credentials creates security and accountability issues instead of resilience. Removing encryption would reduce protection without addressing the actual performance and isolation gaps. The core problems are backup cadence, repository independence, and untested recovery.

What should I do if I get this SY0-701 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.