Cloud Service and Deployment Models

The service model decides where the line falls between what the provider manages and what you do. Exam questions almost always test that line rather than the definitions.

Who manages what

LayerOn-premisesIaaSPaaSSaaS
ApplicationsYouYouYouProvider
DataYouYouYouYou
RuntimeYouYouProviderProvider
MiddlewareYouYouProviderProvider
Operating systemYouYouProviderProvider
VirtualisationYouProviderProviderProvider
Servers and storageYouProviderProviderProvider
Networking and facilitiesYouProviderProviderProvider

Examples

ModelAzureAWS
IaaSVirtual Machines, Virtual NetworkEC2, VPC, EBS
PaaSApp Service, Azure SQL DatabaseElastic Beanstalk, RDS
SaaSMicrosoft 365Amazon WorkMail
ServerlessAzure FunctionsLambda
Containers as a serviceAzure Container Apps, AKSECS, EKS, Fargate

Deployment models

ModelWhat it isSuits
PublicShared infrastructure, provider ownedMost workloads, elastic demand
PrivateDedicated to one organisationRegulatory or latency constraints
HybridPublic and private connectedMigration, burst capacity, data residency
CommunityShared by organisations with common requirementsSector consortia, government
MulticloudMore than one public providerAvoiding lock-in, using the best of each

Cloud economics

TermMeaning
CapExBuy the asset up front. On-premises
OpExPay as you consume. Cloud
ElasticityScale with demand, automatically and both ways
ScalabilityAbility to grow. Vertical is bigger, horizontal is more
AgilityTime from deciding to having it running
Total cost of ownershipEverything, including staff, power and space
Consumption-based pricingCharged for what you use rather than what you reserved

Now test yourself

Memorizing a table is a start. Practice questions are what make it stick, and every answer carries the full explanation.