โ† All AZ-400 Flashcard Decks

Continuous Delivery 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 Continuous Delivery flashcards as text
  1. Which Azure DevOps feature allows you to require a manual approval before a deployment proceeds to a production stage?

    Answer: Pre-deployment approval gate

    Pre-deployment approvals in Azure Pipelines let you designate approvers who must sign off before a stage begins.

  2. A team wants to deploy to Azure App Service only when code coverage stays above 80%. Which mechanism enforces this in a release pipeline?

    Answer: Quality gate

    Quality gates query external services (like SonarCloud) and block or allow deployment based on metric thresholds.

  3. What is the purpose of a deployment slot in Azure App Service during a continuous delivery process?

    Answer: It allows zero-downtime deployments via slot swap

    Deployment slots let you deploy to a staging slot and then swap it with production, achieving near-zero downtime.

  4. Which artifact source type in Azure Pipelines supports triggering a release pipeline when a new Docker image is pushed?

    Answer: Azure Container Registry

    Azure Container Registry can be configured as an artifact source, triggering releases when a new image tag is pushed.

  5. A YAML pipeline uses the 'environment' keyword targeting a Kubernetes namespace. What additional capability does this unlock?

    Answer: Deployment history tracking and approvals at the environment level

    Using environments in YAML pipelines enables deployment history, traceability, and approval/check policies at the environment scope.

  6. When configuring a multi-stage YAML pipeline, which keyword controls the condition under which a stage runs?

    Answer: condition

    The 'condition' keyword evaluates an expression at runtime to decide whether a stage or job should execute.

  7. Your team wants every production deployment to be traceable to a specific work item. Which Azure DevOps feature supports this requirement?

    Answer: Deployment history linked to commits and work items

    Azure Pipelines automatically associates commits and linked work items to each deployment recorded in the release history.