In Azure DevOps web portal, you have a work item itemA that depends on another work item itemB. How should you represent this dependency on itemA?
Choose an answer
Tap an option to check your answer.
Correct answer: From itemA, open the Links tab, and then select Add link. Set Link type to Successor and add the ID of itemB..
Why this is the answer
To represent a dependency where itemA depends on itemB, you should use a "Successor" link from itemA to itemB. This indicates that itemA (the successor) cannot start or complete until itemB (the predecessor) is finished. The Links tab within a work item is the correct place to manage these relationships. Incorrect options: "Add a Parent link to the user story of itemA" is incorrect because a Parent link defines a hierarchical relationship (e.g., a Feature is a parent of a User Story), not a dependency between two items at the same or similar level. "From Backlogs, open the context menu, select Add link, and then select itemA. Set Link type to References and add the ID of itemB" is incorrect because adding links is typically done from within the work item itself, not directly from the backlog context menu in this manner for a specific dependency. Also, "References" is a generic link type and doesn't explicitly convey a dependency like "Successor" or "Predecessor." "From itemA, open the Links tab, and then select Add link. Set Link type to References and add the ID of itemB" is incorrect because while the location is correct, "References" is too generic. "Successor" specifically denotes the dependency.
Pass your exam — without the endless answer hunt
Get every verified question and explanation for this exam in one place, and save hours of prep. 1,000+ certifications · 20+ languages · free to start.
Pass your exam faster → No card needed