Which statement describes a Recursive Merge?

Which statement describes a Recursive Merge?

• A. A fast-forward merge that simply moves the tip forward
• B. A rebase operation that rewrites history
• C. A merge that discards the other branch
• D. A merge that creates a new commit combining changes from both branches

Answer: (D)

A recursive merge in Git is the process of combining two diverged branches by using a common ancestor to perform a three-way merge, resulting in a new merge commit that records the changes from both branches and preserves both histories. This is why the description of creating a new commit that brings together the changes from both sides is the best match—the merge commit serves as a tangible record of how the two branches were integrated. The other scenarios describe different operations: a fast-forward merge merely moves the current branch pointer to the tip of the other branch with no merge commit; a rebase rewrites history by replaying commits onto a new base; and a merge that discards the other branch isn’t really merging at all.

A recursive merge in Git is the process of combining two diverged branches by using a common ancestor to perform a three-way merge, resulting in a new merge commit that records the changes from both branches and preserves both histories. This is why the description of creating a new commit that brings together the changes from both sides is the best match—the merge commit serves as a tangible record of how the two branches were integrated. The other scenarios describe different operations: a fast-forward merge merely moves the current branch pointer to the tip of the other branch with no merge commit; a rebase rewrites history by replaying commits onto a new base; and a merge that discards the other branch isn’t really merging at all.