hot site and cold site

The most basic form of Disaster Recovery is called Cold, because there are no active (“hot”) services running at a different location (Disaster Recovery site) and all services are provided from a single location or data center.

In the other extreme, there is Hot Disaster Recovery, which provides no down-time (zero RTO) and updated data everywhere (zero RPO).

In between Cold and Hot Disaster Recovery there is a continuum of intermediate RTO/RPO requirements called Warm Disaster Recovery. These setups can be closer to either extreme, Cold or Hot, according to Business requirements and available budget.
https://cloudnow.co.il/the-differences-between-hot-warm-and-cold-disaster-recovery-dr/

Types of Backup Sites - Hot Site, Warm Site, Cold Site
https://www.omnisecu.com/ccna-security/types-of-backup-sites.php

VMware perfomance

HOL-2004-01-SDC - Mastering vSphere Performance
https://labs.hol.vmware.com/HOL/catalogs/lab/6424

https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-esxi-vcenter-server-67-resource-management-guide.pdf

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/performance/vsphere-esxi-vcenter-server-67-performance-best-practices.pdf

Exchange questions

Select scenarios which don’t provide load balancing:
A. Multiple Source Servers for Send Connector in the same AD Site
B. Source Transport Servers for Send Connector in different remote AD Sites
C. Multiple Send Connectors with Equal Cost
D. Message Relay from an Edge Transport Servers to a Mailbox Servers

You have a lagged copy for a database. What are requirements for transaction logs to be truncated from disk for that database (active and non-lagged copies)?
A. Logs should be copied, verified and replayed to lagged copy
B. Logs should be copied and verified on lagged copy
C. Logs should be copied and verified for lagged copy, backup should be passed successfully or circular logging enabled for database