Azure Pipelines YAML Fundamentals Quiz

1. What is the function of the 'condition' keyword in Azure Pipelines YAML?

Control whether a task or job runs based on a condition

Define branching logic for stage execution

Validate input parameters before pipeline start

Set approval requirements for deployments

2. What is the primary benefit of using YAML pipelines over classic pipelines in Azure DevOps?

YAML pipelines are version-controlled and easier to maintain in source code

YAML pipelines execute faster than classic pipelines

YAML pipelines support more task types than classic pipelines

YAML pipelines require fewer permissions to configure

3. Which keyword allows you to define parameters that can be passed to a pipeline at queue time?

Parameters

Variables

Inputs

Arguments

4. In Azure Pipelines, what is the default behavior when no 'trigger' is specified?

All commits to all branches trigger a build

Only manual triggers are allowed

No builds are triggered automatically

Only the main branch triggers builds

5. What does the 'checkout' task do in an Azure Pipelines YAML file?

Downloads the source code repository to the agent

Verifies pipeline syntax before execution

Exports build artifacts to storage

Authenticates with external services

6. Which of the following correctly represents a multi-stage pipeline structure in Azure Pipelines?

Build stage → Test stage → Release stage

Compile → Link → Package → Deploy

Initialize → Validate → Execute → Finalize

Checkout → Install → Build → Archive

7. In Azure Pipelines YAML, what is the purpose of 'displayName'?

Provides a human-readable name for a task or job

Sets the output variable name for results

Configures the user interface dashboard

Specifies the build number format

8. What does 'continueOnError' do in an Azure Pipelines task?

Allows the pipeline to continue even if the task fails

Automatically retries failed tasks

Logs errors without stopping execution

Sends error notifications to administrators

9. Which keyword specifies the operating system and software on the agent?

VmImage

OsType

AgentOS

Platform

10. In Azure Pipelines, what does the 'template' keyword allow you to do?

Reuse YAML pipeline definitions across multiple pipelines

Create default variable sets for all jobs

Generate reports from build logs

Configure Docker image templates

11. What is the primary purpose of the 'trigger' keyword in an Azure Pipelines YAML file?

Define which branches automatically start a pipeline run

Set the schedule for manual pipeline execution

Configure email notifications for build failures

Specify the Azure DevOps project name

12. Which task is commonly used to publish build artifacts in Azure Pipelines?

PublishBuildArtifacts

UploadArtifacts

SaveBuild

ArchiveFiles

13. What does 'dependsOn' accomplish in an Azure Pipelines YAML file?

Creates a dependency between jobs or stages

Specifies required NuGet package versions

Links to external GitHub repositories

Configures Azure DevOps permissions

14. In Azure Pipelines, how do you reference a variable named 'buildVersion' in YAML?

$(buildVersion)

$buildVersion

{buildVersion}

@buildVersion

15. What is the purpose of the 'pool' keyword in a pipeline YAML file?

Specify the agent pool where jobs run

Define shared resource groups across projects

Configure database connection pooling

Set up load balancing for deployments

16. Which of the following correctly defines a job in Azure Pipelines YAML?

A collection of stages that run on the same agent

A unit of work that can run on an agent pool

A manual approval step between deployments

A scheduled task that runs daily

17. In Azure Pipelines, what does 'pr' under the trigger section control?

Pull request validation builds

Production release approvals

Performance reporting metrics

Priority level assignment

18. What is the correct YAML syntax for a basic script task that runs a shell command?

- script: echo 'Hello World'

- run: echo 'Hello World'

- execute: echo 'Hello World'

- command: echo 'Hello World'

19. Which keyword is used to define environment variables available to all tasks in a pipeline?