Council asks for a simple diagram: which cloud service type is closest to renting infrastructure while the city still manages the operating system?
Select an answer to reveal the explanation.
Short Explanation
Renting the virtual hardware and still babysitting the OS is the IaaS picture for council. SaaS is more like subscribing to a finished app. Keep the diagram at that rent-versus-subscribe story.
Full Explanation
IaaS is the service type closest to renting infrastructure while the city still manages the operating system—compute, storage, and networking as a service with customer responsibility from the guest OS upward. That rent-versus-subscribe diagram is standard AZ-900 framing for council briefings and keeps the OS duty line visible. Candidates should be able to point at IaaS when the story is “we still babysit the OS.” SaaS is a complete application delivered as a service, not rented infrastructure with OS management by the customer. A managed SaaS identity portal with no virtual machines illustrates SaaS or identity consumption, not IaaS rental of infrastructure. Serverless-only billing with no infrastructure abstraction choices misses the IaaS control model council asked to diagram and skips the OS-management characteristic. Exam caveat: “renting infrastructure” does not mean buying the provider’s physical servers—IaaS is still a service, not a hardware purchase order shipped to city hall. Operational check: when briefing council, label one slide IaaS (customer manages OS) versus SaaS (finished app) and verify stakeholders can distinguish the OS duty line without confusing it with facility ownership.