Selkobase certification index

DevOps Engineer Certification Path: A Reviewed Route from Linux Administration to Cloud-Scale Automation

Linux, infrastructure as code, containers, and a professional cloud credential

DevOps work sits between systems administration and software delivery, and the certification choices reflect that. This reviewed route is for administrators, developers, and support engineers making the move, ordering Linux, automation, containers, and cloud credentials and flagging where one credential formally depends on another.

Key takeaways

  1. 01

    Linux and container credentials carry across employers, while the final step is platform-specific and should follow the cloud your team runs.

  2. 02

    The Azure DevOps expert credential formally requires an Azure associate credential, so take the Azure administrator credential in the cloud step if you may go that way.

  3. 03

    Hands-on command-line exams in the Linux and Kubernetes steps test practical skill more directly than the multiple-choice cloud exams.

  4. 04

    Most credentials in this route expire, so plan upkeep and avoid collecting more than you will use.

Who it is for

System administrators who want to automate, developers who want to own deployment and operations, and support engineers moving toward platform and delivery work.

The goal

Be able to build and operate automated delivery pipelines and infrastructure on Linux and a major cloud platform, using infrastructure as code and containers.

Maybe not for you

People who want a pure cloud architecture track are usually better served by the cloud engineer pathway.

Where to start

Where to start on the DevOps Engineer path depending on your current skills

Start with the Linux foundation if the command line is new to you. If you already administer Linux, begin with infrastructure as code and containers, and if you already automate and run containers, move to the cloud associate for your platform and then the professional credential.

Where are you starting?

Choose your background. We mark where to begin and fold away steps people with your experience usually skip.

The route

The route from Linux administration to cloud DevOps credentials

The route builds the skills DevOps teams ask for in order: Linux, infrastructure as code and Kubernetes, a cloud platform, and a professional DevOps credential. Hands-on command-line exams in the first half are flagged so you know what each step demands.

  1. 1
    Step 1Pick oneNew to the field

    Learn Linux and IT fundamentals

    Get comfortable with the Linux command line, files, users, and the basic concepts of IT infrastructure. Both options are introductions rather than administration credentials.

    These are real alternatives for the same goal. Choose the one that fits.

    2 options

    How to choose

    Linux Essentials focuses on Linux and open source itself and does not expire. The Linux Foundation IT associate is broader, covering cloud, security, and delivery concepts as well as Linux, and needs renewing.

    You can skip this step if

    Suggested skip if you already work comfortably on the Linux command line.

    After this step you can

    • Work comfortably on the Linux command line with files, users, and processes
    • Describe core infrastructure, security, and delivery concepts at a high level
  2. 2
    Step 2Pick oneSome experience

    Administer Linux systems

    Learn to install, configure, secure, and troubleshoot Linux systems. Administration skills underpin container hosts, build servers, and cloud instances.

    These are real alternatives for the same goal. Choose the one that fits.

    3 options

    How to choose

    Red Hat's credential and the Linux Foundation's credential are both hands-on command-line exams. The Red Hat one is specific to Red Hat Enterprise Linux, while the Linux Foundation one is distribution-independent. LPIC-1 is vendor-neutral and knowledge-based rather than hands-on.

    After this step you can

    • Install, configure, and secure Linux servers and services
    • Manage storage, networking, users, and permissions reliably
    • Troubleshoot boot, service, and performance problems from the command line
  3. 3
    Step 3Pick any that fitExperienced

    Automate infrastructure and run containers

    Describe infrastructure as code and operate Kubernetes. This step is where the work starts to look like DevOps rather than systems administration.

    Each option adds something different. Take the ones that match your work.

    4 options

    How to choose

    Terraform Associate covers infrastructure as code in a knowledge-based exam. The Kubernetes and Cloud Native Associate is a conceptual introduction. Certified Kubernetes Administrator suits people who run clusters, and Certified Kubernetes Application Developer suits people who build and deploy applications on them.

    You can skip this step if

    Suggested skip for parts you already do daily, but keep at least one hands-on credential in the route.

    After this step you can

    • Define and manage infrastructure with code instead of manual steps
    • Explain how Kubernetes runs, scales, and heals containerized applications
    • Deploy and troubleshoot workloads on a cluster from the command line
  4. 4
    Step 4Pick one

    Add a cloud platform

    Learn one public cloud well enough to deploy and operate workloads on it. Pick the platform you expect to run pipelines on.

    These are real alternatives for the same goal. Choose the one that fits.

    4 options

    How to choose

    Choose the AWS developer or operations credential, the Azure administrator credential, or the Google Cloud associate engineer credential. The Azure DevOps expert credential in the next step requires an Azure associate credential, and the administrator credential is the one offered here.

    After this step you can

    • Deploy and operate applications on one cloud using its native services
    • Apply the platform's identity, networking, and monitoring basics
  5. 5
    Step 5Pick one

    Prove cloud DevOps skills at professional level

    Demonstrate that you can design and operate delivery pipelines, automation, monitoring, and recovery on one cloud. These professional-level credentials assume real production experience.

    These are real alternatives for the same goal. Choose the one that fits.

    3 options

    How to choose

    Stay on the platform from the previous step. The AWS and Google Cloud professional credentials have no formal prerequisite, while the Azure DevOps expert credential requires an Azure associate credential, so it is reachable only through the Azure option in the previous step.

    After this step you can

    • Design and operate continuous delivery pipelines on a major cloud platform
    • Automate infrastructure, monitoring, and incident response at scale
    • Plan resilient, secure, and observable delivery for production systems

