Computer-aided dispatch stays in the city datacenter while the public website bursts to a provider, and both environments operate together. Which model is this?
Select an answer to reveal the explanation.
Short Explanation
CAD stays home in the datacenter; the website rides the public cloud when traffic spikes — and they work as a team. That mix is hybrid cloud. It is not 'everything public' and not a lonely laptop.
Full Explanation
Hybrid cloud combines private or on-premises systems with public cloud so both environments operate together as part of one architecture. Computer-aided dispatch remaining in the city datacenter while the public website bursts to a provider is a canonical hybrid pattern: sensitive or latency-local systems stay private while elastic citizen web capacity uses public cloud. Public-only cloud with no on-premises workloads remaining does not describe CAD staying in the city datacenter. Community cloud used exclusively by unrelated retail franchises is the wrong sharing model and constituency for this municipal design. A single laptop running all municipal services offline is neither hybrid nor an acceptable resilient city architecture. Exam caveat: hybrid is about operating across private/on-premises and public together—not merely having a VPN, and not identical to multicloud across two public providers without an on-premises component. Operational check: define which workloads stay on-premises versus burst to public cloud, secure connectivity between CAD and public web tiers, test failover and data flows, monitor both environments in one operations view, and keep identity and logging consistent across the hybrid boundary.