A housing authority colo cage prefers not to run hybrid AI pipelines over the open Internet. Which secure connectivity choice best fits that evaluation?

A housing authority colo cage that prefers not to run hybrid AI pipelines over the open Internet should use a private interconnect or equivalent controlled path for those pipelines. Secure-connectivity evaluation favors paths with stronger isolation and policy attachment—private interconnect, dedicated circuit, or comparable controlled transit—over ad-hoc public Internet exposure for municipal hybrid AI.

Using a private interconnect for offline tape archive replication of hybrid AI pipelines puts the controlled path on tape archive replication rather than on the hybrid AI pipelines, so it does not satisfy the secure-connectivity choice for those pipelines.

Using a private interconnect for facility access telemetry within hybrid AI pipelines scopes the controlled path to facility access telemetry rather than to the hybrid AI pipeline traffic, so it does not meet the requirement for those pipelines.

Using a private interconnect for serial console management of hybrid AI pipelines restricts the controlled path to serial console management rather than to the hybrid AI pipelines themselves, so it misses the evaluated connectivity need.

Exam caveat: Domain 2.5 covers secure connectivity choices for hybrid AI; private or controlled paths are preferred when open Internet risk is unacceptable, but they do not replace identity, encryption, and policy controls.

Operational check: force housing-authority hybrid jobs onto the private interconnect, block equivalent open-Internet routes for those workloads, and verify encryption and auth still apply on the controlled path.