Effort and upkeep

What this path asks of you

Steps

Steps

5

Certifications on the reference route

Certifications on the reference route

5

Study effort

Study effort

290-525h

Exam fees

Exam fees

$640.50

Reference route estimates use the recommended option at each required step and come from the structured certification records. Prices and study time change and vary by region, so confirm with the provider. Last reviewed: Oct 22, 2026

Effort and upkeep

The Linux administration and Kubernetes credentials take the most practice because they are hands-on. The foundation steps are light, and the professional step builds on the cloud associate with scenario-based questions about pipelines, automation, monitoring, and recovery.

Keeping it current

Several credentials here expire, and some renew through a short assessment rather than a full retake. Linux Foundation credentials can renew one another under the foundation's own rules, which can reduce the upkeep burden.

Where it leads

Where the DevOps Engineer path leads in platform and delivery work

The route prepares you for DevOps, platform engineering, and site reliability work and leaves room to specialize in cloud, security, or observability. The role page lists the connected skills, related certifications, and providers if you want to look beyond this route.

You come out ready for DevOps engineer, platform engineer, and site reliability roles, with room to specialize in cloud, security, or observability.

Explore the DevOps Engineer role

More paths

Other paths worth comparing

  • Switch careers

    AI Governance Specialist pathway

    Add AI governance to a risk, privacy, audit, or security career

    From AI literacy through an AI governance credential and an established risk, audit, or security credential to advanced AI audit, risk, or security credentials.

    • 4 steps
    • 10 certifications
    Entry pointsNew to the fieldSome experienceExperienced
    AI Governance SpecialistView the path
  • Switch careers

    Data Engineer pathway

    Switch into data engineering on AWS, Fabric, Databricks, Snowflake, or Google Cloud

    From a data fundamentals credential through a platform data engineering associate and optional Spark skills to a professional-level data engineering credential.

    • 4 steps
    • 10 certifications
    Entry pointsNew to the fieldSome experienceExperienced
    Data EngineerView the path
  • Switch careers

    Penetration Tester pathway

    Become a penetration tester: from offensive security foundations to advanced adversary skills

    From offensive security foundations through a core penetration testing credential to specializations and optional advanced adversary credentials.

    • 4 steps
    • 14 certifications
    Entry pointsNew to the fieldSome experienceExperienced
    Penetration TesterView the path

Reviewed and editorial. Paths suggest an order; they do not replace the provider's own requirements.

Pick the path that matches the role you are aiming for

Open the path closest to your goal, check where your current experience places you, and follow the links to the certifications behind each step. If no path fits yet, search certifications directly and compare level, provider, and assessment style.