Q: 9
DRAG DROP You have a protect in Azure DevOps. You need to associate an automated testto a test case. Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. 
Drag & Drop
Discussion
Create a test project → Check in the project to Azure DevOps → Add the automated test to a build pipeline.
Create a test project → Check in the project → Add the automated test to a build pipeline. Had something like this in a mock and this order matched their process, pretty sure that's it.
Nah, 'Create a work item' is the trick-they throw that in on purpose but it's not needed for associating automated tests. You need to create the test project, check it into your DevOps repo, then hook it up in the build pipeline. Seen this order on similar exam dumps.
Create a test project → Check in to Azure DevOps → Add to build pipeline. I don't think 'Create a work item' is needed here, that's a classic distractor on similar exam questions.
Create a work item → Create a test project → Add the automated test to a build pipeline. I think starting with the work item makes sense since you usually plan/tests before building them out, even if that's a bit of a trap here.
Not sure-I'd start with 'Create a work item' before the test project, then check in, then add the test. The work item feels like a common real-world first step even if it usually isn't needed here.
Create a test project → Check in the project → Add to build pipeline. Not 100% but that matches how automated tests get associated from what I've seen.
Create a work item → Create a test project → Check in a project to the Azure DevOps repo. I thought you always start by tracking requirements, so work item first makes sense to me. Then set up the test project, and commit it for version control. Maybe not perfect but matches how I'd see it in practice exams or the official guide. If someone disagrees let me know.
Always frustrating-I'd map it as Create a work item, Create a test project, Check in to repo.
Be respectful. No spam.