MugUp logoMugUp
HomeBrowseAboutBlog
LoginSign Up
MugUp

Plan your day, study, read, write and track your habits in one app.

Follow MugUp

Product

  • Features
  • Compare
  • Free Tools
  • Deck Library
  • MugUp for Discord

Community

  • Blog
  • Changelog
  • Feature Requests
  • Deck Requests

Company

  • Home
  • About
  • Contact

© 2026 MugUp. All rights reserved.

Terms of ServicePrivacy PolicyCookie Policy
  1. Browse decks
  2. DevOps: CI/CD, Infrastructure as Code and GitOps
Public deck

DevOps: CI/CD, Infrastructure as Code and GitOps

How teams build, test, release and run software with automation: CI pipelines, deployment strategies, Terraform and Ansible, artifact versioning, pipeline secrets and GitOps.

Engineering
AShared by Alex Chen
0PlaySign in to clone

You’re reading a free preview. Sign up to see every topic and question — and to play this deck as games.

See the whole deck

Suggested order

Arrows point from what to learn first. Topics side by side can be studied in any order — and cloning the deck brings this order with it.

Topics

Open a topic to read through its content, then play just that topic.

DevOps Practices and the DORA Metrics
What DevOps means in practice, the four DORA metrics used to measure software delivery, and habits such as small batches, trunk-based development and shifting left.
MCQ: 10
Fill-in: 8
Flashcards: 12
Pair match: 10
40 total questions
Continuous Integration: Builds, Tests and Pipelines
How CI pipelines build and test every change: stages, runners, caching, artifacts, flaky tests and reproducible builds, using GitHub Actions and GitLab CI terms.
MCQ: 10
Fill-in: 8
Flashcards: 12
Pair match: 10
40 total questions
Deployment Strategies and Release Safety
Ways to release new versions safely: rolling, blue-green and canary deployments, feature flags, dark launches, rollback versus roll forward, and database changes during a deploy.
MCQ: 10
Fill-in: 8
Flashcards: 12
Pair match: 10
Locked · 40 questions inside
Infrastructure as Code with Terraform
How Terraform describes infrastructure in code: providers, resources, state and remote backends, locking, plan and apply, modules, variables, outputs, drift and import.
MCQ: 10
Fill-in: 8
Flashcards: 12
Pair match: 10
Locked · 40 questions inside
Configuration Management with Ansible
How Ansible configures servers: inventories, playbooks, modules, handlers and roles, why tasks should be idempotent, and how push-based Ansible differs from Puppet and Chef.
MCQ: 10
Fill-in: 8
Flashcards: 12
Pair match: 10
Locked · 40 questions inside
Artifacts, Versioning and Supply Chain
How build outputs are versioned, stored and trusted: semantic versioning, artifact registries, immutable artifacts, image tags versus digests, SBOMs and signing.
MCQ: 10
Fill-in: 8
Flashcards: 12
Pair match: 10
Locked · 40 questions inside
Secrets Management in Pipelines
How pipelines get the credentials they need without leaking them: secrets managers, short-lived credentials, OIDC federation from CI to the cloud, scanning and rotation.
MCQ: 10
Fill-in: 8
Flashcards: 12
Pair match: 10
Locked · 40 questions inside
GitOps and Progressive Delivery
How GitOps keeps running systems matching the state declared in Git, using pull-based agents such as Argo CD and Flux, and how progressive delivery automates canary decisions.
MCQ: 10
Fill-in: 8
Flashcards: 12
Pair match: 10
Locked · 40 questions inside
6 more topics in this deck

Create a free account to open every topic — and play the whole deck without copying it.

Sign up freeLog in