ExamTopics Logo
Mail Us[email protected]
Menu
Microsoft Discussions
exam questions

Exam AZ-400 All Questions

View all questions & answers for the AZ-400 exam
Go to Exam

Exam AZ-400 topic 4 question 12 discussion

Actual exam question from Microsoft's AZ-400
Question #: 12
Topic #: 4
[All AZ-400 Questions]

You have a branch policy in a project in Azure DevOps. The policy requires that code always builds successfully.
You need to ensure that a specific user can always merge changes to the master branch, even if the code fails to compile. The solution must use the principle of least privilege.
What should you do?

  • A. Add the user to the Build Administrators group.
  • B. Add the user to the Project Administrators group.
  • C. From the Security settings of the repository, modify the access control for the user.
  • D. From the Security settings of the branch, modify the access control for the user.
Show Suggested Answer Hide Answer
Suggested Answer: D 🗳️
by AS007 at May 15, 2020, 1:59 a.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
examkid
Highly Voted 4 years, 9 months ago
What a horrible scenario! Anyway the answer is correct
upvoted 40 times
Dankho
4 months, 4 weeks ago
So true!
upvoted 1 times
...
ManikandaKumaran
3 years, 6 months ago
Sometimes in real time, these are valid scenarios. Some development repos won't have customer's third-party integrated software's db access. At those times developers can't compile but still need to port the changes.
upvoted 4 times
...
Dkijc
4 years, 7 months ago
I know, right? lol
upvoted 3 times
d0bermannn
3 years, 8 months ago
yes that q is about our honorable code stars))
upvoted 1 times
...
...
...
AS007
Highly Voted 5 years ago
Correct Answer
upvoted 36 times
...
Dankho
Most Recent 5 months, 4 weeks ago
Selected Answer: D
" even if the code fails to compile"??? what kind of a shop is this?
upvoted 2 times
...
UrbanRellik
1 year ago
Selected Answer: D
Although it's not recommended to allow a failed build to merge with the master branch, D will allow you to have granular control over each user's privileges.
upvoted 1 times
...
jmglezgz
1 year, 1 month ago
Selected Answer: D
From the Security settings of the branch, modify the access control for the user.
upvoted 1 times
...
vsvaid
1 year, 5 months ago
Selected Answer: D
Correct answer
upvoted 1 times
...
flafernan
1 year, 8 months ago
I accepted but I don't agree with the question. The question said a specific user and I understood that it would not be the same user. Therefore, it would not be modified but rather add a new user. I also add a comment that this would not be a good practice in DevOps. Very strange question.
upvoted 1 times
...
yana_b
1 year, 9 months ago
Selected Answer: D
Correct answer
upvoted 1 times
...
xRiot007
1 year, 10 months ago
Hello Microsoft, why would you want to do this in the first place ? This is against the best practices of DevOps.
upvoted 3 times
DiligentAmoeba
1 year, 9 months ago
Agree, access should be granted to a group, of which the user is a member.
upvoted 1 times
...
...
renzoku
1 year, 10 months ago
Selected Answer: D
D: From the Security settings of the branch, modify the access control for the user. By modifying the access control you can grant them the necessary permissions to bypass the policy in the specific branch. Modify access control at repository scope, break the rule to use the principle of least privilege. Build Administrators group, Project Administrators group Grant permissions to view, managing or building pipelines and related funtionalities.
upvoted 1 times
...
syu31svc
2 years, 9 months ago
Selected Answer: D
https://docs.microsoft.com/en-us/azure/devops/repos/git/branch-permissions?view=azure-devops "Users with this permission are exempt from the branch policy set for the branch when completing pull requests and can opt-in to override the policies by checking Override branch policies and enable merge when completing a PR." Answer is D
upvoted 3 times
...
Govcomm
2 years, 10 months ago
From the Security settings of the branch, modify the access control for the user.
upvoted 1 times
...
Kalaismile06
2 years, 11 months ago
Given answer is correct
upvoted 1 times
...
UnknowMan
3 years ago
Because if for a specific "master branch", we user Branch security level and not Repository security level (that set for all branche) Correct answer
upvoted 3 times
...
rdemontis
3 years, 2 months ago
Selected Answer: D
answer is correct as documentation provided demonstrate
upvoted 2 times
rdemontis
3 years, 1 month ago
https://docs.microsoft.com/en-us/azure/devops/repos/git/branch-policies?view=azure-devops&tabs=browser#bypass-branch-policies
upvoted 1 times
...
...
Pino2012
4 years, 3 months ago
Why do you want to do this? It makes no sense.
upvoted 3 times
tom999
4 years, 3 months ago
Agreed. But for the given requirements the answer is right though: D "From the Security settings of the branch, modify the access control for the user. "
upvoted 4 times
...
...
aftab7500
4 years, 6 months ago
If you want to bypass branch policies which are already in place. Go to security setting to change them.
upvoted 2 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel