Practice Test Geeks(SRE) Site Reliability Engineering Foundation Certification Practice Test
← All SRE Flashcard Decks

Release Engineering & CI/CD Flashcards

7 cards from real SRE practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 7 Release Engineering & CI/CD flashcards as text

  1. What is the purpose of a 'staging environment' in a release pipeline?

    Answer: To provide a production-like environment for final validation before releasing to end users

    Staging mimics production so that final integration and acceptance tests catch issues before they reach real users.

  2. What is 'deployment frequency' and why does it matter for SRE?

    Answer: How often a team successfully deploys to production — higher frequency indicates a healthier delivery process

    Higher deployment frequency signals that teams can deliver value quickly and safely, a key DORA elite performance indicator.

  3. Which practice ensures that a failed pipeline step stops downstream stages from running?

    Answer: Fast-fail (fail-fast) configuration where any failing step aborts the pipeline

    Fail-fast stops pipeline execution immediately on failure, preventing wasted compute and surfacing problems early.

  4. In release engineering, what is the purpose of semantic versioning (SemVer)?

    Answer: To communicate the type and impact of changes (major, minor, patch) through the version number

    SemVer uses MAJOR.MINOR.PATCH to signal breaking changes, new features, and bug fixes respectively.

  5. What is a 'post-deployment smoke test' in a CI/CD pipeline?

    Answer: A minimal set of critical checks run immediately after deployment to verify the application is functional

    Smoke tests are lightweight, fast checks that verify core functionality is working right after deployment before deeper validation.

  6. Which approach helps an SRE team reduce the blast radius of a faulty deployment?

    Answer: Using smaller, incremental deployments with automated rollback triggers

    Smaller, frequent deployments limit the scope of any single change, making issues easier to isolate and roll back.

  7. What is the role of a 'release train' model in large-scale software delivery?

    Answer: A fixed-schedule release cadence where features that are ready board the next scheduled release

    The release train model ships on a fixed schedule regardless of individual feature readiness, promoting predictability and discipline.