Cisco 350-901 Exam - Topic 5 Question 91 Discussion

Actual exam question for Cisco's 350-901 exam

Question #: 91
Topic #: 5

A developer is working on a new feature in a branch named 'newfeay000222118' and the current working primary branch is named 'pnm409024967' The developer requires a merge commit during a fast forward merge for record-keeping purposes. Which Git command must Be used?

AOption A

BOption B

COption C

DOption D

Show Suggested Answer

Suggested Answer: B

by Miesha at Feb 10, 2025, 02:02 PM

Limited Time Offer

25%

Off

Get Premium 350-901 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Trinidad

9 months ago

I didn't know you could force a merge commit like that!

upvoted 0 times

...

Georgeanna

9 months ago

Yup, that's correct! It's all about keeping the history clear.

upvoted 0 times

...

Evelynn

10 months ago

Wait, are you sure about that? I thought fast-forward merges didn't create merge commits.

upvoted 0 times

...

Jennifer

10 months ago

Totally agree, that's the way to go!

upvoted 0 times

...

Von

10 months ago

You need to use `git merge --no-ff` for a merge commit.

upvoted 0 times

...

Melinda

10 months ago

I think it might be option C, but I need to double-check if it includes the `--no-ff` flag for the merge commit.

upvoted 0 times

...

Lawrence

11 months ago

I feel like one of the options has the right command, but I can't remember if it's `git merge` or something else entirely.

upvoted 0 times

...

Lashawnda

11 months ago

I remember practicing a question about merging branches, and it was something like `git merge --no-ff`, but I can't recall the exact syntax.

upvoted 0 times

...

Lachelle

11 months ago

I think we need to use the `--no-ff` option for the merge to create a merge commit, but I'm not entirely sure which command that applies to.

upvoted 0 times

...

Benedict

11 months ago

This is a good test of my Git knowledge. I'll carefully consider each option and try to apply my understanding of merge behavior to select the correct command.

upvoted 0 times

...

Renea

11 months ago

I'm a bit confused by the different branch names and the specific requirement for a merge commit. I'll need to double-check my understanding of Git merge strategies.

upvoted 0 times

...

Claribel

11 months ago

Okay, I think I've got it. Based on the branch names and the need for a merge commit, I'm going to go with Option C.

upvoted 0 times

...

Weldon

11 months ago

Hmm, the requirement for a merge commit during a fast-forward merge is throwing me off. I'll have to review the Git documentation on that scenario.

upvoted 0 times

...

Augustine

11 months ago

This looks like a tricky Git question. I'll need to think through the different merge options carefully to determine the right command.

upvoted 0 times

...

Sabine

1 year ago

Option C for the win! I'm just impressed the developer is even using Git branches, to be honest. Most of the time, they just push straight to master and call it a day.

upvoted 0 times

Minna

1 year ago

Option C is definitely the way to go for the merge commit.

upvoted 0 times

...

Shelton

1 year ago

Yes, it's important for code organization and collaboration.

upvoted 0 times

...

Glen

1 year ago

I agree, using branches shows good development practice.

upvoted 0 times

...

Jose

1 year ago

Ah, the old 'I want the best of both worlds' problem. Option C is the way to go, though I'm still trying to figure out why anyone would want a merge commit in a fast forward scenario. Must be a developer thing.

upvoted 0 times

Jacquelyne

1 year ago

Yeah, it's definitely a developer thing to want a merge commit in a fast forward merge.

upvoted 0 times

...

Linn

1 year ago

I agree, Option C is the best choice here.

upvoted 0 times

...

Tom

1 year ago

Why do you think Option D is the correct answer?

upvoted 0 times

...

Bulah

1 year ago

Wait, what? A fast forward merge and a merge commit? That's like saying 'I want to run fast, but I also want to take the stairs.' Option C is the only one that makes sense here.

upvoted 0 times

...

Mertie

1 year ago

I disagree, I believe the correct answer is Option D.

upvoted 0 times

...

Ernest

1 year ago

Option C looks like the correct answer. The question specifically states that the developer requires a merge commit during a fast forward merge, and Option C shows the git merge command with the --no-ff flag, which creates a merge commit even in a fast forward scenario.

upvoted 0 times