Git MCQ: Git Multiple Choice Questions and Answers

Git MCQ with answers and explanations for placement tests and job interviews. These solved Git MCQ are useful for the campus placement for all freshers including Engineering Students, MCA students, Computer and IT Engineers, etc.

Our Git MCQ ( Git Multiple Choice Questions and Answer ) focuses on all areas of Git software. We will also regularly update the Git MCQ and the most interesting thing is that questions come in a random sequence. So every time you will feel new questions.

Note: Your score along with correct answers will be visible after answering all of these questions.

So let’s see our Git MCQ (Multiple Choice Questions & Answers on “Git”)

Git MCQ: Git Multiple Choice Questions and Answers

1 / 90

What commands would you use to force an overwrite of your local files with the master branch?

git pull --all git reset --hard origin/master

git pull -u origin master git reset --hard master

git pull origin master git reset --hard origin/myCurrentBranch

git fetch --all git reset --hard origin/master

2 / 90

Which use case is NOT a good candidate for a Git hook?

state dependent environment changes

continuous integration

increasing code coverage

enforcing commit rules

3 / 90

Which of the following is true you when you use the following command?

git add -A

x All new and updated files are staged

Files are staged in alphabetical order.

All new files are staged

Only updated files are staged

4 / 90

What is the difference between using the git stash and git stash pop commands?

git stash removes a commit from the repo history, while git stash pop saves changes to multiple branches.

git stash saves changes to multiple branches, while git stash pop removes a commit from the repo history.

git stash removes the most recent commit, while git stash pop saves current changes.

git stash creates a stash entry, while git stash pop places the saved state onto the working directory.

5 / 90

After starting to work on a new feature and creating new files in the working directory related to it, the customer determinded the feature was no longer required. What command can be used to remove the untracked files from the working directory ?

git clean -f

git rm .

git reset HEAD

git checkout .

6 / 90

If you have several commits for a single feature, what is the most efficient way to restructure your commit history?

Use git stash to consolidate the commits under a new hash.

Use git squash to consolidate the commits together into a single coherent commit.

Delete the task commits and recommit with a new message.

Use git cherry-pick to place the commits in another branch.

7 / 90

This command is an example of what kind of tag ?

git tag -a v1.4 -m "ABCD v1.5"

verbose

annotated

lightweight

deferred

8 / 90

You're in the middle of modifying a file when you're unexpectedly assigned an urgent bug fix on another branch. What would you do to temporarily save the work your doing locally without committing?

You cannot save locally without committing, so that is not possible.

Run git hold to save a local copy of what you're doing to return to later.

Save your work with git local-cache.

Use git stash to save your work and come back later and reapply the stashed commit.

9 / 90

What files is this .gitignore programmed to leave out?

#.swift
build/

*.txt
*.metadata

All files with a .swift, .txt, or metadata file extension, as well as the entire build directory

Only the build directory

All files in the build directory, as well as files ending with .txt or .metadata

Only files with .swift and .txt extensions.

10 / 90

. Which statement is true of the git push command?.

Commits can be tagged only when they are created.

By default a push doesn't send tags to the remote repository.

Only annotated tags are automatically pushed to the remote repository with a commit.

Tags are pushed to the remote repository with their respective commits.

11 / 90

Which statement is true when you use the git add -A command?

Only new files in the working directory are staged to the index.

All new and updated files from the working directory are staged to the index.

All files in the working directory are staged to the index in alphabetical order.

Only updated files in the working directory are staged to the index.

12 / 90

After starting to merge a feature branch into your master branch, you encounter a merge conflict and decide you do not want to perform the merge. How can you stop the merge and restore to the pre-merge state?

Use git restore -p.

se git merge -u.

Use git merge --abort.

Use git merge --undo.

13 / 90

Where are files stored before they are committed to the local repository ?

git

saved files

staging area/index

git documents

14 / 90

After you've successfully merged two branches and committed the changes, what is the next step in keeping your git structure organized?

Use the git reset --soft HEAD to roll back one commit.

Run git branch -d to delete the merged branch.

Use git clear-all to clean up any hanging files.

Run git rebase to move the current commit to its original location.

15 / 90

What is version control?

a type of architecture used to manage large databases

a system that shows, tracks, and controls changes to a set of files over time

a programmatic design pattern used to manage code between multiple engineering teams

a type of software that links a project with a GitHub repository

16 / 90

While modifying a file, you're unexpectedly assigned an urgent bug fix on another branch. How can you temporarily save your local work without committing?

Save your work with git local-cache.

Use git stash to save your work, then come back later and reapply the stashed commit.

Run git hold to save a local copy of what you're doing to return to later.

This is not possible, as you cannot save locally without committing.

17 / 90

How could you squash multiple commits together without using git merge --squash?

Caching

You can't. git merge --squash is the only git command for that operation.

Rebasing

Reflogging

18 / 90

Which of the following is true of the git push command?

By default a push doesn't send tags to the remote repository.

Commits can only be tagged when they are created.

Tags are pushed to the remote repository with their respective commits.

Only annotated tags are automatically pushed to the remote repository with a commit.

19 / 90

Your current project has several branches; master, beta, and push-notifications. You've just finished the notification feature in the push-notification branch, and you want to commit it to beta branch. How can you accomplish this?

Checkout the push-notifications branch and run git merge beta

Checkout the master branch and run git merge beta -> push-notification

Delete the push-notification branch and it will be committed to the master branch automatically

Checkout the beta branch and run git merge push-notification

20 / 90

What types of tags does Git support?

heavy and concise

lightweight and immutable

heavy and annotated

lightweight and annotated

21 / 90

What happens if you run this command from your master branch?

git checkout -b beta-test

The beta-test branch will be checked out of the current commit.

The beta-test branch will be checked out and deleted.

A new branch called beta-test will be created and switched to.

The beta-test branch will be merged with the master branch.

22 / 90

. How many ways are present in Git to integrate changes from one branch into another?

3

5

2

4

23 / 90

What does refs store?

SHA-1 value

None of these

Branch name

Project name

24 / 90

Where are files stored before they are committed to the local repository?

Saved files

git documents

Staging area

git cache

25 / 90

Your team lead needs a list of all commits that will be moved before you perform a rebase. Which command can you use to access that information?

git rebase -log

git rebase -i

git rebase -verbose

git rebase -all

26 / 90

What is the difference between Git and SVN?

Git works only on Linux, while SVN works on all operating systems.

SVN works only on Linux, while Git works on all operating systems.

SVN is a centralized system, while Git is a distributed system.

Git a centralized system, while SVN is a distributed system.

27 / 90

How would you delete unreachable objects older than a specified time from your project database?

git cache --obsolete

git branch --rebase

git delete --inert

git prune --expire

28 / 90

Which Git command begins tracking of a new file?

add

addfile

begin

track

29 / 90

Which command can be used to list the branches that have been merged into the currently checked-out branch?

git master --status

git branch --status

git branch --merged

git status --merged

30 / 90

What command would let you modify your previous commit?

--fix

--quickfix

--modify

--amend

31 / 90

What command creates a new branch from the currently checked-out branch?

git -b checkout

git branch

git checkout

git checkout -b

32 / 90

. After staging a series of changes to the index, which command could you use to review them prior to a commit?

git diff --cached

git diff

git diff --HEAD

git status -v -v

33 / 90

How many individual commits can a single repository have?

any number of commits

only one commit local per repository

only three commits per branch

only one commit per HEAD

34 / 90

What Git workflow is used by teams that collaborate on a single branch and avoid creating long-lived development branches?

Git flow

Mainline flow

Trunk-Based Development

GitHub flow

35 / 90

What is a remote repository?

a version of the repository that mirrors changes made in the local repository's master branch for open-source collaboration efforts

the lead repository elected by the Git arbitrator found within local repositories of collaborating team members

a read-only version of the repository stored on a backup server in case local repositories become lost or corrupted

a version of the repository hosted on the internet or network that is pushed to or pulled from by collaborators

