Study Hub / CompTIA Cloud+ (CV0-004) / Domain 5.0
CompTIA Cloud+ (CV0-004) Domain 5.0: DevOps Fundamentals — Explained
Domain 5.0 is new to Cloud+ and pure concept: how DevOps practices — version control, CI/CD, infrastructure as code — change the way cloud systems are built and run. No pipeline to configure here; just the ideas the exam asks about.
Version control: the foundation
- What version control does — tracks every change to code and configuration: who changed what, when, and why — with the ability to revert. Git is the standard; everything else builds on it.
- Repositories and branching — the repo holds the project; branches isolate work (feature branches), main stays deployable, merging combines work, pull requests gate merges with review.
- Why it matters for cloud — infrastructure as code lives in version control: every environment change is a reviewed commit, not a console click. "Who changed production?" has an answer.
- Collaboration basics — push/pull, merge conflicts (two people edited the same lines — resolve deliberately), and commit hygiene (small, described commits beat mystery blobs).
CI/CD: the delivery pipeline
- Continuous integration (CI) — developers merge frequently; every merge triggers automated build and test. Broken code is caught in minutes, not at release.
- Continuous delivery/deployment (CD) — delivery: code is always in a releasable state (a human approves the release); deployment: releases go out automatically. Know which "CD" a question means.
- Pipeline stages — source → build → test (unit, integration, security scans) → stage → production, with gates between. Artifacts flow one direction; failures stop the line.
- Cloud relevance — pipelines deploy to cloud targets: container images to registries, IaC templates to environments. The pipeline is the deployment mechanism.
Infrastructure as code in the DevOps loop
- IaC recap — environments defined as versioned templates (Terraform, CloudFormation): reproducible, reviewable, testable infrastructure.
- Declarative vs. imperative — declarative ("here's the desired state" — Terraform) vs. imperative ("run these steps" — scripts). Declarative dominates cloud IaC because the tool figures out the steps and handles drift.
- Testing infrastructure — lint templates, validate plans before applying, test in ephemeral environments. "It worked on my cloud" is the new "it worked on my machine."
- GitOps — the repo is the source of truth; automation converges the environment to match it. Change the repo, the cloud follows — auditable by construction.
- Culture note — DevOps is collaboration between dev and ops (shared responsibility, blameless postmortems), not a job title. The domain covers the practices, not the org chart.
The must-memorize table: DevOps vocabulary
The terms the domain is built from.
| Term | Meaning | One-liner |
|---|---|---|
| Version control | Track every change | Git: who changed what, when; revert anything |
| CI | Continuous integration | Merge often; automated build + test on every merge |
| Continuous delivery | Always releasable | Human approves the actual release |
| Continuous deployment | Automatic release | Every passing build goes to production |
| IaC | Infrastructure as code | Versioned templates define environments |
| GitOps | Repo as source of truth | Automation converges the cloud to the repo |
Try it: 4 sample questions
Sample questions to check your understanding of this domain. Answers and full reasoning are tucked under each one.
1. A team merges code daily and every merge triggers automated builds and tests, catching bugs within minutes. Which practice is this?
- A. A. Continuous deployment
- B. B. Continuous integration — frequent merges with automated build/test
- C. C. GitOps
- D. D. Infrastructure as code
Show answer & reasoning
B. CI's definition: integrate frequently, verify automatically. The build+test on every merge is the CI signature. Deployment (A) would release automatically — a step further. IaC (D) is about infrastructure definition, not the merge workflow.
2. A company wants every production release to require explicit human approval, while keeping code always ready to release. Which "CD" is this?
- A. A. Continuous deployment
- B. B. Continuous delivery — releasable at any time, released by human decision
- C. C. Continuous integration
- D. D. Continuous testing
Show answer & reasoning
B. Delivery = the pipeline keeps code in a deployable state; a human decides when. Deployment (A) removes the human — every green build ships. The approval gate is the tell: human in the loop → delivery.
3. Why does infrastructure as code belong in version control rather than being applied from engineers' laptops?
- A. A. Version control is faster
- B. B. Reviewed, revertible, auditable changes — every environment modification is a tracked commit, not an untracked console click
- C. C. Laptops can't run Terraform
- D. D. It reduces cloud bills directly
Show answer & reasoning
B. Version control gives IaC its superpowers: peer review before apply, full history ("who changed production?"), and one-command revert. Laptop-applied IaC is snowflake infrastructure with extra steps. The repo as source of truth is the entire GitOps idea.
4. Two developers edit the same lines of a Terraform file and both try to merge. What happens, and how is it resolved?
- A. A. The system picks one automatically and deletes the other
- B. B. A merge conflict — the merger manually reviews both changes and resolves them deliberately
- C. C. Both versions are kept side by side forever
- D. D. The file is locked permanently
Show answer & reasoning
B. Same lines + two authors = merge conflict: automation stops and a human reconciles. This is by design — silent auto-resolution would corrupt infrastructure definitions. Small, frequent merges keep conflicts rare and trivial; giant rare merges make them painful.
This was one domain. The simulator drills all 6.
This free preview covered DevOps Fundamentals (Domain 5.0, 10%). Not covered here: Operations (Domain 3.0, 17%); Troubleshooting (Domain 6.0, 12%). Cloud operations and scenario troubleshooting stay in the paid guide and practice bank. The ByteBar Practice Exam Simulator drills every domain with 1,000 exam-style questions — $9.99 one-time unlocks all 28 exams. Prefer to read? The full Cloud+ Study Guide is in the ByteBar shop on Etsy.
Practice Exam Simulator — $9.99 one-time, all 28 exams Full Study Guides on Etsy