Sensitive resident datasets must stay on-premises, but the city wants to burst heavy model training into public cloud capacity. Which model describes that design?
Select an answer to reveal the explanation.
Short Explanation
Hybrid is the split house: crown jewels stay on-prem, heavy lifting can burst to public cloud. Sensitive resident data need not block all elastic compute. Two sides, one coordinated plan.
Full Explanation
Hybrid cloud combines on-premises or private resources with public cloud capacity so organizations can keep sensitive datasets local while bursting compute outward. That pattern fits municipal constraints that forbid wholesale public replication of protected resident data yet still need elastic training or analytics. Public-only defaults, total cloud abandonment, or media-only storage miss the hybrid Chapter 9 model. Architects choose placement by data sensitivity and workload shape.