A public-health GPU cluster will run PHI-adjacent clinic triage inference that city policy says must remain inside the municipal data center. Which AI infrastructure type is required?
Select an answer to reveal the explanation.
Short Explanation
When patient-adjacent inference has to stay home, you don't run it on hybrid cloud that's only anchored in the city DC or on colocated racks that are only backed by city systems. On-prem in the city DC keeps residency and operational control with the municipality. Think locked clinic vault, not a dedicated private tenancy that's only connected to the city DC.
Full Explanation
On-premises AI infrastructure inside the city data center is required when PHI-adjacent clinic triage inference must remain under municipal residency and operational control. The correct type works because city policy places the inference workload and its sensitive inputs inside the civic DC boundary, where access control, logging, and sovereignty are municipal responsibilities. Dedicated private tenancy connected to the city data center for residency and control cannot meet that mandate because a connection to the municipal data center is not placement inside the municipal data center boundary.
Dedicated private tenancy connected to the city data center for residency and control fails because policy requires inference to stay inside the municipal data center, not merely connected to it from an outside tenancy. Hybrid cloud infrastructure anchored in the city data center for residency and control fails conceptually because anchoring in the city data center while operating as hybrid still extends workload placement and control outside the municipal data center and undermines residency and operational control. Colocated GPU racks backed by the city data center for residency and control fail for the same residency and control reasons and are the wrong infrastructure class for clinic triage inference under city DC policy because the workload must remain inside the municipal data center, not in a commercial facility that is only backed by city systems.
Exam caveat: on-prem still needs patching, identity, encryption, and monitoring—residency alone does not equal security. Operational check: confirm inference nodes, model stores, and PHI-adjacent feature paths remain inside the city DC, document exceptions, and reject hybrid cloud, colocated, or dedicated private cloud options when policy language requires municipal-data-center placement.
Prefer to study offline? Printable PDF study book + test engine ($7.50, unofficial). These questions stay free here.