iwantcoding.com
🔥 Daily 👥 Rooms 🏆 Top Log in Sign up

Quiz

CI/CD track quiz: 10 questions on pipelines, deploys, branching, security.

CI/CD — track quiz

EXAMPLE
# 10 questions. Pass: >= 7.

# ===== Q1 =====
# What does CI stand for?
# A) Continuous Integration
# B) Continuous Inspection
# C) Code Integrity
# D) Compile + Install

# ===== Q2 =====
# What does CD (Continuous Delivery) require?
# A) Every commit deployed automatically
# B) Every commit produces a deployable artifact; deploy is one-click
# C) No manual gates ever
# D) Tags only

# ===== Q3 =====
# What is a 'fail fast' pipeline?
# A) The pipeline times out after 5 minutes
# B) Cheap stages (lint, typecheck) run first; failure aborts before expensive stages
# C) Pipeline runs every minute
# D) Auto-rollback on prod failure

# ===== Q4 =====
# What is a 'flaky test'?
# A) A test that sometimes passes, sometimes fails on the same code
# B) A test that takes too long
# C) A test marked with @flaky annotation
# D) A test for legacy code

# ===== Q5 =====
# What is a 'feature flag'?
# A) A git branch
# B) Runtime toggle controlling feature visibility, decoupling deploy from release
# C) A required PR label
# D) A docker label

# ===== Q6 =====
# What is the 'merge queue'?
# A) The list of open PRs sorted by date
# B) Sequentially merges PRs, retesting against trunk to avoid race conflicts
# C) A type of branch protection rule
# D) A linter

# ===== Q7 =====
# A 'canary' deploy means:
# A) Deploy to all users at once
# B) Deploy to a small subset of traffic to validate before full rollout
# C) Deploy only after midnight
# D) Deploy with no monitoring

# ===== Q8 =====
# 'Trunk-based development' means:
# A) Long-lived feature branches
# B) Short-lived branches; frequent merges to main
# C) Releasing only from a release branch
# D) GitFlow with develop branch

# ===== Q9 =====
# What is 'shift left' in CI/CD?
# A) Move tests earlier in the pipeline
# B) Move quality + security checks earlier (lint, SAST, dependency scan in PR)
# C) Push code to the left repo
# D) Use the left-arrow key

# ===== Q10 =====
# 'GitOps' is:
# A) Storing infrastructure config in git; tools reconcile clusters to that state
# B) Using git for code only
# C) An Atlassian product
# D) A type of CI tool

# ===== Answers =====
# 1. A — Continuous Integration
# 2. B — CD = deployable artifact + one-click deploy
# 3. B — cheap stages first to abort fast
# 4. A — non-deterministic test results on same code
# 5. B — runtime toggle decoupling deploy + release
# 6. B — merge queue serialises merges, retesting
# 7. B — small subset of traffic first
# 8. B — short branches, frequent merges
# 9. B — quality + security earlier in dev cycle
# 10. A — git as source of truth for infra; tools reconcile

# ===== Patterns to internalise =====
# - Cheap stages first (lint, typecheck before tests before build)
# - Feature flags decouple deploy + release
# - Trunk-based dev + merge queue for fast teams
# - Canary + auto-rollback for risky deploys
# - GitOps (Argo CD / Flux) for cluster state

Why it matters

Quiz takeaway: CI = integration, CD = delivery (or deployment), trunk-based + feature flags + merge queue + canary deploys + GitOps are the modern stack. Shift quality + security left so you catch issues in PR, not in prod.

Tip: Tweak the snippet with Try it Yourself », then sit the quiz at the bottom of the page.

Example

Example
# 3 questions per lesson.
Try it Yourself »

Discussion

Loading…