DRAG DROP You have a project in Azure DevOps named Project1 that has a release pipeline in Azure Pipeline named ReleaseP1. you need toensure that when a new release is generated for ReleaseP1, a new release note document is created. The release notes must contain new features and bug fixes. Which three actions should you perform in sequence? To answer, move the appropriate actions from the Most of actions to the answer area and arrange them r the correct order. NOTE: More than one order of answer choices is correct You will receive credit for any of the correct orders you select 
Yeah, dashboard widget first (to fetch info), then create PAT so the script can access the data, and finish by adding a PowerShell task to actually build the markdown file. Pretty sure that covers the release note workflow here. If anyone thinks using the query step changes things let me know.
Tricky detail here: you actually need to create the query first (to define what counts as features/bugs), then set up a PAT for script auth, and last add the PowerShell task. Widget isn’t for outputting to markdown. Query -> PAT -> PowerShell task is the sequence I’ve seen in labs. If someone got it working by starting with the widget let me know, but pretty sure this is it.
Pretty sure the right flow is: Create a query to get new features and bug fixes, then generate a PAT so the script can authenticate, then add a PowerShell task in ReleaseP1 to write it all out as markdown. This matches how release notes are typically automated. Let me know if you see it differently!
- Create a query for features/bugs
- Create PAT
- Create PowerShell task to write markdown file
Widget as first step looks right to me-seems like the intention is to fetch and show info before automating the file creation. PAT then script after makes sense if you want it all connected. I might be missing a trick with the query step but this way lines up with similar practice tests. Maybe the widget is a trap but I think this order works. Agree?
