A water utility checks whether cloud landing zones and identity controls exist before hosting an AI platform. What readiness dimension is being assessed?
Select an answer to reveal the explanation.
Short Explanation
Before parking an AI platform in the cloud, you need a paved landing zone and badge checks at the door—identity, network, guardrails. That plumbing check is technology readiness, not hydrant paint debates.
Full Explanation
Checking whether cloud landing zones and identity controls exist before hosting an AI platform assesses technology and infrastructure readiness for secure AI platform hosting. Landing zones, IAM, network segmentation, logging, secrets management, and platform guardrails are prerequisites when municipal AI workloads may touch sensitive operational or resident data. Assessing these controls early reduces civic platform risk, audit findings, and costly redesign after departments onboard. Whether residents prefer blue or green hydrant paint is aesthetic preference, not infrastructure readiness for AI. Poetry quality of the utility’s annual report is communications craft unrelated to hosting controls. The number of unused picnic permits in parks systems is an unrelated program metric that says nothing about cloud landing-zone fitness. Exam caveat: infrastructure readiness is not measured by unrelated civic aesthetics or cross-department trivia. Operational check: verify landing-zone standards and account vending, enforce least-privilege identities for model and data endpoints, confirm network segmentation and private connectivity patterns, enable audit logging and key management, harden CI/CD for model artifacts, and only then onboard department AI workloads to the shared utility or city platform.