Study CompTIA 220-1201 Cloud Models, Thin Clients, and VDI: key concepts, common traps, and exam decision cues.
Cloud questions on Core 1 are not architect-level questions. They are support questions. CompTIA wants you to know what the service model means for the user and where a thin client, remote desktop path, or hosted app fits.
SaaS: Software as a Service, where the user consumes the finished application.
IaaS: Infrastructure as a Service, where the customer manages more of the system stack.
PaaS: Platform as a Service, where the provider manages the infrastructure and platform while the customer focuses more on the application layer.
Thin client: A lightweight endpoint that depends heavily on central compute or hosted desktop resources.
VDI: Virtual desktop infrastructure, where the user connects to a centrally hosted desktop session instead of running the full desktop locally.
The exam usually wants you to:
IaaS, PaaS, and SaaSVDI| Model | Support-level meaning |
|---|---|
| SaaS | the provider delivers the finished app |
| PaaS | the provider delivers the platform and runtime layer |
| IaaS | the provider delivers virtual infrastructure while the customer manages more above it |
| thin client | a lightweight endpoint that relies heavily on central resources |
| VDI | a centrally hosted desktop delivered remotely |
CompTIA often turns this into a support-boundary question. The simplest safe model is:
| If the user or local IT team mostly manages… | Strongest fit |
|---|---|
| almost none of the application stack | SaaS |
| the application code while the provider handles more of the platform | PaaS |
| the operating system and more of the server stack | IaaS |
| very little on the endpoint because the desktop runs centrally | thin client with VDI |
The exam does not expect deep cloud-architecture ownership maps. It does expect you to avoid calling every hosted service SaaS.
| If the user is really getting… | Best fit |
|---|---|
| the finished application in the browser | SaaS |
| a full remote desktop experience | VDI or another hosted desktop model |
| a lightweight device that mainly connects to central resources | thin client endpoint |
| a virtual server the organization manages above the infrastructure layer | IaaS |
flowchart LR
A["User device"] --> B["Local app runs here"]
A --> C["Browser opens provider app"]
A --> D["Remote display session"]
C --> E["SaaS application"]
D --> F["VDI desktop in data center or cloud"]
What to notice:
SaaS app gives the user the finished application, not a full desktopVDI gives the user a desktop session that runs centrallythin client describes the endpoint choice, while VDI describes the hosted desktop model it often connects to| Symptom | First interpretation |
|---|---|
| user can open one hosted app in the browser but not the full work desktop | likely SaaS access versus VDI access difference |
| device is intentionally low-power and depends on central sessions | thin-client design, not automatically a broken normal PC |
| admin needs to patch the guest operating system inside a virtual server | more like IaaS ownership than SaaS |
| user only needs CRM or webmail from anywhere | a finished SaaS app may fit better than a full hosted desktop |
A call-center team uses lightweight desk terminals that open centrally hosted desktops. The best description is not “everyone is using SaaS.” The endpoint is a thin client, and the user experience is closer to VDI because the desktop session is running centrally rather than locally on the device.
Another common Core 1 trick is the reverse case: a company uses Microsoft 365 or Google Workspace in the browser on ordinary laptops. That is usually better classified as SaaS, not VDI, because the user is consuming finished applications rather than a centrally hosted desktop.
PaaS like a user-facing desktop or endpoint model instead of a provider-managed platform layerA company replaces full desktops with lightweight endpoints that mainly connect to centrally hosted Windows desktops. Which answer is the best fit?
Correct answer: A. The endpoints are thin clients, and the centrally delivered desktop experience aligns to VDI rather than a finished SaaS app or a server-admin IaaS model.
VDI to centralized desktops rather than ordinary file sync