Accenture · Git & Version Control

Accenture Git & Version Control interview questions

Practice Git & Version Control questions specifically asked in Accenture interviews – ideal for online test preparation, technical rounds and final HR discussions.

Company: AccentureSubject: Git & Version Control51 questions in this page

Quick overview

Questions

Tagged for this company + subject

Company

Accenture

View company-wise questions

Subject

Git & Version Control

Explore topic-wise practice

Accenture · Git & Version Control questions (51)

Go through each question and its explanation. Use this page for targeted revision just before your Accenture Git & Version Control round.

Back to Accenture page•View all Git & Version Control questions

1. What is `git reflog` and when is it indispensable?

Difficulty: MediumType: SubjectiveTopic: Reflog

Reflog records movements of HEAD and refs (even orphaned). It’s crucial for recovering "lost" commits after resets/rebases or branch deletions.

2. How do you find a commit by message and then show its patch?

Difficulty: Medium

Continue your preparation

For complete preparation, combine this company + subject page with full company-wise practice and subject-wise practice. You can also explore other companies and topics from the links below.

Quick navigation:Accenture company page•Git & Version Control subject page•All companies•All subjects

Master Interviews Anywhere, Anytime

Accenture Git & Version Control interview questions

Quick overview

1. What is `git reflog` and when is it indispensable?

2. How do you find a commit by message and then show its patch?

Continue your preparation

3. You checked out a commit SHA directly. Which is TRUE?

4. A team wants one commit per PR on main. Which setting fits best?

5. Which is a safe scenario for interactive rebase?

6. What is the purpose of a CODEOWNERS file?

7. Which option reduces the risk when force-pushing rewritten history?

8. What is a repository in Git? Differentiate local and remote repositories.

9. What is the typical order for recording changes?

10. Define a commit in Git. Why are commit messages important?

11. What is a merge conflict and how do you resolve it?

12. Which command uses the modern syntax to create and switch to a branch named `feature/api`?

13. Contrast `git rebase` and `git merge` in collaboration. Mention risks and best practices.

14. Your new branch `bugfix/typo` has no upstream. What sets it and pushes once?

15. Give two `git log` flags useful during reviews and explain them.

16. You forgot to include one file in the last commit. Which sequence is correct?

17. Explain `git commit --fixup` and `git rebase --autosquash` workflow.

18. Which command changes the URL of the existing 'origin' remote?

19. Which command pushes all local tags to the `origin` remote?

20. What is a Git submodule and how do you initialize and update them after cloning?

21. Explain `git restore` and `git restore --staged` as modern replacements for older patterns.

22. Which statement about merge vs rebase is MOST accurate?

23. Why is it unsafe to rebase public branches and when is it acceptable?

24. You accidentally finished a destructive rebase. How do you recover your previous branch state?

25. Which command moves HEAD and updates the index but leaves the working tree unchanged?

26. Why use `git merge --no-ff` on a feature branch?

27. Main has moved ahead. Show two safe ways to bring a feature branch up to date and discuss trade-offs.

28. Which command sets the upstream branch so `git pull` knows the remote to track?

29. List good reviewer behaviors in PRs.

30. Describe a pragmatic branching model for a product team shipping weekly (branches, integration, release).

31. Which command saves tracked modifications and clears your working tree?

32. How do you stash tracked, untracked, and ignored files?

33. You want to stash only parts of files. Which command helps?

34. How do you clean ignored files (e.g., build artifacts) as well?

35. When should you open a Draft PR?

36. How do you configure `git pull` to rebase by default for the current repo?

37. When is `git cherry-pick` preferred over merging a whole branch?

38. Which flag adds a Signed-off-by trailer while cherry-picking?

39. Which command creates an annotated tag named v1.2.0 with a message?

40. In Semantic Versioning MAJOR.MINOR.PATCH, which increment signals backward-incompatible changes?

41. How would you design a tagging strategy for a service with weekly releases, hotfixes, and experimental builds?

42. Which settings best protect the main branch in a collaborative repo?

43. How should you respond when you disagree with a reviewer’s suggestion?

44. What is one proven tactic to reduce back-and-forth in reviews?

45. You want to nudge developers to submit smaller PRs. What’s a practical step?

46. Which command stages all modified and deleted files but not untracked files?

47. Which command deletes a branch named `feature/login` on the `origin` remote?

48. What is the effect of using a platform’s “Squash and merge” option on a PR?

49. Which command both creates a new branch and switches to it (modern syntax)?

50. Which statement best describes GitHub Flow?

51. You want CI to cut a PATCH release on every merged hotfix PR. Which approach is most appropriate?

Master Interviews
Anywhere, Anytime