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.