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 Exam 350-901 Topic 5 Question 91 Discussion

Actual exam question for Cisco's 350-901 exam
Question #: 91
Topic #: 5
[All 350-901 Questions]

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)

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Sabine
2 months 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
13 days ago
Option C is definitely the way to go for the merge commit.
upvoted 0 times
...
Shelton
22 days ago
Yes, it's important for code organization and collaboration.
upvoted 0 times
...
Glen
1 months ago
I agree, using branches shows good development practice.
upvoted 0 times
...
...
Jose
2 months 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
2 months ago
Yeah, it's definitely a developer thing to want a merge commit in a fast forward merge.
upvoted 0 times
...
Linn
2 months ago
I agree, Option C is the best choice here.
upvoted 0 times
...
...
Tom
2 months ago
Why do you think Option D is the correct answer?
upvoted 0 times
...
Bulah
2 months 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
2 months ago
I disagree, I believe the correct answer is Option D.
upvoted 0 times
...
Ernest
2 months 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
Eveline
1 months ago
Good choice, Option C it is.
upvoted 0 times
...
Amber
2 months ago
Let's go with Option C then.
upvoted 0 times
...
Kina
2 months ago
I disagree, Option C is the correct answer.
upvoted 0 times
...
Iluminada
2 months ago
I think Option A might work too.
upvoted 0 times
...
...
Tom
2 months ago
I think the answer is Option C.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77