Release pipeline basics in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a release pipeline stage in Azure DevOps.

Azure

stages:
- stage: [1]
  jobs:
  - job: Build
    steps:
    - script: echo Building...

Drag options to blanks, or click blank then click option'

ABuild

BDeploy

CTest

DRelease

Attempts:

3 left

💡 Hint

Common Mistakes

Using a stage name that doesn't match the job purpose.

Confusing job names with stage names.

The stage name defines a phase in the release pipeline. Here, Build is the correct stage name for the build job.

2fill in blank

medium

Complete the code to specify the trigger for the release pipeline.

Azure

trigger:
  branches:
    include:
    - [1]

Drag options to blanks, or click blank then click option'

Afeature

Bdev

Crelease

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Using a feature branch as the trigger for production releases.

Forgetting to include the branch name under include.

The trigger defines which branch starts the pipeline. Usually, main is the primary branch for releases.

3fill in blank

hard

Fix the error in the deployment job to correctly specify the agent pool.

Azure

jobs:
- deployment: DeployWeb
  pool:
    vmImage: [1]
  environment: 'production'
  strategy:
    runOnce:
      deploy:
        steps:
        - script: echo Deploying...

Drag options to blanks, or click blank then click option'

Awindows-latest

Bubuntu-latest

Cmacos-latest

Dlinux-latest

Attempts:

3 left

💡 Hint

Common Mistakes

Using an invalid vmImage name like 'linux-latest' which is not recognized.

Confusing OS names or misspelling the image name.

The vmImage specifies the OS image for the agent. ubuntu-latest is a valid and common choice for deployment jobs.

4fill in blank

hard

Fill both blanks to define a job with a script step that runs a deployment command.

Azure

jobs:
- job: Deploy
  steps:
  - script: [1] [2]

Drag options to blanks, or click blank then click option'

Aaz

Bdeploy

Crun

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect command words that do not form a valid Azure CLI command.

Swapping the order of command parts.

The Azure CLI command az deploy is used to run deployment scripts in pipelines.

5fill in blank

hard

Fill all three blanks to create a release pipeline variable group reference with a secret variable.

Azure

variables:
- group: [1]
- name: [2]
  value: [3]
  isSecret: true

Drag options to blanks, or click blank then click option'

AProdSecrets

BAPI_KEY

C$(mySecretValue)

DDevSecrets

Attempts:

3 left

💡 Hint

Common Mistakes

Using a non-secret value for a secret variable.

Mixing variable group names or variable names incorrectly.

The variable group ProdSecrets holds secret variables. API_KEY is the variable name, and $(mySecretValue) references the secret value securely.

Practice

1. What is the main purpose of a release pipeline in Azure DevOps?

easy

A. To monitor user activity on a website

B. To automate the delivery of applications through different stages

C. To write code for applications

D. To store application data securely

Solution

1. Step 1: Understand the role of a release pipeline

   A release pipeline automates the process of delivering software through stages like testing and production.

2. Step 2: Identify the correct purpose

   Among the options, only automating delivery matches the release pipeline's function.

3. Final Answer:

   To automate the delivery of applications through different stages -> Option B

4. Quick Check:

   Release pipeline = automate delivery [OK]

Hint: Release pipelines automate app delivery stages [OK]

Common Mistakes:

• Confusing release pipeline with coding or monitoring tools
• Thinking it stores data instead of deploying apps

2. Which syntax correctly defines a stage in an Azure release pipeline YAML?

easy

A. stage:
- Build
jobs: []

B. jobs:
- stage: Build

C. stages:
Build:
jobs: []

D. stages:
- stage: Build
jobs: []

Solution

1. Step 1: Review YAML structure for stages

   In Azure pipelines, stages are defined under 'stages:' as a list with '- stage:' entries.

2. Step 2: Match correct syntax

   stages: - stage: Build jobs: [] correctly uses 'stages:' followed by '- stage: Build' and an empty jobs list.

3. Final Answer:

   stages: - stage: Build jobs: [] -> Option D

4. Quick Check:

   Stages list starts with 'stages:' and '- stage:' [OK]

Hint: Stages use 'stages:' then '- stage:' list items [OK]

Common Mistakes:

• Using singular 'stage:' instead of 'stages:'
• Placing 'stage' inside 'jobs' incorrectly
• Incorrect indentation or list syntax

3. Given this YAML snippet in a release pipeline:

stages:
  - stage: Test
    jobs:
      - job: RunTests
        steps:
          - script: echo Testing

What will be the output when this pipeline runs?

medium

A. It will print 'Testing' in the job logs

B. It will print 'echo Testing' literally

C. No output will be shown

D. The pipeline will fail due to syntax error

Solution

1. Step 1: Understand the script step in pipeline

   The 'script' step runs the command given, here 'echo Testing', which prints 'Testing'.

2. Step 2: Predict output

   Since the script runs successfully, the output 'Testing' appears in the job logs.

3. Final Answer:

   It will print 'Testing' in the job logs -> Option A

4. Quick Check:

   Script runs command, prints output [OK]

Hint: Script steps run commands and show output [OK]

Common Mistakes:

• Thinking script prints the command text instead of output
• Assuming syntax error without checking YAML correctness
• Expecting no output from script step

4. You have this YAML snippet in a release pipeline:

stages:
  - stage: Deploy
    jobs:
      - job: DeployJob
        steps:
          - script: echo Deploying
          - script: echo Done
        dependsOn: Build

What is wrong with this pipeline configuration?

medium

A. 'dependsOn' should be inside the stage, not inside jobs

B. 'dependsOn' must be a job, not a stage

C. The 'steps' section cannot have multiple scripts

D. The 'jobs' keyword is not allowed inside stages

Solution

1. Step 1: Locate 'dependsOn' usage

   'dependsOn' controls stage dependencies and must be placed at the stage level, not inside jobs.

2. Step 2: Identify correct placement

   In the snippet, 'dependsOn: Build' is incorrectly placed inside the job, it should be directly under the stage.

3. Final Answer:

   'dependsOn' should be inside the stage, not inside jobs -> Option A

4. Quick Check:

   'dependsOn' belongs to stage level [OK]

Hint: 'dependsOn' goes under stage, not job [OK]

Common Mistakes:

• Placing 'dependsOn' inside jobs instead of stages
• Thinking 'dependsOn' applies to jobs only
• Believing multiple scripts in steps is invalid

5. You want to create a release pipeline with two stages: Build and Deploy. Deploy should only run if Build succeeds. Which YAML snippet correctly sets this up?

hard

A. stages:
- stage: Build
jobs:
- job: BuildJob
steps:
- script: echo Building
- stage: Deploy
jobs:
- job: DeployJob
steps:
- script: echo Deploying

B. stages:
- stage: Build
dependsOn: Deploy
jobs:
- job: BuildJob
steps:
- script: echo Building
- stage: Deploy
jobs:
- job: DeployJob
steps:
- script: echo Deploying

C. stages:
- stage: Build
jobs:
- job: BuildJob
steps:
- script: echo Building
- stage: Deploy
dependsOn: Build
jobs:
- job: DeployJob
steps:
- script: echo Deploying

D. stages:
- stage: Deploy
dependsOn: Build
jobs:
- job: DeployJob
steps:
- script: echo Deploying
- stage: Build
jobs:
- job: BuildJob
steps:
- script: echo Building

Solution

1. Step 1: Understand stage dependencies

   To run Deploy only after Build succeeds, Deploy stage must depend on Build.

2. Step 2: Check YAML for correct 'dependsOn'

   stages: - stage: Build jobs: - job: BuildJob steps: - script: echo Building - stage: Deploy dependsOn: Build jobs: - job: DeployJob steps: - script: echo Deploying places 'dependsOn: Build' under Deploy stage, correctly setting the dependency.

3. Step 3: Verify order and jobs

   Build stage is first, Deploy second, with proper jobs and steps defined.

4. Final Answer:

   Correctly sets Deploy to depend on Build -> Option C

5. Quick Check:

   'dependsOn' on Deploy stage = correct dependency [OK]

Hint: Use 'dependsOn' on Deploy stage to wait for Build [OK]

Common Mistakes:

• Reversing 'dependsOn' causing wrong execution order
• Omitting 'dependsOn' so stages run in parallel
• Placing stages in wrong order without dependencies