Q: 3
HOTSPOT Your company is building a new web application. You plan to collect feedback from pilot users on the features being delivered. All the pilot users have a corporate computer that has Google Chrome and the Microsoft Test & Feedback extension installed. Thepilot users will test the application by using Chrome. You need to identify which access levels are required to ensure that developers can request and gather feedback from the pilot users. The solution must use the principle of least privilege. Which access levels m Azure DevOps should you identify? To answer, select the appropriate options in the answer area NOTE: Each correct selection is worth one point. 
Your Answer
Discussion
Basic for both. Saw this trap on a similar question where Stakeholder looks ok for pilot users, but with the Chrome extension and full feedback workflow, they also need Basic. I think that's right here but open to discussion.
Extension in Connected mode flips it, so both need Basic access.
Basic for both roles here.
Why not Stakeholder for pilot users? The extension in connected mode seems to require Basic, Stakeholder is a trap here.
Basic for both roles. Not certain if Stakeholder could ever work for the extension, but here Basic fits the least privilege requirement.
Stakeholder for pilot users should be enough. Saw something similar on an official practice test and docs.
Basic for both developer and pilot user is my pick here. The Test & Feedback extension in connected mode cuts off the Stakeholder access workaround, so Basic is the minimum needed. Pretty sure that's in line with least privilege for this scenario. Let me know if I missed something.
Not sure I'd pick Basic for the pilot users, Stakeholder seems like a trap here since it's almost enough for feedback.
Is Stakeholder for pilot users not enough in this scenario since they're just giving feedback, or is Basic still required here?
I think both should have Basic. Stakeholder is too limited for collecting feedback via the extension.
Be respectful. No spam.