36 / 90

Your current repository has three branches: master, beta and push-notifications. You've just finished the notification feature and commit the changes to the push-notifications branch, and you want to include them in the beta branch. How can you accomplish this?

Check out the master branch and run git merge beta -> push-notifications.

Delete the push-notifications branch; it will be committed to the master branch automatically.

Check out the push-notifications branch and run git merge beta.

Check out the beta branch and run git merge push-notifications.

37 / 90

You want to perform a git reset but cannot recall all of the available options. What command would you use to see a description of them?

git help reset

git -h reset

git options reset

git reset help

38 / 90

Which user should be created first during setting up of SSH?

git

admin

root

None of these

39 / 90

What Language is used in GIT?

C

C++

C#

Java

40 / 90

. What is the best way to characterize the git commit structure?

Data array

Data log

Data snapshot

Data dictionary

41 / 90

How does this command alter the currently checked-out branch?

git reset --soft HEAD^

It resets the working branch to the first commit.

It sets HEAD to previous commit and leaves changes from the undone commit in the stage/index.

It deletes all previous commits and resets the repository history back to its initial state.

It keeps the HEAD at the current commit, but clears all previous commits.

42 / 90

After you make changes to a tracked file, you run the following command. What will this do?

git commit -a -m "Refactor code base"

Nothing, you can't use multiple options in the same command

Adds all new files to the staging area

Commits all new files with a message

Adds all modified files to the staging area, then commits them with a message

43 / 90

How does Git think of its data?

File

None of these

Snapshot

Folder

44 / 90

Which option to git commit, will modify last commit message?

-replace

-change

-amend

-update

45 / 90

Why would you use a pre-receive hook in your remote repository?

You wouldn't, you would use it in the local repository

To execute a script when a remote receives a push that is triggered before any refs are updated

To fire a script after updates are made to the remote repository

To debug all commit tags and release versions

46 / 90

What does the git stash drop command do?

removes the most recent stash entry

deletes the stash

lists everything in the stash

throws away the oldest entry

47 / 90

What command would you use to create a new git repository?

git add

git start

git new

git init

48 / 90

How would you create a custom shortcut or command across your git environment?

Run git hotfix with the shortcut name.

Assign a shortcut or command using git options file.

Use the git custom-key command.

Create an alias in the git config file.

49 / 90

Which command gets a copy of an existing Git repository?

duplicate

replicate

copy

clone

50 / 90

What information does the git config file store?

shell scripts and flags

keychain and account information

local and global repository options

pre-compile scripts and settings

51 / 90

How would you configure Git to abort a commit if a smoke test script fails?

Create a post-commit shell script that triggers the action.

Create a post-commit hook to trigger the script.

Create a pre-commit hook to trigger the script.

Create a pre-commit shell script that triggers the action.

52 / 90

What change will the following command make to the staging area files?

git rm --cached testfile.js

testfile.js will be removed from the staging area and its changes no longer tracked.

testfile.js will be removed from the staging area but its changes will still be tracked.

A copy of testfile.js will be cached on your desktop.

The current copy of testfile.js will be saved in the staging area.

53 / 90

Which command correctly creates a lightweight tag?

git tag v3.8.1

git tag --light "v3.8.1"

git tag v3.8.1 —-annotate -m ""

git tag -l v3.8.1

54 / 90

You find a bug in your project, but can't locate where it was introduced in the commit history. How would you diagnose this problem?

Manually backtrack through your commit history.

Use git search -diff to compare all commits in your repository history.

Run a git rebase to find the buggy commit.

Use git bisect to compare the buggy commit to an early commit that works as expected.

55 / 90

After checking your git status you get the following output, which shows the file beta-notes.js in the commit but also unstaged. How can this situation occur?

Change to be committed:

(use "git reset HEAD <file>..." to unstage)
modified: beta-notes.js
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout --<file>..." to discard changes in working directory)

modified: beta-notes.js

There were two copies of beta-notes.js but one was deleted

beta-notes.js was staged, then modified afterwards, creating two different versions of the file

