A financial-services company in the United States must comply with regulations that require all personally identifiable information (PII) to remain on-premises. However, the firm sees a sharp but temporary rise in compute demand at the close of every fiscal quarter and wants to off-load only the extra, non-sensitive processing to a third-party IaaS provider instead of buying additional in-house hardware. Which cloud deployment model best satisfies both the regulatory data-residency requirement and the need for on-demand bursting during peak periods?
A hybrid cloud joins at least two distinct infrastructures-typically a private (on-premises) cloud holding sensitive data and a public provider used for elastic workloads-and links them with technology that permits cloud bursting and application portability. This lets the firm keep regulated PII inside its own data centers to meet compliance mandates, yet burst excess compute to the public cloud only when needed.
Public cloud alone would place the regulated data outside the company's control, violating residency rules. A private-only cloud would satisfy compliance but cannot elastically scale without new capital purchases. Community cloud is intended for multiple organizations with shared concerns, not for mixing a single company's private resources with a public provider.