10X DEVOPS 10X Practice
DevOps 10X Knowledge Hub

Learn the concepts.
Practice the work.

A guided starting point for DevOps, Azure, Terraform, and Git—with hands-on exercises, reliable references, and interview questions that test understanding, not memorization.

Use this as a roadmap, not a checklist. Build small projects and explain your decisions.

A sensible order

Beginner learning path

Learn the foundations first, then combine the tools into one end-to-end delivery workflow.

Cloud safety: use a sandbox or free-tier account, set budgets and alerts, and remove lab resources when finished. Cloud services and pricing change—check current provider documentation before deploying.

01 · Foundations

DevOps essentials

DevOps is a way of improving how teams build, deliver, and operate software. It combines culture, automation, feedback, and shared responsibility—not just a collection of tools.

Open the interactive playground

Delivery loop

Plan → code → build → test → release → deploy → operate → observe. Short feedback loops help teams detect problems earlier.

CI and CD

Continuous integration frequently merges and verifies changes. Continuous delivery keeps releases deployable; continuous deployment automatically releases qualifying changes.

Observability

Metrics show numeric trends, logs record events, and traces connect work across services. Use them together to investigate system behavior.

DevSecOps

Build security into design and delivery: least privilege, secret management, dependency and image scanning, policy checks, and actionable remediation.

Core skills to practice

  • • Linux files, permissions, processes
  • • DNS, HTTP, ports, TLS, routing
  • • Bash basics and safe scripting
  • • Containers and image basics
  • • CI pipeline stages and artifacts
  • • Logs, metrics, alerts, incidents

Starter project

Take a small web app, store its code in Git, build and test it in CI, package it as a container, deploy it to a sandbox, and add a health check plus a basic dashboard. Document the rollback and cleanup steps.

02 · Cloud platform

Azure learning map

Learn the shared cloud concepts before memorizing service names. Understand how identity, network boundaries, resource organization, reliability, and cost fit together.

Microsoft Learn: Azure training
01Identity and access

Microsoft Entra ID provides identity capabilities. Azure RBAC authorizes actions on Azure resources at scopes such as management group, subscription, resource group, or resource. Prefer managed identities for supported workloads and grant least privilege.

02Resource organization and governance

Management groups organize subscriptions; resource groups collect related resources; tags help classify ownership and cost. Azure Policy evaluates or enforces organizational rules. Understand scope and inheritance.

03Networking

Study virtual networks, address spaces, subnets, NSGs, routing, private endpoints, DNS, load balancing, and connectivity. Be able to trace a request from client to service and identify where traffic is allowed or denied.

04Compute, storage, and data

Compare virtual machines, app hosting, containers, and managed Kubernetes based on control, operations, scale, and fit. Learn storage redundancy options and how access, encryption, backup, and recovery requirements influence design.

05Reliability, monitoring, and cost

Learn regions and availability zones, backup and disaster recovery objectives, Azure Monitor and alerts, resource health, budgets, cost analysis, and right-sizing. Design for failure and define how recovery will be tested.

Azure practice exercise

Draw a simple web application architecture with a network boundary, application tier, data tier, identity approach, monitoring, backup, and a cost owner. Explain which services are public, how administrators connect, and what happens if one zone fails.

03 · Infrastructure as code

Terraform essentials

Terraform describes infrastructure declaratively. The workflow compares configuration with current state and provider APIs to propose changes before applying them.

Official Terraform tutorials

Configuration building blocks

terraform settings and providers configure behavior; resources manage infrastructure; data sources read existing information; variables parameterize; outputs expose useful results.

Core workflow

Format → initialize → validate → plan → review → apply. A plan is a proposed change set, not a guarantee that the remote operation will succeed unchanged.

State and collaboration

State maps configuration to real objects. Use an appropriate remote backend, locking where supported, access controls, backups, and careful handling of sensitive values. Never commit secrets or state containing secrets.

Modules and lifecycle

Modules package reusable configuration with clear inputs and outputs. Understand dependencies, replacement behavior, lifecycle settings, version constraints, and the impact of refactoring addresses.

