Explanation/Reference:
Explanation:
In a hot standby disaster recovery scenario, you set up a failover farm in the standby data center so that it can assume production operations almost immediately after the primary farm goes offline. An environment that has a separate failover farm has the following characteristics:
A separate configuration database and the SharePoint Central Administration website content database

must be maintained on the failover farm.
All customizations must be deployed on both farms.

Operating system, SQL Server and SharePoint Server software updates must be applied to both farms,

to maintain a consistent configuration across both farms.
You can copy SharePoint Server content databases to the failover farm by using asynchronous

mirroring, asynchronous commit on an availability group replica, or log-shipping.
Service applications vary in whether they can be log-shipped to a farm.

The hot standby farm topology can be repeated across more than one data center, as long as you configure SQL Server log shipping to one or more additional data centers.
Scenario: Disaster recovery requirements
You must use the secondary datacenter in Chicago for disaster recovery.

You must be able to recover the Chicago.contoso.com SharePoint farm to the secondary datacenter.

Any recovery operations must complete in less than five minutes if the primary datacenter fails.
You must minimize the costs associated with deploying the disaster recovery solution.

References:
https://docs.microsoft.com/en-us/sharepoint/administration/plan-for-disaster-recovery