A public agency's sponsor wants dozens of agents in production next quarter. No one has ranked the use cases, and no proof of concept has been run. The agency already has an Azure landing zone. What should the architect do first?
Select an answer to reveal the explanation.
Short Explanation
You do not open forty job sites because someone liked the brochure. You rank the work and prove one site before you scale, which is what the Cloud Adoption Framework plan for AI is for. A second landing zone is the detour, not the first step.
Full Explanation
The Cloud Adoption Framework plan for AI adoption turns a wish list into a ranked roadmap and uses a proof of concept to test feasibility before the organization scales. Dozens of agents with no ranking and no proof is the moment to do that plan, not the moment to build. The ready guidance says to extend the landing zone the agency already has, so a second landing zone reserved for agents adds a platform the framework says not to create. Building every request straight into production skips both the ranking and the proof, and it leaves the agency with agents nobody scored. Waiting for a custom model for every use case invents a technical prerequisite the requests have not earned. Many of them will be grounding, orchestration, or a prebuilt copilot. Exam caveat: strategy still names use cases, technology fit, data governance, and responsible AI, but the gap in this story is the plan that follows strategy. Operational check: publish a short ranked list with one proof-of-concept use case, its success criteria, and the existing landing zone it will use.