911 radio logging must stay on-premises for latency and legacy gear, but analytics can run in Azure. Which cloud model should the city select?
Select an answer to reveal the explanation.
Short Explanation
Leave the finicky radio logging where the gear already lives; send the analytics to Azure. That split is hybrid in a sentence. Forcing everything public or everything private ignores the real constraints.
Full Explanation
Hybrid cloud is the model that keeps some systems on-premises while using public cloud for others. 911 radio logging that must stay local for latency and legacy gear, paired with analytics in Azure, matches that split exactly. The city should select hybrid rather than forcing every component into one extreme.
Relocating latency-sensitive radio logging into shared public tenancy immediately ignores the stated constraints. Blocking any Azure analytics under a private-cloud-only rule discards allowed public-cloud value. Claiming SaaS-only dashboards remove the need for any logging system invents a replacement that the scenario does not provide.
Exam caveat: hybrid success depends on secure connectivity, identity alignment, and clear data classification across the boundary—not merely “some VMs here, some there.” Operational check: document why logging must remain local, define what telemetry may leave the premises for Azure analytics, and verify latency and retention requirements still hold after the split. Hybrid designs for public safety should explicitly state what leaves the premises: raw radio recordings may stay local while aggregated metrics or non-sensitive derived analytics land in Azure. That data-flow clarity prevents accidental relocation of regulated logging content under an “analytics in the cloud” slogan.