An organization wants to move non-essential services into a cloud computing environment.
Management has a cost focus and would like to achieve a recovery time objective of 12 hours.
Which of the following cloud recovery strategies would work BEST to attain the desired outcome?
Click on the arrows to vote for the correct answer
A. B. C. D.C.
When moving non-essential services to a cloud computing environment, it is essential to have a disaster recovery plan in place to ensure that services can be restored in the event of a disruption. The recovery time objective (RTO) of 12 hours is the maximum amount of time that an organization can tolerate for a non-essential service to be down before it starts to impact business operations.
Among the given options, the best cloud recovery strategy that would work to attain the desired outcome of achieving an RTO of 12 hours is to set up a warm disaster recovery site with the same cloud provider in a different region (Option C). Here's why:
Option A: Duplicate all services in another instance and load balance between the instances This approach involves duplicating all services in another instance and load balancing between the instances. While this option would provide redundancy, it may not be cost-effective and may not meet the desired RTO of 12 hours. Additionally, if there is a regional outage or a cloud provider outage, both instances may go down, leaving the organization with no redundancy.
Option B: Establish a hot site with active replication to another region within the same cloud provider This approach involves establishing a hot site with active replication to another region within the same cloud provider. This option is more expensive than a warm disaster recovery site, and while it would provide redundancy and faster recovery times, it may not be necessary for non-essential services. It is also worth noting that if there is a regional outage or a cloud provider outage, both the primary site and the hot site may go down, leaving the organization with no redundancy.
Option C: Set up a warm disaster recovery site with the same cloud provider in a different region This approach involves setting up a warm disaster recovery site with the same cloud provider in a different region. This option is cost-effective and can meet the desired RTO of 12 hours. It would provide redundancy and allow for failover in the event of a disruption in the primary site. A warm disaster recovery site typically has some of the infrastructure pre-configured and can be brought online quickly in the event of a disruption.
Option D: Configure the systems with a cold site at another cloud provider that can be used for failover This approach involves configuring the systems with a cold site at another cloud provider that can be used for failover. A cold site is essentially a backup data center that does not have any infrastructure pre-configured. This option may not meet the desired RTO of 12 hours since it would take time to configure the infrastructure and bring the site online. It may also be more expensive since the organization would need to pay for the standby resources at the other cloud provider. Additionally, if there is a regional outage or a cloud provider outage, both the primary site and the cold site may go down, leaving the organization with no redundancy.
In summary, the best cloud recovery strategy for this organization to attain the desired outcome of achieving an RTO of 12 hours for non-essential services is to set up a warm disaster recovery site with the same cloud provider in a different region (Option C).