Cloud+ · Domain 5 of 6

Cloud+ Domain 5: DevOps Fundamentals

This is the newest Cloud+ domain. It covers DevOps practices for the cloud: source control, continuous integration and delivery pipelines and automation, and using infrastructure as code and configuration management.

Exam format
10%
Official domains
2
Assessment estimate
~9
Suggested study time estimate
10–15 hrs

About 8 min read Reviewed October 2026

Overview

DevOps Fundamentals is the domain added in CV0-004, reflecting how automation and pipelines have become core cloud skills. It is vendor-neutral and has two areas. Source control, CI/CD and automation covers version control concepts and branching, continuous integration and continuous delivery or deployment pipelines, automated testing and deployment, and general automation and orchestration. Infrastructure as code and configuration management covers defining infrastructure declaratively, idempotency, templates and modules, configuration management tools, and the difference between provisioning infrastructure and configuring it.

At 10%, this is the smallest domain, but it is the likeliest gap for candidates from a traditional systems administration background. The exam rewards understanding how source control, CI/CD and infrastructure as code work in principle, and why they make cloud deployments repeatable, consistent and fast, independent of any specific tool.

How it's tested

Cloud+ questions in this domain describe an automation, pipeline or infrastructure-as-code need and ask for the correct DevOps concept or practice. Cloud+ questions are vendor-neutral and scenario-based, so translate any provider-specific knowledge into the generic concept and read the requirement before choosing.

  • Pipeline stage

    A build, test or release need is described, and you choose the CI/CD concept or stage.

  • Source control

    A versioning or collaboration need is described, and you choose the source-control practice.

  • Infrastructure as code

    A repeatable-deployment need is described, and you choose infrastructure as code or configuration management.

Reasoning it through

A team wants every code change to be automatically built and tested so integration problems are caught early, before release. Manual integration finds problems late. Continuous integration automatically builds and tests each change as it is committed, catching integration issues early, which is the DevOps practice the exam expects for this goal, distinct from continuous delivery, which automates release.

Domains 2

Official domains from the CompTIA outline, in outline order.

5.1 Apply source control, CI/CD pipelines, and automationVersion control, branching, continuous integration and delivery, and automation.
What it means
This covers source control and version control concepts, branching and merging, continuous integration (automatically building and testing changes), continuous delivery and deployment (automating release), pipeline stages, automated testing, and general automation and orchestration of tasks.
What to understand
Source control tracks changes and enables collaboration through branches. Continuous integration builds and tests each change early, while continuous delivery automates releasing to staging and continuous deployment automates releasing to production. Pipelines chain these stages. Automation reduces manual, error-prone work. These speed and stabilize delivery.
How it shows up
A build, test, release or automation need is described, and you must choose the source-control or CI/CD concept.
Common confusion
Confusing continuous integration with continuous delivery; integration builds and tests changes, while delivery automates releasing them.
5.2 Use infrastructure as code and configuration managementDeclarative infrastructure, idempotency, templates, and configuration management.
What it means
This covers infrastructure as code, defining infrastructure declaratively in version-controlled files, idempotency, templates and modules for reuse, and configuration management tools that configure and maintain the state of systems, distinguishing provisioning infrastructure from configuring it.
What to understand
Infrastructure as code declares the desired state so deployments are repeatable and version-controlled, and idempotency means applying the same code yields the same result without duplication. Provisioning creates infrastructure, while configuration management installs and configures software on it. Templates and modules promote reuse. These make environments consistent.
How it shows up
A repeatable-deployment or configuration need is described, and you must choose infrastructure as code or configuration management.
Common confusion
Confusing infrastructure provisioning with configuration management; provisioning creates the infrastructure, while configuration management configures what runs on it.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Source control

    Tracks changes and enables collaboration.

    Remember
    Branches isolate work.
    Tested as
    DevOps questions.
    Trap
    Not versioning infrastructure or code.

  • Branching and merging

    Parallel work streams combined back.

    Remember
    They enable collaboration.
    Tested as
    DevOps questions.
    Trap
    Working without branches.

  • Continuous integration

    Automatically build and test each change.

    Remember
    It catches integration issues early.
    Tested as
    Pipeline questions.
    Trap
    Confusing it with delivery.

  • Continuous delivery vs. deployment

    Automate release to staging versus to production.

    Remember
    Deployment releases automatically to production.
    Tested as
    Pipeline questions.
    Trap
    Confusing the two.

  • Pipeline stages

    Chained build, test and release steps.

    Remember
    They automate the path to release.
    Tested as
    Pipeline questions.
    Trap
    Manual steps between stages.

  • Automation and orchestration

    Reducing manual work and coordinating tasks.

    Remember
    They reduce error and toil.
    Tested as
    Automation questions.
    Trap
    Manual, error-prone processes.

  • Infrastructure as code

    Declarative, version-controlled infrastructure.

    Remember
    Repeatable and consistent.
    Tested as
    IaC questions.
    Trap
    Manual infrastructure changes.

  • Idempotency

    Same code yields the same result.

    Remember
    No duplication on re-apply.
    Tested as
    IaC questions.
    Trap
    Expecting duplicate resources.

  • Templates and modules

    Reusable infrastructure definitions.

    Remember
    They promote consistency and reuse.
    Tested as
    IaC questions.
    Trap
    Rewriting definitions each time.

  • Configuration management

    Configures and maintains system state.

    Remember
    Distinct from provisioning.
    Tested as
    Config questions.
    Trap
    Confusing it with provisioning.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Continuous integration vs. delivery vs. deployment