Two copies of beta-notes.js were created, but only one is being tracked

There are two tracked copies of beta-notes.js, but one was removed from the commit

56 / 90

What is the status of the beta-notes.js file in the following output?

Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)

modified: beta-notes.js

beta-notes.js is untracked and has been modified.

beta-notes.js is a tracked file and has been modified, but has not been added to the current commit.

beta-notes.js is untracked but has been added to the current commit.

beta-notes.js is tracked, and the modified file has been added to the current commit.

57 / 90

While working on a feature branch you try to use "git rerere" to solve a recurring merge conflict but nothing is happening. What could be causing this issue?

The "-all" option isn't added to the command.

"rerere.enabled" isn't enable in the config file.

The commit hash is missing.

The filepath isn't specified.

58 / 90

Which setting determines what pager is used when Git pages output?

core.page

page

pager

core.pager

59 / 90

Which command will list tags with the 1.4.2 series?

git tag 'v1.4.2'

git tag -I 'v1.4.2.*'

git tag-list 'v1.4.2*'

git tag 'v1.4.2*'

60 / 90

Why would the following command be used?

git rebase -i HEAD~10

To run a comparative search of the last 10 commits for differences

To list the last 10 commits and modify them with either the squash or fixup command

To delete the last 10 commits and reset the HEAD

In order to locally cache the last 10 commits

61 / 90

What is usually the extension of file which has the public key?

ssh

pub

key

pk

62 / 90

Which key press returns a set of suggestions to pick from, when writing a Git command?

Control

Shift

Tab

Alt

63 / 90

Which option on the git log command allows you to limit output to commits made after certain data?

--since

--sinceWhen

-

--afterDate

64 / 90

After pushing commits to the remote repository for the first time using the command below, what shorthand command can you use in future?

git push -u origin master

git push master

git push origin

Same as before, git push -u origin master

git push

65 / 90

What is the main issue with using git rebase when working with multiple developers?

Rebase affects only your repository and creates a diff in the master branch.

Rebase creates a temporary copy of the master branch in the remote repo.

Rebase moves the HEAD of the remote master branch one commit forward.

Rebase deletes all commit history for the new feature branch.

66 / 90

What is the difference between initializing a normal repo and a bare repo?

Bare repos store their git history in a .git subfolder.

Bare repos do not have the .git extension.

Bare repos do not come with working or checked-out source files.

Bare repos should be used for local rather than remote repos.

67 / 90

Which strategy is used by Git for merging two branches?

LIFO

recursive

FIFO

octopus

68 / 90

How can you check your current git version?

git --v

git --version

git --option

git --current

69 / 90

Which of the following is called dumb protocol?

All of these

SSH

Git

HTTP

70 / 90

What conflicts can occur when forcing a push after rebasing?

The remote master branch could have existing changes overwritten.

The origin URL will be reset to its default value.

The current HEAD will be deleted and can't be reinstated.

Nothing, it's common practice to force a push after rebasing.

71 / 90

Suppose you needed to see a list of all files that had been modified or added to a specific commit over the course of a project. How would you accomplish this?

Find the commit in the remote repository, as that's the only place that kind of information is stored.

Use the diff-tree command with the commit hash.

Run git commit --info with the commit hash.

Access the commit stash data with git stash.

72 / 90

Which version onwards did Git offer reversing a file back to what it looked like when last committed?

1.7

1.6

2.0

1.8

73 / 90

Which of these terms best describes Git?

Distributed Version Control System

Issue Tracking System

Integrated Development Environment

Web-Based Repository Hosting Service

74 / 90

Describe what the following git commands do to the commit history.

git reset --hard HEAD~5
git merge --squash HEAD@{1}

Reset the HEAD to the 5th commit in the repo, then merges to the master branch

Reset the commit branch back before the last 5 commits, then squashes them into a single commit

Delete the last 5 commits

Merges the last 5 commits into a new branch

75 / 90

You find that your project has a tag and branch both named push-notifications, which causes confusion when trying to print out given reference. How can you specify which branch you want to look at?

