Git Test

How can you check your current git version?

GIT --OPTIONS

GIT --VERSION

GIT --CURRENT

GIT --V

What command lets you create a connection between a local and remote repository?

GIT REMOTE ADD ORIGIN

GIT REMOTE ADD NEW

GIT REMOTE NEW ORIGIN

GIT REMOTE ORIGIN

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 the beta branch. How can you accomplish this?

CHECKOUT THE PUSH-NOTIFICATIONS BRANCH AND RUN GIT MERGE BETA.

DELETE THE PUSH-NOTIFICATIONS BRANCH AND IT WILL BE COMMITTED TO THE MASTER BRANCH AUTOMATICALLY.

CHECKOUT THE BETA BRANCH AND RUN GIT MERGE PUSH-NOTIFICATIONS.

CHECKOUT THE MASTER BRANCH AND RUN GIT MERGE BETA -> PUSH-NOTIFICATIONS.

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

ALL NEW AND UPDATED FILES ARE STAGED

FILES ARE STAGED IN ALPHABETICAL ORDER.

ALL NEW FILES ARE STAGED

ONLY UPDATED FILES ARE STAGED

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

THE CURRENT GIT VERSION YOU'RE RUNNING

AN INLINE EDITOR FOR MODIFYING REMOTE REPOSITORIES

A LIST OF REMOTE REPOSITORIES YOU ARE CONNECTED TO

THE LAST 5 GIT VERSIONS YOU'VE INSTALLED

What does the following command do to the git repository history? git reset --soft HEAD^

UNDOES THE LAST COMMIT IN THE WORKING BRANCH AND SETS THE HEAD BACK ONE COMMIT.

DELETES ALL PREVIOUS COMMITS AND RESETS THE REPOSITORY HISTORY BACK TO ITS INITIAL STATE.

KEEPS THE HEAD AT THE CURRENT COMMIT, BUT CLEARS ALL PREVIOUS COMMITS.

RESETS THE WORKING BRANCH TO THE FIRST COMMIT.

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?

USE GIT BISECT TO COMPARE THE BUGGY COMMIT TO AN EARLY COMMIT THAT WORKS AS EXPECTED.

USE GIT SEARCH -DIFF TO COMPARE ALL COMMITS IN YOUR REPOSITORY HISTORY.

MANUALLY BACKTRACK THROUGH YOUR COMMIT HISTORY.

RUN A GIT REBASE TO FIND THE BUGGY COMMIT.

Why would the following command be used? git rebase -i HEAD~10

TO DELETE THE LAST 10 COMMITS AND RESETS THE HEAD

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

IN ORDER TO LOCALLY CACHE THE LAST 10 COMMITS

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

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

--ALL

--GLOBAL

--MASTER

--UPDATE

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

CACHING

REBASING

YOU CAN'T. GIT MERGE --SQUASH IS THE ONLY GIT COMMAND FOR THAT OPERATION.

REFLOGGING

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.

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?

RUN GIT COMMIT --INFO WITH THE COMMIT HASH.

ACCESS THE COMMIT STASH DATA WITH GIT STASH.

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

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

COMMITS ALL NEW FILES WITH A MESSAGE

ADDS ALL NEW FILES TO THE STAGING AREA

ADDS ALL MODIFIED FILES TO THE STAGING AREA, THEN COMMITS THEM WITH A MESSAGE

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

SAVED FILES

STAGING AREA

GIT DOCUMENTS

GIT CACHE

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

ALL FILES IN THE WORKING DIRECTORY ARE STAGED TO THE INDEX IN ALPHABETICAL ORDER.

ALL NEW AND UPDATED FILES FROM THE WORKING DIRECTORY ARE STAGED TO THE INDEX.

ONLY NEW FILES IN THE WORKING DIRECTORY ARE STAGED TO THE INDEX.

ONLY UPDATED FILES IN THE WORKING DIRECTORY ARE STAGED TO THE INDEX.

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 -VERBOSE

GIT REBASE -I

GIT REBASE -ALL

GIT REBASE -LOG

Take a look at the git commands below and determine what the operation is doing?

IT IDENTIFIES 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.

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.

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 UNDER A NEW HASH.

STASH THE RELATED COMMITS UNDER A NEW HASH.

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.

Which statement is true of the git push command?

TAGS ARE PUSHED TO THE REMOTE REPOSITORY WITH THEIR RESPECTIVE COMMITS.

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.

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

GIT PUSH -U ORIGIN MASTER

GIT PUSH

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.

What command would let you modify your previous commit?

- - FIX

- - QUICKFIX

- - MODIFY

- - AMEND

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

DATA ARRAY

DATA LOG

DATA SNAPSHOT

DATA DICTIONARY

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.

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

USE 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.

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 THIS 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.

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?

USE GIT STASH TO SAVE YOUR WORK, THEN COME BACK LATER AND REAPPLY THE STASHED COMMIT.

SAVE YOUR WORK WITH GIT LOCAL-CACHE.

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

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

GIT START

GIT ADD

GIT INIT

GIT NEW

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?

RERERE.ENABLED ISN'T ENABLED IN THE CONFIG FILE.

THE FILEPATH ISN'T SPECIFIED.

THE COMMIT HASH IS MISSING.

THE -ALL OPTION ISN'T ADDED TO THE COMMAND.

Your Name: (required)
Your Email: (required)
Skype Username:
Exams you want to pass:

Exam Type:	Git MCQ Skill Test
Questions Type:	Multiple Choice Questions
Total Questions:	31
Time Limit:	30 Minutes
Last Update	June, 2025

Pass Git Exam

Git Quiz