Build pipeline basics in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Azure DevOps YAML Pipeline: Output of a simple build step

What will be the output of this Azure DevOps pipeline step when it runs successfully?

Azure

steps:
- script: echo Hello, Azure DevOps!
  displayName: 'Print greeting'

A Hello, Azure DevOps!

B Print greeting

C

steps:
- script: echo Hello, Azure DevOps!

D No output, only logs

💡 Hint

The script step runs a shell command and prints its output.

The script step runs the echo command, which outputs the text 'Hello, Azure DevOps!' to the console.

🧠 Conceptual

intermediate

Purpose of triggers in Azure DevOps pipelines

What is the main purpose of the 'trigger' keyword in an Azure DevOps YAML pipeline?

A To specify when the pipeline should automatically start based on branch changes

B To define the build agent pool to use

C To set environment variables for the pipeline

D To list the tasks to run in the pipeline

💡 Hint

Think about what causes the pipeline to run automatically.

The 'trigger' keyword defines which branches or paths cause the pipeline to start automatically when code is pushed.

🔀 Workflow

advanced

Correct order of steps in a build pipeline

Arrange these steps in the correct order for a typical Azure DevOps build pipeline.

A 4,2,1,3

B 2,1,4,3

C 2,4,1,3

D 1,2,4,3

💡 Hint

Think about what must happen before building and testing.

First, source code must be checked out, then built, then tested, and finally artifacts are published.

❓ Troubleshoot

advanced

Diagnosing a failed pipeline due to missing agent pool

An Azure DevOps pipeline fails immediately with the error: 'No agent found in pool Default'. What is the most likely cause?

A The repository URL is invalid

B The pipeline YAML syntax is incorrect

C The build script has a runtime error

D The specified agent pool 'Default' has no available agents to run the job

💡 Hint

Consider what the error message says about the agent pool.

The error means the pipeline cannot find any active agents in the specified pool to run the job.

✅ Best Practice

expert

Recommended practice for storing secrets in Azure DevOps pipelines

Which is the best practice for securely using passwords or API keys in Azure DevOps pipelines?

A Save secrets in a public repository file and read them during the build

B Store secrets in pipeline variables marked as secret and reference them in the YAML

C Send secrets as plain text in pipeline logs for debugging

D Hardcode secrets directly in the YAML file for easy access

💡 Hint

Think about how to keep secrets safe and hidden.

Marking variables as secret hides their values in logs and protects them during pipeline runs.