Cloud Service Management Fundamentals
Domain 1 tests the vocabulary and mental models that make cloud service management coherent: what a service is, who creates value, how cloud services differ, and where responsibility sits.
Core rules
- A service is a means of enabling value co-creation by facilitating outcomes customers want, without the customer managing specific costs and risks.
- NIST SP 800-145 defines cloud computing by five essential characteristics: on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service.
- Service models are SaaS, PaaS, and IaaS; deployment models are private, public, community, and hybrid. Do not treat them as synonyms.
- Utility is fit for purpose; warranty is fit for use, covering availability, capacity, continuity, and security.
- Responsibility is shared. The provider secures the service platform; the customer secures identities, data, configurations, and usage.
Worked example
A team buys SaaS CRM. The provider patches the application and runs its infrastructure. The customer still owns user provisioning, role design, data classification, integration credentials, and export decisions. If a sales user shares a report publicly, that is a customer configuration failure, not a provider breach. The reasoning: control follows the layer that can actually configure the risk.
Traps
Confusing public cloud with SaaS; assuming cloud removes customer duties; describing deployment model when asked for service model; ignoring warranty; and treating measured service as billing only, rather than a feedback loop for capacity and cost.