CV0-004 · Question #196
Once a year, a company's private cloud experiences increased activity. The company has a disaster recovery site that is hosted in a public cloud. To avoid investment in additional hardware, which of…
The correct answer is A. Configure cloud bursting to spin up new VMs automatically and terminate them when usage is. Cloud bursting (Option A) is the ideal solution for handling periodic spikes in demand without purchasing additional hardware. It allows the private cloud to automatically overflow workloads into the public cloud when capacity is exceeded, spinning up new VMs on demand and…
Question
Once a year, a company's private cloud experiences increased activity. The company has a disaster recovery site that is hosted in a public cloud. To avoid investment in additional hardware, which of the following actions would BEST address this issue?
Options
- AConfigure cloud bursting to spin up new VMs automatically and terminate them when usage is
- BActivate the disaster recovery site, and deactivate it when usage is back to normal.
- CCreate a new backup site and decommission it when usage is back to normal.
- DManually add memory and CPU to existing VMs, and remove them when usage is back to
How the community answered
(36 responses)- A72% (26)
- B17% (6)
- C6% (2)
- D6% (2)
Explanation
Cloud bursting (Option A) is the ideal solution for handling periodic spikes in demand without purchasing additional hardware. It allows the private cloud to automatically overflow workloads into the public cloud when capacity is exceeded, spinning up new VMs on demand and terminating them when the spike subsides - paying only for what is used. Option B is incorrect because activating the disaster recovery site for routine load spikes misuses it and leaves the company without a true DR fallback during that period. Option C is incorrect because creating a new backup site adds complexity and cost, and decommissioning it repeatedly is operationally inefficient. Option D is incorrect because manually adjusting VM resources is time-consuming, error-prone, and not scalable for an automatic annual event.
Topics
Community Discussion
No community discussion yet for this question.