Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco 350-901 Exam - Topic 5 Question 91 Discussion

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

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?

A)

B)

C)

D)

Suggested Answer: B

Get Premium 350-901 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
30 comments · newest first
TR
Trinidad 11 months ago
I didn't know you could force a merge commit like that!
GE
Georgeanna 11 months ago
Yup, that's correct! It's all about keeping the history clear.
EV
Evelynn 11 months ago
Wait, are you sure about that? I thought fast-forward merges didn't create merge commits.
JE
Jennifer 11 months ago
Totally agree, that's the way to go!
VO
Von 12 months ago
You need to use `git merge --no-ff` for a merge commit.
ME
Melinda 12 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.
LA
Lawrence 1 year 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.
LA
Lashawnda 1 year 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.
LA
Lachelle 1 year 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.
BE
Benedict 1 year 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.
RE
Renea 1 year 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.
CL
Claribel 1 year 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.
WE
Weldon 1 year 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.
AU
Augustine 1 year ago
This looks like a tricky Git question. I'll need to think through the different merge options carefully to determine the right command.
SA
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.
MI
Minna 1 year ago
↳ replying to Sabine
Option C is definitely the way to go for the merge commit.
SH
Shelton 1 year ago
↳ replying to Sabine
Yes, it's important for code organization and collaboration.
GL
Glen 1 year ago
↳ replying to Sabine
I agree, using branches shows good development practice.
JO
Jose 2 years 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.
JA
Jacquelyne 1 year ago
↳ replying to Jose
Yeah, it's definitely a developer thing to want a merge commit in a fast forward merge.
LI
Linn 1 year ago
↳ replying to Jose
I agree, Option C is the best choice here.
TO
Tom 2 years ago
Why do you think Option D is the correct answer?
BU
Bulah 2 years 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.
ME
Mertie 2 years ago
I disagree, I believe the correct answer is Option D.
ER
Ernest 2 years 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.
EV
Eveline 1 year ago
↳ replying to Ernest
Good choice, Option C it is.
AM
Amber 1 year ago
↳ replying to Ernest
Let's go with Option C then.
KI
Kina 1 year ago
↳ replying to Ernest
I disagree, Option C is the correct answer.
IL
Iluminada 1 year ago
↳ replying to Ernest
I think Option A might work too.
TO
Tom 2 years ago
I think the answer is Option C.
0/2000 characters

Save Cancel