A large finance firm processes three times as many transactions in December of each year. The transactions are processed in a private cloud. Management wants to avoid adding permanent resources to…

Migrating all processing to a public cloud and sizing for peak demand would incur unnecessary costs for the 11 months of lower usage, rather than just handling the spike without permanent resource additions.

Cloud bursting allows an application running in a private cloud to "burst" or expand its capacity into a public cloud during peak loads, such as the December transaction spike. This strategy leverages the elasticity of the public cloud to temporarily scale resources as needed, preventing the need for the private cloud to provision permanent, underutilized infrastructure for seasonal demands. Once the peak load subsides, the application can scale back to the private cloud, optimizing cost and resource utilization.

Virtualizing processing traffic in the private cloud does not inherently add capacity beyond the physical resources available; it's a way of managing existing resources but doesn't solve the need for more capacity during peak times without adding permanent hardware.

Adding physical resources to accommodate seasonal needs directly contradicts the management's desire to avoid adding permanent resources.