Why DevOps integration matters in Azure - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a pipeline trigger on the main branch.

Azure

trigger:
  branches:
    include:
      - [1]

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

Adevelop

Brelease

Cfeature

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a feature branch instead of the main branch for triggers.

Leaving the trigger section empty, so pipeline never runs automatically.

The pipeline triggers on the main branch to automate deployment when code changes.

2fill in blank

medium

Complete the code to add a build job named 'BuildApp'.

Azure

jobs:
- job: [1]
  steps:
    - script: echo Building the app

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

ABuildApp

BTestApp

CDeployApp

DCleanApp

Attempts:

3 left

💡 Hint

Common Mistakes

Using a job name that does not match the build step.

Using generic names that confuse the pipeline purpose.

The job name BuildApp clearly indicates the build process in the pipeline.

3fill in blank

hard

Fix the error in the pipeline step to use the correct task for Azure CLI.

Azure

- task: [1]
  inputs:
    azureSubscription: 'MyAzureSub'
    scriptType: 'ps'
    scriptLocation: 'inlineScript'
    inlineScript: 'az group list'

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

AAzurePowerShell@5

BAzureCLI@2

CBash@3

DPowerShell@2

Attempts:

3 left

💡 Hint

Common Mistakes

Using PowerShell task for Azure CLI commands causes errors.

Choosing Bash task when scriptType is PowerShell.

The AzureCLI@2 task runs Azure CLI commands in the pipeline.

4fill in blank

hard

Fill both blanks to define a deployment job that depends on the build job and runs on Ubuntu.

Azure

jobs:
- job: DeployApp
  dependsOn: [1]
  pool:
    vmImage: [2]
  steps:
    - script: echo Deploying the app

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

ABuildApp

BTestApp

Cwindows-latest

Dubuntu-latest

Attempts:

3 left

💡 Hint

Common Mistakes

Setting dependsOn to a wrong job name.

Using Windows VM image when Linux is required.

The deployment job depends on the BuildApp job and runs on ubuntu-latest VM image.

5fill in blank

hard

Fill all three blanks to create a variable group reference with a secure variable and a script step using it.

Azure

variables:
- group: [1]
- name: secretToken
  value: $[2]
steps:
- script: echo Token is [3]

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

AMyVariableGroup

BsecretToken

C$(secretToken)

DtokenValue

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect syntax to access variables in scripts.

Not referencing the variable group properly.

The variable group MyVariableGroup is referenced. The secret variable secretToken is accessed with $(secretToken) syntax in the script.

Practice

1. Why is DevOps integration important in cloud projects?

easy

A. It replaces all developers with robots

B. It makes cloud servers run faster physically

C. It automates software delivery to speed up releases

D. It removes the need for testing code

Solution

1. Step 1: Understand DevOps integration purpose

   DevOps integration connects tools to automate software delivery processes.

2. Step 2: Identify the main benefit

   This automation helps teams release software faster and with better quality.

3. Final Answer:

   It automates software delivery to speed up releases -> Option C

4. Quick Check:

   DevOps integration = automation and faster releases [OK]

Hint: DevOps means automating delivery, not replacing people [OK]

Common Mistakes:

• Thinking DevOps replaces developers
• Believing DevOps speeds up hardware
• Assuming DevOps removes testing

2. Which Azure service is commonly used to create automated DevOps pipelines?

easy

A. Azure DevOps Pipelines

B. Azure Virtual Machines

C. Azure Blob Storage

D. Azure Cosmos DB

Solution

1. Step 1: Identify Azure services for automation

   Azure DevOps Pipelines is designed to automate build, test, and deployment.

2. Step 2: Exclude unrelated services

   Blob Storage stores files, VMs run servers, Cosmos DB is a database; none automate pipelines.

3. Final Answer:

   Azure DevOps Pipelines -> Option A

4. Quick Check:

   Pipeline automation = Azure DevOps Pipelines [OK]

Hint: Pipelines automate builds and deploys in Azure DevOps [OK]

Common Mistakes:

• Confusing storage or database services with pipelines
• Choosing virtual machines for automation tasks

3. Given this Azure DevOps pipeline snippet:

trigger:
  branches:
    include:
      - main

steps:
- script: echo "Deploying app..."
  displayName: 'Deploy Step'

What happens when code is pushed to the main branch?

medium

A. Nothing happens automatically

B. The pipeline runs and prints 'Deploying app...'

C. The pipeline deletes the main branch

D. The pipeline runs but skips the deploy step

Solution

1. Step 1: Understand trigger configuration

   The pipeline triggers on pushes to the 'main' branch as specified.

2. Step 2: Check pipeline steps

   It runs a script that echoes 'Deploying app...'.

3. Final Answer:

   The pipeline runs and prints 'Deploying app...' -> Option B

4. Quick Check:

   Trigger on main branch runs deploy echo [OK]

Hint: Trigger on main means pipeline runs on push [OK]

Common Mistakes:

• Thinking pipeline does nothing without manual start
• Assuming pipeline deletes branches
• Believing steps are skipped without reason

4. You wrote this Azure DevOps pipeline YAML:

trigger:
  branches:
    include:
      - main

steps:
- script: echo "Deploying app..."
  displayName: 'Deploy Step'
- script: echo "Testing app..."
  displayName: 'Test Step'
  condition: failed()

Why does the 'Test Step' never run?

medium

A. Because 'Test Step' is missing a script command

B. Because the pipeline triggers only on 'main' branch

C. Because 'echo' commands are not allowed in pipelines

D. Because the condition 'failed()' runs only if previous steps failed

Solution

1. Step 1: Analyze the condition on 'Test Step'

   The condition 'failed()' means this step runs only if a previous step failed.

2. Step 2: Check previous steps

   The 'Deploy Step' runs successfully, so 'Test Step' does not run.

3. Final Answer:

   Because the condition 'failed()' runs only if previous steps failed -> Option D

4. Quick Check:

   Condition failed() runs step only on failure [OK]

Hint: Condition 'failed()' runs step only if earlier step fails [OK]

Common Mistakes:

• Thinking trigger affects step conditions
• Believing echo commands are invalid
• Assuming missing script command

5. Your team wants to improve software quality by integrating automated tests in Azure DevOps pipelines. Which approach best supports this goal?

hard

A. Add test scripts to run automatically after each code commit

B. Run tests manually only before major releases

C. Skip tests to speed up deployment

D. Test only on developer machines, not in pipelines

Solution

1. Step 1: Identify best practice for quality

   Automated tests running after each commit catch issues early and improve quality.

2. Step 2: Compare other options

   Manual or skipped tests delay feedback or reduce quality assurance.

3. Final Answer:

   Add test scripts to run automatically after each code commit -> Option A

4. Quick Check:

   Automated tests after commits = better quality [OK]

Hint: Automate tests on every commit to catch bugs early [OK]

Common Mistakes:

• Delaying tests until major releases
• Skipping tests to save time
• Testing only locally, not in pipelines