A city archives department stores low-priority historical photo scans that can tolerate days of downtime after a loss. Leadership wants the most cost-effective continuity design that still meets a long RTO. Which approach best fits?
Select an answer to reveal the explanation.
Short Explanation
A dusty photo archive that can wait days does not need a second city always running lights-on. Back it up, practice the restore, and skip the hot-standby tax until the RTO actually demands it.
Full Explanation
When recovery time and recovery point objectives allow slow recovery, backup and restore is an appropriate business-continuity tier and is typically far cheaper than pilot light, warm standby, or multi-site active-active. Continuously running multi-Region hot capacity and Global Database standby fleets overspend against a long RTO for low-priority archives. Storing uniquely on a single workstation without backups fails durability and recoverability requirements.