ConceptMeaningKey differenceCommon trap
Continuous integration Build and test each change Catch issues early Confusing with delivery
Continuous delivery Automate release to staging Ready to release Confusing with deployment
Continuous deployment Automate release to production Fully automated release Confusing with delivery

Infrastructure as code vs. configuration management

ConceptMeaningKey differenceCommon trap
Infrastructure as code Provisions infrastructure declaratively Creates the resources Confusing with config management
Configuration management Configures software on systems Maintains system state Confusing with provisioning

Manual vs. automated delivery

ConceptMeaningKey differenceCommon trap
Manual Human steps between build and release Slow, error-prone Keeping it manual at scale
Automated (pipeline) Chained automated stages Fast, consistent Not automating repetitive steps

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. CD for early testing

    What candidates pick
    Use continuous delivery to automatically build and test every code change for early integration feedback.
    Why it looks right
    Both are pipeline practices.
    Why it's wrong
    Continuous integration builds and tests each change early; continuous delivery automates releasing changes.

    Clue to watch for The goal is to catch integration issues early on each change.

  2. IaC duplicates resources

    What candidates pick
    Expect re-running infrastructure as code to create duplicate resources each time.
    Why it looks right
    Running it again seems to re-create things.
    Why it's wrong
    Infrastructure as code is idempotent, so applying the same code converges to the desired state without duplication.

    Clue to watch for The same configuration is applied more than once.

  3. IaC configures software

    What candidates pick
    Use infrastructure-as-code provisioning to install and configure application software on servers.
    Why it looks right
    Both deploy things.
    Why it's wrong
    Provisioning creates infrastructure; configuration management installs and configures software on it.

    Clue to watch for The task is configuring software on existing infrastructure.

  4. Manual release at scale

    What candidates pick
    Release every change through manual steps as the team scales.
    Why it looks right
    Manual steps feel controllable.
    Why it's wrong
    A CI/CD pipeline automates build, test and release, which is faster and less error-prone at scale.

    Clue to watch for Releases are frequent and repetitive.

  5. No source control for infrastructure

    What candidates pick
    Make infrastructure changes directly without version control.
    Why it looks right
    It is quicker.
    Why it's wrong
    Infrastructure as code in source control makes changes reviewable, repeatable and reversible.

    Clue to watch for Infrastructure changes must be tracked and repeatable.

Answer framework

For any Domain 5 scenario, use these steps to find the vendor-neutral answer Cloud+ expects.

  1. Identify whether the need is source control and pipelines, automation, or infrastructure as code and configuration management.
  2. Use source control with branching to track and collaborate on code and infrastructure definitions.
  3. Apply continuous integration to build and test each change early, and continuous delivery or deployment to automate release.
  4. Use infrastructure as code for repeatable, idempotent, version-controlled provisioning, with templates and modules for reuse.
  5. Use configuration management to install and configure software on provisioned infrastructure, keeping provisioning and configuration distinct. Where several options could fit, choose the generic concept the requirements make defensible rather than a provider-specific product name, choosing the generic concept the requirements make defensible.

Practice question

A development team wants every code change to be automatically built and tested as soon as it is committed, so that integration problems are detected early rather than at release time. Which DevOps practice achieves this?

Want more like this? The Cloud+ practice test has questions for every domain.

Checklist

0 of 10

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

If your background is traditional systems administration, give this new domain focused attention, since it is the most common gap despite being the smallest. Start with source control and pipelines: understand version control and branching, and fix firmly the continuous-integration-versus-continuous-delivery-versus-deployment distinctions, which the exam tests.

Then learn infrastructure as code conceptually: declarative, version-controlled, idempotent provisioning, and the difference between provisioning infrastructure and configuration management of software on it. You do not need to master a specific tool, since Cloud+ is vendor-neutral, but you must understand the concepts and why they make delivery repeatable and fast.

Because it is a small domain, a focused study of the concepts and a set of practice questions suffice. Afterwards, move to Domain 6, Troubleshooting. Because Cloud+ is vendor-neutral and partly hands-on, map each provider product you know to its generic concept and practice the tasks on a real cloud, and review missed practice questions by domain to find weak spots.

FAQ

How much of Cloud+ is Domain 5?

DevOps Fundamentals is 10% of the exam, the smallest domain, and it is new in CV0-004.

Why was DevOps Fundamentals added in CV0-004?

Because automation, CI/CD pipelines and infrastructure as code have become core cloud skills rather than optional, so the exam now tests them directly.

What is the difference between continuous integration and continuous delivery?

Continuous integration automatically builds and tests each change as it is committed. Continuous delivery automates releasing those changes to a staging environment ready for release, and continuous deployment automates releasing to production.

What is infrastructure as code?

Defining infrastructure declaratively in version-controlled files so deployments are repeatable, consistent and reviewable, applied idempotently so re-running converges to the desired state without duplication.

What is idempotency?

The property that applying the same infrastructure code multiple times produces the same result without creating duplicate resources, converging to the declared desired state.

What is the difference between provisioning and configuration management?

Provisioning creates infrastructure such as servers and networks. Configuration management installs and configures the software running on that infrastructure and maintains its state.

How does Domain 5 connect to the rest of the exam?

DevOps practices automate the deployment of Domain 2 and the operations of Domain 3, apply to the architecture of Domain 1, integrate security from Domain 4, and automation failures are diagnosed in Domain 6.

Other Cloud Computing certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 5 knowledge

You have covered source control, CI/CD, automation and infrastructure as code. Test whether you can choose the right DevOps practice under exam conditions.

Take the Cloud+ practice test Check your Cloud+ readiness

Keep going