DevOps Introduction to DevOps Flashcards

24 sample cards from the Introduction to DevOps deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

1. What is the difference between Continuous Integration and Continuous Delivery?

   Continuous Integration (CI) automatically builds and tests merged code frequently; Continuous Delivery (CD) extends CI by ensuring code is always in a deployable state, ready for release.

2. What is the difference between Continuous Delivery and Continuous Deployment?

   Continuous Delivery requires a manual approval step before production release; Continuous Deployment automatically releases every passing change to production with no manual gate.

3. What is a CI/CD pipeline?

   An automated workflow that builds, tests, and deploys code changes through stages, enabling fast and reliable delivery from commit to production.

4. What is Infrastructure as Code (IaC)?

   Managing and provisioning infrastructure through machine-readable definition files (code) rather than manual configuration, enabling versioning, repeatability, and automation.

5. How does automation support continuous improvement?

   By eliminating repetitive manual work, reducing human error, accelerating feedback, and freeing teams to focus on higher-value improvements and experimentation.

6. What is a blameless postmortem?

   A retrospective after an incident that focuses on understanding systemic causes and learning, without assigning personal blame to individuals involved.

7. Why are postmortems made 'blameless' in DevOps culture?

   To encourage honesty and full disclosure; when people fear punishment they hide information, but a blameless approach surfaces root causes so systems can be improved.

8. What key assumption underlies a blameless postmortem?

   That people act with good intentions given the information they had; failures stem from systemic and process weaknesses, not individual incompetence or malice.

9. What is a root cause analysis in the context of a postmortem?

   A structured investigation to identify the underlying systemic factors that led to an incident, rather than just the immediate trigger or symptoms.

10. Name a common technique used to find root causes in postmortems.

    The '5 Whys'—repeatedly asking 'why' (about five times) to drill from a symptom down to its underlying systemic cause.

11. What are typical sections of a postmortem document?

    Summary, impact, timeline of events, root cause(s), resolution/recovery, lessons learned, and action items to prevent recurrence.

12. What is the desired outcome of a blameless postmortem?

    Actionable improvements (process, tooling, monitoring) that reduce the likelihood and impact of similar incidents, plus organizational learning.

13. What is a 'culture of learning' in DevOps?

    An environment where failures are treated as learning opportunities, experimentation is encouraged, and knowledge is shared openly across the organization.

14. What is 'shift left' in DevOps?

    Moving testing, security, and quality activities earlier in the development lifecycle to catch and fix issues sooner and cheaper.

15. What is observability in DevOps?

    The ability to understand a system's internal state from its external outputs (logs, metrics, traces), enabling teams to detect, diagnose, and learn from issues.

16. What is the difference between monitoring and observability?

    Monitoring tracks known, predefined conditions (is X healthy?); observability lets you explore unknown problems and ask new questions about system behavior.

17. What is the relationship between Lean and DevOps?

    DevOps applies Lean manufacturing principles—eliminating waste, optimizing flow, reducing batch sizes, and pursuing continuous improvement—to software delivery.

18. What does 'small batch size' mean in DevOps and why is it valuable?

    Releasing small, incremental changes frequently; smaller batches reduce risk, simplify debugging, speed feedback, and lower the impact of any single failure.

19. What is a 'feedback loop' and why is it central to DevOps?

    A cycle where output information returns to inform the next iteration; short, fast feedback loops let teams detect problems quickly and continuously improve.

20. How does DevOps relate to Site Reliability Engineering (SRE)?

    SRE is a specific implementation of DevOps principles by Google, using software engineering to operations problems, with concepts like SLOs, error budgets, and toil reduction.

21. What is an 'error budget' in SRE/DevOps?

    The acceptable amount of unreliability (downtime) allowed by a service-level objective; it balances release velocity against reliability. $$\text{Error budget} = 1 - \text{SLO}$$

22. Compare 'waterfall' and 'DevOps' delivery models.

    Waterfall uses sequential phases with infrequent, large releases and siloed teams; DevOps uses continuous, automated, frequent small releases with cross-functional collaboration.

23. What cultural shift is required to move from 'firefighting' to continuous improvement?

    Shifting from reactive incident response and blame toward proactive prevention, systemic thinking, blameless learning, and investing in automation and resilience.

24. How do collaboration and blameless culture reinforce continuous improvement?

    Open collaboration and blame-free postmortems build the psychological safety needed for honest feedback, which fuels the learning loops that drive ongoing improvement.

What this deck covers

Introduction to DevOps flashcards FAQ