use git show refs/push-notifications

use git show push-notifications

use git show head/refs/push-notifications

use git show refs/head/push-notifications

76 / 90

What does commit object contain?

A set of files, representing the state of a project at a given point of time.

Reference to parent commit objects.

An SHA1 name, a 40-character string that uniquely identifies the commit object.

None of the above

77 / 90

What is the difference between a soft reset (git reset --soft) and a hard reset (git reset –hard) ?

A soft reset only changes the commit that HEAD points to, while a hard reset resets the index and working tree to match the specified commit, discarding any changes.

A soft reset caches the old HEAD pointer, while a hard reset deletes it entirely.

A hard reset changes only where the HEAD is pointing, while a soft reset changes the HEAD and index.

A hard reset caches the old HEAD pointer, while a soft reset deletes it entirely.

78 / 90

Which of the following is an integration manager?

lieutenants

benevolent dictator

Depends upon project type

Depends upon data

79 / 90

What will the following command print to the Terminal?
git remote -v

A list of remote repositories and their URLs

The current git version you're running

An inline editor for modifying remote repositories

The last 5 git versions you've installed

80 / 90

If you cloned an existing git repository, what would happen?

A new copy would overwrite the central repository

A copy of the repository would be created on your local machine

Nothing, cloning is not a supported git function

A copy of the repository would be created on the hosting platform

81 / 90

How does Git internally manage branches?

by creating a pointer to the most recent snapshot/commit for the branch.

by creating a data array of branches in the same repository.

by creating a data dictionary of code changes.

be creating a debug log that stores repository changes.

82 / 90

What is the operation doing given the Git commands below?
git bisect start
git bisect bad 5d41402abc4b2a76b9719d911017c592
git bisect good 69faab6268350295550de7d587bc323d

It runs a merge of a good commit that is discovered using a known bad commit and known good commit

It marks a commit for deletion using a known bad commit and known good commit to determine which commit introduced a bug

It defines a bad commit and resets the HEAD using a known bad commit and known good commit

It performs a binary search using a known bad commit and known good commit to determine which commit introduced a bug

83 / 90

Looking at the following commands, describe what is happening.

git checkout feature-user-location
git cherry-pick kj2342134sdf090093f0sdgasdf99sdfo992mmmf9921231

The commit is being tagged for release on the feature-user-location branch

A commit is being copied from its original branch over to the feature-user-location branch

The commit is being cherry picked as the new HEAD of the commit history

A commit is being copied from the feature-user-location branch to the master branch

The branch is switched to the feature-user-location branch, and the specified commit is applied to the branch.

84 / 90

What option can you use to apply git configurations across your entire git environment?

--all

--master

--global

--update

85 / 90

Which option enables inclusion of author name in custom log format?

%am

%ad

%ae

%an

86 / 90

In a situation where you have several commits for a single task, what is the most efficient way to restructure your commit history?

Cherry pick the related commits to another branch.

Delete the task commits and recommit with a new message.

Squash the related commits together into a single coherent commit.

Stash the related commits under a new hash.

87 / 90

. Which option enables inclusion of committer name in custom log format?

%ce

%cr

%cd

%cn

88 / 90

After modifying some existing files in a repository, you decide to discard the changes. What command can you use?

git restore

git undo

git clean

git checkout

89 / 90

After mistakenly staging a file named myFile to the index, how would you remove it from the index to exclude it from your next commit?

Use git reset HEAD^.

Use git reset myFile.txt.

Use git -rm myFile.txt.

Use git reset.

90 / 90

What does the following command do to the git repository?

git reset --soft HEAD^

It deletes all previous commits and reset the repository history back to its initial state.

It resets the working branch to the first commit.

It keeps the HEAD at the current commit, but clears all previous commits.

It sets HEAD to the previous commit and leaves changes from the undone commit in the stage/index.

Your score is
LinkedIn Facebook Twitter VKontakte

Git MCQ: Git Multiple Choice Questions and Answers

Which of the following is true you when you use the following command?

Recommended Articles for you: