Match IaaS, PaaS, and SaaS tickets; leave on-prem Type 1, thin-provision, and container distractors unused.
Match each cloud service model to the ticket that fits. Leave on-prem hypervisor, datastore, and container tickets unused.
Pick the layer the customer stops managing. IaaS = guest OS you own. PaaS = app on a managed runtime. SaaS = use the app. Type 1 hosts, thin disks, and containers are different questions.
Tickets still in the queue
Finance needs a Windows Server they can Group Policy and RDP into after an Azure image deploy — Guest OS you own = IaaS. Patching Windows is still your ticket.
Dev team wants to git-push a web app and never SSH into nodes or manage the Python runtime — Platform owns OS/runtime; you own the app and data.
HR wants company email and docs with no Exchange servers — just licenses and MFA in a portal — You use the app; vendor runs it. Identity and sharing are still yours.
Rack a bare-metal ESXi host in the closet for forty local VDI desktops — On-prem Type 1 / VDI — not a cloud service model.
Thin-provision three guests until the datastore fills and VMs pause — Host storage accounting on a hypervisor — not IaaS/PaaS/SaaS.
Run ten microservices that share one Linux kernel on a laptop Docker engine — Containers share a host kernel; that is isolation, not a cloud service model.