A bank's platform team wants a new landing zone that contains only AI workloads. The bank already operates a landing zone with an approved governance baseline. What should the architect do?
Select an answer to reveal the explanation.
Short Explanation
Pouring a second foundation beside a building the inspectors already approved splits the rules in two. You extend the bank's existing landing zone and keep the governance baseline it already runs. A zone reserved for agents would leave that baseline behind.
Full Explanation
Cloud Adoption Framework ready guidance for AI adoption is to extend the landing zone the organization already has, including the governance baseline on that zone. The bank wants a second zone that holds only AI workloads, which splits identity, policy, and logging from the baseline the rest of the bank already runs. Creating that second zone with its own governance stack is the platform the framework says not to stand up. A vendor security page describes the vendor's controls, and it is not the bank's baseline for subscriptions, network, and access. Placing agents in production now and promising a baseline after a new zone is funded ships the workload with neither the existing baseline nor a finished new one. The agents join the landing zone that already has an owner and a review cycle. Exam caveat: extending the zone does not waive a review of the agent itself. The baseline is the floor the workload joins, not a rubber stamp. Operational check: confirm the agent's subscription and policies are the existing landing zone, and confirm no second zone was requested for this release.