Azure Boards for tracking - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new work item in Azure Boards using Azure CLI.

Azure

az boards work-item create --title "Fix bug" --type [1]

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

AEpic

BTask

CFeature

DBug

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Task or Feature instead of Bug for defect tracking.

The correct work item type to track a bug is Bug.

2fill in blank

medium

Complete the code to list all work items assigned to a user in Azure Boards.

Azure

az boards query --wiql "SELECT [System.Id], [System.Title] FROM WorkItems WHERE [System.AssignedTo] = '[1]'"

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

AActive

BProjectName

[e-mail]

DBug

Attempts:

3 left

💡 Hint

Common Mistakes

Using project name or work item type instead of user email.

The query filters work items assigned to a specific user email.

3fill in blank

hard

Fix the error in the Azure Boards query to filter work items by state.

Azure

az boards query --wiql "SELECT [System.Id] FROM WorkItems WHERE [System.State] = '[1]'"

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

AResolved

BComplete

CDone

Dresolving

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect or lowercase state names causing query failure.

The correct state value is Resolved with capital R and exact spelling.

4fill in blank

hard

Fill both blanks to create a query that selects work items with priority 1 and state Active.

Azure

az boards query --wiql "SELECT [System.Id] FROM WorkItems WHERE [System.Priority] = [1] AND [System.State] = '[2]'"

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

A1

B2

CActive

DClosed

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing priority numbers or using wrong state names.

Priority 1 means highest priority and state Active means work item is in progress.

5fill in blank

hard

Fill all three blanks to create a work item with title, assigned user, and area path.

Azure

az boards work-item create --title '[1]' --assigned-to '[2]' --area-path '[3]'

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

AImplement login feature

[e-mail]

CProjectX\Frontend

DFix bug

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong values for title, email, or area path.

The title describes the task, assigned-to is the user's email, and area path specifies the project area.

Practice

1. What is the main purpose of Azure Boards in project management?

easy

A. To host websites and web applications

B. To help teams track work using cards and lists

C. To store large amounts of data securely

D. To manage virtual machines and networks

Solution

1. Step 1: Understand Azure Boards functionality

   Azure Boards is designed to help teams organize and track their work visually using cards and lists.

2. Step 2: Compare options with Azure Boards purpose

   Options A, B, and D describe other Azure services, not Azure Boards.

3. Final Answer:

   To help teams track work using cards and lists -> Option B

4. Quick Check:

   Azure Boards = Work tracking with cards and lists [OK]

Hint: Azure Boards = tracking work visually with cards [OK]

Common Mistakes:

• Confusing Azure Boards with Azure Storage
• Thinking Azure Boards manages infrastructure
• Mixing Azure Boards with Azure App Services

2. Which of the following is a valid work item type in Azure Boards?

easy

A. User Story

B. Virtual Machine

C. Blob Storage

D. SQL Database

Solution

1. Step 1: Identify work item types in Azure Boards

   Common work items include User Stories, Bugs, Tasks, and Features.

2. Step 2: Eliminate unrelated Azure services

   Virtual Machine, Blob Storage, and SQL Database are Azure infrastructure or service types, not work items.

3. Final Answer:

   User Story -> Option A

4. Quick Check:

   User Story = valid work item type [OK]

Hint: Work items = User Story, Bug, Task, Feature [OK]

Common Mistakes:

• Confusing Azure services with work items
• Selecting infrastructure components as work items
• Not recognizing User Story as a work item

3. Given a team using Azure Boards, which view shows the prioritized list of work items to be done next?

medium

A. Backlog

B. Dashboard

C. Repository

D. Pipeline

Solution

1. Step 1: Understand Azure Boards views

   The Backlog view lists work items prioritized for upcoming work.

2. Step 2: Differentiate other views

   Dashboard shows summary widgets, Repository holds code, Pipeline manages builds and releases.

3. Final Answer:

   Backlog -> Option A

4. Quick Check:

   Backlog = prioritized work list [OK]

Hint: Backlog = prioritized work items list [OK]

Common Mistakes:

• Confusing Dashboard with Backlog
• Mixing code repository with work tracking
• Thinking Pipeline shows work priorities

4. A team member cannot see the Azure Board for their project. What is the most likely cause?

medium

A. The Azure Board service is offline

B. They are using the wrong browser

C. Their internet connection is too slow

D. They do not have the correct project permissions

Solution

1. Step 1: Check common access issues in Azure Boards

   Access to Boards depends on project permissions assigned to users.

2. Step 2: Evaluate other options

   Azure Boards is a cloud service with high availability, so service offline is unlikely. Internet speed or browser issues usually cause loading delays, not complete invisibility.

3. Final Answer:

   They do not have the correct project permissions -> Option D

4. Quick Check:

   Permissions control Board visibility [OK]

Hint: Check user permissions first for Board access issues [OK]

Common Mistakes:

• Assuming service outage without checking permissions
• Blaming internet speed for access denial
• Ignoring permission settings

5. A team wants to track bugs and user stories separately but see both on one board. How can they configure Azure Boards to achieve this?

hard

A. Merge Bugs and User Stories into a single work item type

B. Create two separate projects, one for Bugs and one for User Stories

C. Create separate work item queries for Bugs and User Stories, then add both queries as cards on a single board

D. Use Azure Pipelines to automate bug tracking and user stories

Solution

1. Step 1: Understand Azure Boards customization

   Azure Boards allows adding multiple queries as card sources on one board to show different work item types together.

2. Step 2: Evaluate other options

   Creating separate projects splits work and complicates tracking. Azure Pipelines is for automation, not work item display. Merging work item types loses distinction.

3. Final Answer:

   Create separate work item queries for Bugs and User Stories, then add both queries as cards on a single board -> Option C

4. Quick Check:

   Use queries to combine work items on one board [OK]

Hint: Use queries to show multiple work types on one board [OK]

Common Mistakes:

• Splitting work into separate projects unnecessarily
• Confusing Pipelines with Boards functionality
• Trying to merge distinct work item types