Exam AZ-400 All Questions

View all questions & answers for the AZ-400 exam

Exam AZ-400 topic 7 question 28 discussion

Actual exam question from Microsoft's AZ-400

Question #: 28
Topic #: 7

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
Your company uses Azure DevOps to manage the build and release processes for applications.
You use a Git repository for applications source control.
You need to implement a pull request strategy that reduces the history volume in the master branch.
Solution: You implement a pull request strategy that uses fast-forward merges.
Does this meet the goal?

A. Yes
B. No

Show Suggested Answer

Suggested Answer: B 🗳️

by fallenDaffy at Sept. 4, 2020, 10:04 a.m.

Comments

Submit Cancel

fallenDaffy

Highly Voted 4 years, 11 months ago

Should be No. Squash merge - creates a linear history with a single commit in the target branch with the changes from the source branch.

upvoted 63 times

...

JimmyC

Highly Voted 4 years, 3 months ago

I would argue that this answer is correct (keep in mind that these yes/no questions can have more than one Yes answer). Squash merge is also correct. However fast-forward merging does reduce the main branch history size, by not adding the merge itself into the history. Squash merging is a much better answer, but as the question is written, this answer is 100% correct.

upvoted 19 times

kennynelcon

3 years ago

--ff merges the commit history of the source branch when the pull request closes and creates a merge commitin the target branch, and that is not in line with the question. So maybe we can say it is wrong ?

upvoted 1 times

...

GPRai

Most Recent 1 year, 1 month ago

Selected Answer: B

It should be Squash Merge

upvoted 1 times

...

ozbonny

1 year, 5 months ago

Selected Answer: B

Should be B. No

upvoted 1 times

...

ServerBrain

1 year, 7 months ago

Selected Answer: B

Question: 'a pull request strategy that reduces the history volume' Best Answer: Squash merge..

upvoted 1 times

...

vsvaid

1 year, 7 months ago

Selected Answer: B

No for me

upvoted 1 times

...

yana_b

1 year, 9 months ago

Selected Answer: B

The proper solution is squash merge -> see link https://learn.microsoft.com/en-us/azure/devops/repos/git/branch-policies?view=azure-devops&tabs=browser Basic merge (no fast-forward) creates a merge commit in the target whose parents are the target and source branches. Squash merge creates a linear history with a single commit in the target branch with the changes from the source branch. Learn more about squash merging and how it affects branch history. Rebase and fast-forward creates a linear history by replaying source commits onto the target branch with no merge commit. Rebase with merge commit replays the source commits onto the target and also creates a merge commit.

upvoted 1 times

...

xRiot007

2 years ago

We want to reduce the history volume, so SQUASH merge, not rebase. Also, in real life project, please do not use rebase, you will screw the history and nobody will understand anything anymore. At most you should use squash to condense things, but that's about it.

upvoted 1 times

...

MohmmadFayez

2 years, 11 months ago

There is No "Fast Forward merge" on azure repo Azure repo has 4 merge option : 1) Basic (no fast forward) 2Squatch 3) rebase with fast forward 4) rebase with merge commit As i think the correct options which meet the rquirment here is - sqatch And - rebase with fast forward

upvoted 2 times

...

syu31svc

2 years, 12 months ago

Selected Answer: B

https://docs.microsoft.com/en-us/azure/devops/repos/git/merging-with-squash?view=azure-devops "Squash merging is a merge option that allows you to condense the Git history" Answer is No

upvoted 1 times

...

UnknowMan

3 years, 2 months ago

Selected Answer: B

Squash is a better solution

upvoted 1 times

...

rdemontis

3 years, 4 months ago

Selected Answer: B

answer is No, you need to use squash merge to condensate history

upvoted 1 times

...

cirojascr

3 years, 6 months ago

Selected Answer: B

fast forward takes all the commit messages

upvoted 1 times

...

Art3

3 years, 6 months ago

No is correct answer.

upvoted 2 times

...

Ycombo

3 years, 7 months ago

Selected Answer: B

It should be no. Squash merge is more appropriate.

upvoted 2 times

...

erickim007

4 years, 1 month ago

the answer should be no.

upvoted 1 times

...

monniq

4 years, 2 months ago

The provided answer contradicts with the explanation in MSDN. "Rebase and fast-forward - creates a linear history by replaying source commits onto the target branch with no merge commit." I'd go with 'No'.

upvoted 2 times

...

Load full discussion...