Cloud service transition and cloud service operation
What this domain tests
Cloud service transition and cloud service operation tests how services move into live use and stay usable. Questions cover change enablement, release and deployment, service validation and testing, configuration management, service desk, incident, problem, service request, event and access management, especially where provider boundaries and automation change the risk.
Core rules
- Separate change, release and deployment. Change enablement authorizes change; release makes it available; deployment places it in the live environment. Cloud APIs and pipelines do not remove the need for control.
- Validate before release. Test service levels, security controls, rollback, monitoring and provider dependencies.
- Operate with observability. Correlate events, logs, metrics and user reports; monitor the consumer experience, not only provider health.
- Define incident and supplier escalation boundaries. A provider incident is not automatically resolved for the consumer; the consumer still manages impact, communication and workarounds.
- Use problem management for recurring or unexplained incidents, and service requests for standard, pre-approved requests.
Worked example
A payment API from a cloud provider starts returning intermittent errors. Monitoring raises an event; the service desk logs an incident because checkout is failing. The team confirms scope, invokes the provider's support process, publishes a workaround, and opens a problem record because errors recur. Reasoning: the event is a signal, the incident is the user-impacting failure, and the problem is the unknown cause. A change is raised only for the fix or workaround deployment, with validation and rollback defined.
Traps
Assuming the provider's status page equals the consumer's service health; treating every alert as an incident; skipping release validation because cloud deployment is automated; failing to document configuration items and dependencies; and not assigning ownership across the provider boundary.