AZ-400 Question 237
Single answerYou have two new team members: a non-technical stakeholder who needs to view project status and work items in Azure DevOps, and an external developer who needs to collaborate on your private GitHub repository by submitting pull requests. You want to ensure both have only the necessary privileges. Which approach should you recommend?
- A
Provide the non-technical stakeholder with Contributor access in Azure DevOps and assign the external developer as an Admin on the GitHub repository.
- B
Provide the non-technical stakeholder with Stakeholder access in Azure DevOps and grant the external developer read-only access in the GitHub repository.
- C
Provide the non-technical stakeholder with Stakeholder access in Azure DevOps and grant the external developer outside collaborator access with Write permissions in the GitHub repository.
- D
Provide the non-technical stakeholder with Basic access in Azure DevOps and assign the external developer as a GitHub Owner under the organization's repository.
Show answer and explanation
Correct answer: C
Explanation
Stakeholder access in Azure DevOps is designed for those who need to track work items and project status without contributing code or using advanced features. Outside collaborator access with Write permissions in GitHub allows external developers to clone, push feature branches, and submit pull requests while limiting administrative privileges. For more details, refer to Microsoft documentation on Azure DevOps access levels (docs.microsoft.com/en-us/azure/devops/organizations/security/access-levels) and GitHub� documentation on repository permissions for outside collaborators (docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization).
- A. Incorrect.
Option 1: Incorrect. Contributor access in Azure DevOps is unnecessary for a non-technical stakeholder who only needs to track progress. Also, giving the external developer Admin rights in GitHub grants more permissions than required, such as repository settings modification.
- B. Incorrect.
Option 2: Incorrect. While Stakeholder access in Azure DevOps is suitable for a non-technical stakeholder, providing read-only access in GitHub to the external developer prevents them from pushing branches or submitting pull requests, which they need to do.
- C. Correct.
Option 3: Correct. Stakeholder access in Azure DevOps allows a non-technical stakeholder to view work items and project status without additional privileges. An outside collaborator role with Write permissions in GitHub gives the external developer the ability to submit pull requests and push feature branches without granting administrative access.
- D. Incorrect.
Option 4: Incorrect. Basic access in Azure DevOps grants more permissions than required for a purely non-technical stakeholder, and making the external developer a GitHub Owner grants elevated privileges across the repository, including member management and repository settings changes.