Azure Boards for tracking - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Azure Boards Work Items

Which type of Azure Boards work item is best suited for tracking a new feature request from a customer?

A Bug

B Epic

C Task

D User Story

💡 Hint

Think about the item that represents a feature from the user's perspective.

A User Story represents a feature or requirement from the user's perspective, making it ideal for tracking new feature requests.

❓ Architecture

intermediate

Organizing Azure Boards for Large Projects

You have a large project with multiple teams working on different features. How should you organize Azure Boards to best track progress?

A Create one board and assign all work items to it regardless of team

B Use only Epics to track all work items without boards

C Create separate boards for each team and link work items to a shared backlog

D Create multiple projects in Azure DevOps, one per team, without shared backlogs

💡 Hint

Consider how teams can work independently but still align on overall progress.

Separate boards per team allow focused tracking, while linking work items to a shared backlog keeps overall project visibility.

❓ service_behavior

advanced

Azure Boards Query Behavior

What will be the result of running this Azure Boards query:
"Work Item Type = Bug AND State = Closed"?

A Returns all bugs that are currently open

B Returns all bugs that have been closed

C Returns all work items except bugs

D Returns all work items regardless of state

💡 Hint

Focus on the filter conditions in the query.

The query filters work items to only those of type Bug and with the state Closed, so it returns all closed bugs.

❓ security

advanced

Azure Boards Access Control

Which Azure DevOps permission setting will prevent a user from editing work items but still allow them to view all work items on a board?

A Deny 'Edit work items in this node' and Allow 'View work items in this node'

B Allow 'Edit work items in this node' and Deny 'View work items in this node'

C Deny both 'Edit work items in this node' and 'View work items in this node'

D Allow both 'Edit work items in this node' and 'View work items in this node'

💡 Hint

Think about how to restrict editing but keep visibility.

Denying edit permission while allowing view permission lets users see work items but not change them.

✅ Best Practice

expert

Optimizing Azure Boards for Continuous Delivery

To support continuous delivery, which Azure Boards practice ensures work items flow smoothly from development to deployment?

A Define clear states and transitions that map to deployment stages and automate state changes with pipelines

B Use a single state for all work items to simplify tracking

C Manually update work item states only after deployment is complete

D Avoid linking work items to commits or builds to reduce complexity

💡 Hint

Consider how automation and clear tracking help continuous delivery.

Defining states that reflect deployment stages and automating transitions with pipelines ensures smooth, reliable delivery tracking.

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