Habits that prevent incidents

  • • Review the plan and confirm the target workspace/account.
  • • Pin and test provider/module versions intentionally.
  • • Keep credentials outside source control; use workload identity when available.
  • • Protect and back up remote state; limit who can read it.
  • • Make changes through reviewed code and avoid concurrent applies.

Terraform practice exercise

Create a small, low-cost sandbox resource with variables and outputs. Run formatting, validation, and a plan. Review every proposed action, apply only in a safe account, then destroy and verify cleanup. Next, extract repeated configuration into a module.

04 · Version control

Git that you can explain

Git records snapshots of a project. Understanding the working tree, staging area, commits, and branches makes collaboration and recovery much easier.

Pro Git book

Three places to know

Working tree: current files. Index/staging area: selected changes for the next commit. Repository: committed history. git add stages; git commit records a snapshot.

Branches and merging

A branch is a movable reference to a commit. Merge combines histories; a fast-forward moves the branch pointer when possible. Conflicts require you to choose and validate the intended result.

Undo safely

git revert creates a new commit that reverses changes. git reset moves a branch pointer and can rewrite local history. Avoid destructive commands on shared work unless you understand the impact.

Remote collaboration

Fetch downloads remote history; pull fetches and integrates; push publishes commits. Use focused branches, small commits, reviewable pull requests, and clear messages.

A small daily workflow

$ git status

Inspect changed files

$ git switch -c feature/my-change

Create a focused branch

$ git add path/to/file

Stage intentional changes

$ git diff --cached

Review exactly what is staged

$ git commit -m "Explain the change"

Record a useful snapshot

Interview preparation

Practice explaining your reasoning

Use a clear pattern: clarify requirements → describe the design → explain trade-offs → cover security and failure modes → say how you would verify it. For experience questions, describe context, your actions, and measurable results without sharing confidential details.

What is the difference between continuous delivery and continuous deployment?

In continuous delivery, changes are kept ready for release, but a person or business process may approve production deployment. In continuous deployment, qualifying changes are released automatically after required checks pass.

How would you investigate a failed deployment?

Establish impact and recent changes; inspect pipeline stage, deployment events, application health, logs, metrics, and dependencies. Stabilize or roll back using the team’s procedure, communicate status, then identify root cause and preventive checks.

How do Terraform configuration and state differ?

Configuration expresses desired infrastructure. State records Terraform’s mapping between configured resource addresses and real objects, plus relevant attributes. State is operationally sensitive and should be protected and shared through an appropriate backend.

How do you resolve a Git merge conflict?

Inspect conflicted files and the surrounding intent, edit to the desired combined result, remove conflict markers, run relevant tests, stage the resolution, and complete the merge or rebase. Ask the change owners when intent is unclear.

How would you secure an Azure workload?

Start with requirements and threat boundaries. Apply least-privilege identity, managed identities where supported, network restrictions, secret protection, encryption, policy and logging controls, patching, backups, and tested recovery. Verify controls rather than assuming defaults.

How do you reduce cloud costs without hurting reliability?

Establish ownership and usage baselines, find idle or oversized resources, validate utilization and service objectives, test right-sizing, automate schedules where suitable, and monitor cost and reliability after each change. Treat savings estimates as hypotheses to verify.

What is the difference between a container and a virtual machine?

A VM runs a guest operating system on virtualized hardware. Containers isolate processes while sharing the host kernel. Containers are often lighter to start, but the right choice depends on isolation, compatibility, operations, and workload requirements.

Tell me about a production incident you handled.

Use a concise STAR-style story: situation and impact, your responsibility, actions taken to restore service, how you communicated, and the follow-up that reduced recurrence. Be clear about what you personally did and what the team did.

Build an interview-ready portfolio

Publish a small, sanitized project with a README, architecture diagram, Terraform plan examples, CI workflow, security considerations, monitoring approach, cost notes, and teardown steps. Explain trade-offs and lessons learned; never publish credentials, customer data, or proprietary configuration.

Trustworthy references

Go deeper with primary sources

Start with official documentation for product details; use community roadmaps as a guide, then practice in a safe lab.

External resources are maintained by their respective publishers. Service names, interfaces, certification objectives, and pricing can change; confirm details in current official documentation.

Learn by doing, then share what you discover.

Continue with safe, simulated command practice or head back to the DevOps 10X community.