โ† All AZ-400 Flashcard Decks

Development Processes & Continuous Integration Flashcards

7 cards from real AZ-400 practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 7 Development Processes & Continuous Integration flashcards as text
  1. A team wants to enforce that no code is merged into the main branch without at least two reviewers approving the pull request. Where in Azure DevOps is this configured?

    Answer: Branch policies in Azure Repos

    Branch policies in Azure Repos allow you to require a minimum number of reviewers before a pull request can be completed.

  2. Which Azure Pipelines feature allows you to define reusable pipeline logic that can be called from multiple pipelines?

    Answer: Templates

    Templates in Azure Pipelines enable you to define reusable steps, jobs, or stages that can be referenced across multiple pipeline definitions.

  3. A developer commits code that breaks a shared library used by five downstream services. What CI practice would catch this regression earliest?

    Answer: Multi-repo pipeline triggers that build dependents on library changes

    Multi-repo pipeline triggers automatically build and test downstream services whenever the shared library is updated, catching regressions immediately.

  4. What is the primary purpose of a 'quality gate' in a CI pipeline?

    Answer: To enforce minimum quality thresholds before allowing progression

    Quality gates enforce defined thresholds (e.g., code coverage, test pass rate) and block pipeline progression if the code does not meet them.

  5. You need to run integration tests that require a SQL Server database in your Azure Pipeline. What is the recommended approach?

    Answer: Use service containers in the pipeline YAML to spin up a SQL Server container per build

    Service containers in Azure Pipelines spin up Docker-based dependencies like SQL Server for the duration of the job, providing isolation per build.

  6. A team uses Git Flow and wants CI to trigger only on feature branches and the develop branch, not on hotfix branches. How should they configure this in Azure Pipelines YAML?

    Answer: Use include/exclude filters under the 'branches' key in the trigger block

    The 'branches' key in the trigger block supports include and exclude lists using wildcard patterns to control which branches trigger the pipeline.

  7. Which metric best indicates that a team's CI pipeline is providing fast feedback to developers?

    Answer: Average build duration from commit to result notification

    Average build duration measures how quickly developers receive feedback after committing, which is the core value proposition of CI.