Build the foundations
Practise Linux, Git, scripting and networking; automate a repeatable environment setup.
Loading your career tools…
Automate delivery without losing reliability.
Practise Linux, Git, scripting and networking; automate a repeatable environment setup.
Create a container build and CI/CD pipeline with tests, security checks and infrastructure as code.
Add health probes, observability and service objectives; exercise deployment rollback and incident response.
Document an incident simulation with a timeline, root cause and follow-up improvements.
Your checklist stays in this page session only. It is a self-check, not a skills assessment.
Pick one credential that matches the technology in your target vacancies. Check prerequisites and prove the skills with a project before booking.
Complements a cloud certification when you provision and manage infrastructure using Terraform.
Before booking: Practise real Terraform workflows, state management and reusable modules.
A hands-on credential for engineers operating Kubernetes clusters across cloud providers.
Before booking: Build Linux, container and Kubernetes administration skills; practise timed troubleshooting.
Fits experienced engineers responsible for release automation and resilient AWS operations. Most useful alongside hands-on delivery ownership.
Before booking: Build experience operating AWS systems and automating deployments before this professional exam.
Useful for engineers responsible for delivering software and managing the flow from source control to production.
Before booking: Have experience both administering and developing in Azure, with strength in at least one.
Review the official source for fees, assessment format, prerequisites and award/renewal requirements. Guidance reviewed 13 September 2026.
Ship an application through a tested pipeline with a staged release, alerting, rollback and an SLO dashboard.
Use these original practice scenarios to structure your answers. They are not leaked exam questions or an employer’s interview script.
A strong answer covers: Assess impact, stop rollout, mitigate or roll back, communicate and preserve evidence.
A strong answer covers: Review the service objective, signal quality and thresholds; reduce noise without hiding real failures.