County counsel requires certain 911 audio-derived features to remain in the municipal data center, while data science may use cloud GPUs for non-sensitive model experiments. Which infrastructure placement matches this policy?

Hybrid placement that keeps residency-bound 911 audio-derived features in the municipal data center while allowing cloud GPUs for non-sensitive experiments matches counsel’s split policy. The correct infrastructure works because sensitive corpora stay under on-prem residency and control, yet data science retains elastic cloud compute for experiments that are not sealed. Hybrid is the pattern when one municipality must satisfy both residency and elasticity without collapsing to a single extreme. Hybrid placement that keeps residency-bound data on-prem while using cloud GPUs for tokenized residency extracts fails because tokenized extracts of residency-bound 911-derived features remain residency-bound derivatives, so running them on cloud GPUs moves sealed data outside the municipal data center instead of limiting cloud to non-sensitive experiments. Edge processing for feature extraction with on-prem residency store and cloud GPUs for anonymized residency reruns fails because rerunning residency-bound outputs on cloud GPUs moves sealed 911-derived features outside the municipal data center, and anonymization alone does not reclassify them as non-sensitive eligible for cloud. Hybrid placement that keeps residency-bound data on-prem while using cloud GPUs for encrypted residency backups fails because placing encrypted residency backups on cloud GPUs still places sealed 911-derived features in the cloud, and encryption does not satisfy the municipal-data-center residency requirement nor qualify as a non-sensitive experiment. Exam caveat: "non-sensitive" must be classified rigorously—feature leakage, embeddings, or weakly anonymized audio derivatives can still be regulated. Operational check: inventory which 911-derived assets are residency-bound, tag experiment datasets as eligible for cloud, enforce network/data egress controls from the sealed zone, and verify hybrid runbooks that keep sealed features on-prem rather than running tokenized residency extracts, anonymized residency reruns, or encrypted residency backups on cloud GPUs.