Get certified in
DevOps EngineeringDevOps & Cloud Specialization
Prove you can design, operate and troubleshoot modern software delivery systems - across CI/CD, infrastructure, containers, observability, reliability and security, against a published competency blueprint.
Built for DevOps engineer, Cloud engineer, Platform engineer and similar roles.
Join 100,000+ One Roadmap-certified candidates
The assessment
40 min
timed assessment
20
questions, scenarios & cases
3
assessment sections
75%
passing standard
You will be assessed on
A portable skill certification asks
“Does this person understand this system?”
What a Pod is. What a volume does. Which port HTTPS uses. That is what Linux, Containers & Orchestration and Cloud Fundamentals are for.
This specialization asks
“Can this person ship and operate software reliably?”
Why the artifact you tested must be the artifact you deploy. What-/+ destroy and then createmeans on a production database. Whether to roll back before you know the cause.
12 competencies, scored separately
Not one number called “DevOps”. Your result reports a level for each of these, so you can pass overall and still see exactly where the gap is.
CI/CD & Release Engineering
Reasons about pipeline design, artifact lifecycle, test gates, environment promotion and release safety.
Infrastructure as Code
Reasons about declarative infrastructure, state, drift, plan review, idempotency and safe or destructive change.
Incident Response
Investigates production failures methodically, correlates evidence and avoids acting on unverified assumptions.
Reliability Engineering
Reasons about failure boundaries, redundancy, graceful degradation and the cost of reliability work.
Deployment Strategy & Change Risk
Chooses rollout and rollback approaches according to blast radius, reversibility and data compatibility.
Observability
Distinguishes logs, metrics and traces, reads percentiles and designs alerts that correspond to user impact.
Security & Secrets
Handles credentials, least privilege, exposure and artifact hygiene in delivery systems.
Container Delivery & Runtime
Applies image immutability, runtime configuration, probes, resource limits and container failure reasoning.
Cloud & Networking Operations
Reasons about public and private boundaries, load balancing, DNS, health checks and stateless deployment.
Capacity & Scaling
Reasons about horizontal and vertical scaling, autoscaling signals, bottlenecks and cost trade-offs.
Operational Judgment
Chooses proportionate action under production pressure, balancing urgency, risk and accountability.
Incident Communication
Communicates impact, uncertainty, action and next steps clearly to non-engineering readers.
Assessment standard
Every attempt draws a fresh paper - but always the same number of questions from each competency area, so nobody gets an easier test.
Core DevOps Engineering
CI/CD, Infrastructure as Code, containers, cloud networking, observability and security - understand how the delivery system actually works.
- CI/CD & Release Engineering2
- Infrastructure as Code2
- Containers & Runtime1
- Cloud & Networking1
- Observability1
- Security & Secrets1
You must score at least 65% here, whatever your overall total.
Applied Delivery & Reliability Judgment
Production situations where several answers look technically possible, but only one manages the system risk properly.
- Pipeline Failure & Recovery2
- Reliability / Incident Response2
- Deployment Strategy & Change Risk1
- Scaling / Capacity / Cost1
- Security / Operational Judgment1
DevOps Operational Case Response
Five short written cases: diagnose the issue, identify the evidence you need, choose what you would do, and communicate the operational decision clearly.
- Deployment Failure1
- Infrastructure Change1
- Incident Diagnosis1
- Reliability Trade-off1
- Incident Communication1
You must score at least 60% here, whatever your overall total.
Assessment version
DEVOPS-ENGINEERING-v2
Question bank
87 randomized items
Passing standard
75% weighted
Result bands
Distinction / Strong Performance / Certified
Result bands describe performance on this assessment. They are not a measure of employability or hiring outcomes.
Recommended preparation
Recommended, not required. Nothing blocks your attempt if you do not hold these - equivalent experience from work counts just as well.
Then the specialization topics themselves
- 1CI/CD & release engineering
- 2Infrastructure as Code
- 3Observability & reliability
- 4Deployment strategies
- 5Incident response
- 6Security in delivery systems
Learning outcomes
These are what the public verification page reports - and each one is claimed only where your own attempt evidenced it.
CI/CD & Release Engineering
Demonstrated ability to reason about build-once artifact promotion, test gating, pipeline dependencies and release safety.
Infrastructure as Code
Demonstrated ability to reason about desired state, state files, drift, plan review and destructive infrastructure change.
Incident Investigation
Demonstrated ability to narrow a production failure from evidence rather than assumption, and to sequence mitigation before diagnosis.
Reliability Engineering
Demonstrated ability to reason about failure boundaries, degradation, dependency isolation and the real cost of reliability work.
Deployment Strategy & Change Risk
Demonstrated ability to select rollout strategies from blast radius, reversibility and schema or data compatibility.
Observability & Alert Design
Demonstrated ability to choose the right signal, read percentiles and design alerts tied to user-visible impact.
Security & Secrets in Delivery
Demonstrated ability to handle credentials, least privilege, exposure and artifact hygiene in a delivery pipeline.
Container Delivery & Runtime
Demonstrated ability to reason about immutable images, runtime configuration, probes, resource limits and container failure.
Cloud & Networking Operations
Demonstrated ability to reason about public and private boundaries, load balancing, DNS behaviour and health checking.
Capacity & Scaling
Demonstrated ability to identify real bottlenecks, choose a scaling axis and weigh capacity against cost.
Operational Judgment
Demonstrated ability to choose proportionate action under production pressure with appropriate containment and accountability.
Incident Communication
Demonstrated ability to communicate impact, uncertainty, current action and next steps to a non-engineering audience.
How the written cases are graded
A model reading your answer and returning “8.7 out of 10” is not a grade - it is a guess with a decimal point. So we split the job in two: the AI only observes, and the code scores.
The evaluator reports which operational decisions it can evidence in your own words - restored service before chasing the cause, recognised the plan was destructive, checked a backup first, separated what is confirmed from what is assumed. It has no score field to write into. Points come from a fixed rubric in code, so naming a tool with no reasoning behind it earns nothing.
Your written case answer
100-180 words, in your own words, in the time you have.
AI evaluator
Reports only which expected decisions are evidenced, and which red flags appear.
Deterministic rubric
Code turns those observations into points, using the bank's own signal list.
Weighted result + competency profile
Part A 40%, Part B 35%, Part C 25% decides the 75% pass mark; the same answers roll up into a level for each competency.
Weekly Ranking
Frequently asked questions
Free, 40 minutes, and a verifiable credential at the end.
This is an independent OneRoadmap competency credential. It is not issued, sponsored, approved or endorsed by any cloud provider, CI/CD vendor or tooling company, and it is not a substitute for a vendor certification. Tools are named only as recognisable examples; the assessment measures transferable engineering judgment.