Compare hot site, warm site, and cold site in disaster recovery planning.

Compare hot site, warm site, and cold site in disaster recovery planning.

• A. Hot site is ready to run immediately with up-to-date data; warm site requires setup and data restoration; cold site is a basic facility with minimal readiness.
• B. Hot site requires setup; warm site is always ready; cold site has up-to-date data.
• C. Hot site stores backups on tapes; warm site uses cloud; cold site uses remote mirroring.
• D. Hot site is only used for testing; warm site is for development; cold site is for production.

Answer: (A)

Understanding disaster recovery site types starts with how quickly operations can resume and how current the data will be after a failover. A hot site is configured to run in parallel with production and has up-to-date copies of the data, so you can switch over immediately with minimal disruption. A warm site has the infrastructure in place but requires some setup and data restoration before it can take over, so the failover takes more time and the data may not be as current. A cold site is simply a basic facility with power and space; there are no active systems or current data, so bringing it online involves provisioning hardware and restoring data from backups, which takes the longest. The description in the option aligns with this: a hot site is ready to run immediately with up-to-date data; a warm site requires setup and data restoration; a cold site is a basic facility with minimal readiness. The other options don’t fit these patterns—for example, claiming a warm site is always ready, or that a cold site has up-to-date data, or that hot sites are used only for testing—these ideas contradict the practical differences in readiness and data availability that define hot, warm, and cold sites.

Understanding disaster recovery site types starts with how quickly operations can resume and how current the data will be after a failover. A hot site is configured to run in parallel with production and has up-to-date copies of the data, so you can switch over immediately with minimal disruption. A warm site has the infrastructure in place but requires some setup and data restoration before it can take over, so the failover takes more time and the data may not be as current. A cold site is simply a basic facility with power and space; there are no active systems or current data, so bringing it online involves provisioning hardware and restoring data from backups, which takes the longest.

The description in the option aligns with this: a hot site is ready to run immediately with up-to-date data; a warm site requires setup and data restoration; a cold site is a basic facility with minimal readiness. The other options don’t fit these patterns—for example, claiming a warm site is always ready, or that a cold site has up-to-date data, or that hot sites are used only for testing—these ideas contradict the practical differences in readiness and data availability that define hot, warm, and cold sites.