Practice Test GeeksSAFe - Scaled Agile Framework Practice Test
← All SAFE Flashcard Decks

Continuous Delivery Pipeline and DevOps Flashcards

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

Read the first 6 Continuous Delivery Pipeline and DevOps flashcards as text

  1. What is a 'Definition of Done (DoD)' at the ART level in SAFe?

    Answer: The criteria that must be met for a Feature or PI Increment to be considered complete and releasable

    The ART-level DoD defines the quality and completeness standards a Feature or PI Increment must meet to be considered potentially releasable.

  2. What is 'Test-Driven Development (TDD)' in the context of SAFe Built-in Quality?

    Answer: Writing automated tests before writing the code, using tests to drive the design and validate correctness

    TDD is a development practice where developers write failing unit tests first, then write the minimum code to pass them, ensuring quality is built in from the start.

  3. What is 'Behavior-Driven Development (BDD)' in SAFe?

    Answer: A collaborative technique using Given-When-Then scenarios to define and verify behavior from the customer's perspective

    BDD uses Given-When-Then format to create executable specifications that serve as both documentation and automated acceptance tests, bridging business and technical teams.

  4. What does the SAFe 'Test Automation Pyramid' recommend?

    Answer: A large base of fast unit tests, fewer integration tests, and minimal UI/end-to-end tests — to maximize speed and reliability

    The Test Automation Pyramid recommends many fast unit tests at the base, fewer integration tests in the middle, and minimal slow E2E tests at the top — for fast feedback.

  5. What is 'Pair Work' in the context of SAFe Built-in Quality?

    Answer: Two practitioners collaborating in real time on a single task to improve quality, share knowledge, and catch errors

    Pair Work (including Pair Programming and Pair Testing) improves code quality, knowledge sharing, and error detection by having two practitioners work together simultaneously.

  6. What is a 'Non-Functional Requirement (NFR)' and how is it handled in SAFe?

    Answer: A system quality attribute (e.g., performance, security, scalability) that constrains how the system must work

    NFRs define quality attributes (performance, security, reliability, usability) that constrain the system and are incorporated into the Definition of Done and Enabler Stories.