Git - LinkedIn Skills Assessment Quiz with Answers | net world (2023)

Git

Q1 How can you check your current git version?

• git –v
• git-Version
• git - Option
• git -current

Q2. What command can you use to create a connection between a local and remote repository?

• re-add remote git
• Add remote git origin
• remote git new origin
• git Remote-What

The command is git remote add. The newly added connection can be labeled as source or new. The only caveat, although not documented AFAIK, is that the connection name must be acceptable to the git-check-ref format and cannot be repeated. If the LinkedIn review asks for it and you can only choose one option, please leave a comment.

Q3 Describe what the following Git commands do with the commit history.

git reset --hard HEAD~5git merge --squash[email protected]{1}

• Reverts HEAD to the fifth commit in the repository and then merges it into the master branch
• Roll back the commit branch before the last 5 commits, then squeeze them into a single commit
• Delete the last 5 commits
• Merge the last 5 commits into a new branch

Explanation:

• git reset --hardhead ~ 5resets the current branch to the commit just before the last 5 (seeman the git revisionfor details on this notation and other cool alternatives like[email protected]{2 days ago}). Since this is a hard reset, any changes in the working tree will also be overwritten. Seemann git-reset.
• git --squash-Kombination[email protected]{1} [email protected]{1} is where the branch was just before the previous command (again, seeman the git revision). This command sets the state of the index as it would be immediately after a merge of this commit. This whole operation could be a way to take 5 commits from a branch where you started a new feature and combine them into a single commit, a major one.

Q4 Your current project has multiple branches; Master, Beta and Push Notifications. They just finished the notifications feature in the push notifications branch and want to move it to the beta branch. how can you get this

• Look at the push notifications branch and run git merge beta
• Look at the master branch and run git merge beta -> push notification
• Delete the push notification branch and it will automatically be passed to the master branch
• Check out the beta branch and run the git merge push notification

Q5. Which of the following statements is true when using the following command?

git add -A

• All new and updated files are prepared
• The files are arranged alphabetically.
• All new files are prepared
• Only updated files are prepared

F6. What will the following command output in the terminal?

git remote -v

• A list of remote repositories and their URLs
• The current version of Git you are running
• An online editor for modifying remote repositories
• The last 5 Git versions you have installed

Q7 Describe what happens using the following commands.

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

• The commit is marked for publication in the feature user location branch
• A commit is copied from its original branch to the feature-user-location branch
• The commit is selected as the new HEAD of the commit history.
• A commit is copied from the role user location branch to the master branch
• The branch is changed to the feature-user-location branch and the specified commit is applied to the branch.

Explanation:Commits are not copied when cherries are selected, cherries are selected. The changes introduced by the commit are applied and then a new commit is created. This allows us to fetch certain changes as if they were patches (the git book actually calls thisParchar). When a new commit is created in user-location-role, HEAD also changes accordingly. You can see this in itgato .git/HEADjcat .git/refs/heads/feature-user-ubicaciónin this case. SeeMann git-Cherry-Pickfor details.

USE: So far there are two versions of this question. The task is always "describe what happens", the commands are always acheck overand acherry picker, and the correct answer is always the same.

Q8 What does the following command do with the git repository?

git reset --soft head^

• Removes all previous commits and resets the repository history to its initial state.
• Reverts the working branch to the first commit.
• Keeps HEAD on the current commit but deletes all previous commits.
• Sets HEAD to the previous commit and leaves the reverted commit changes on the stage/index.

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

• Manually go back through your commit history.
• Use git search -diff to compare all commits in your repository's history.
• Run a git rebase to find the commit with errors.
• Use git bisect to compare the failing commit to an early commit that works as expected.

Q10. Why should the following command be used?

git rebase -i HEAD~10

• To do a comparative search of the last 10 diff commits
• To list the last 10 commits and change them with the squash or fixup command
• To delete the last 10 commits and reset HEAD
• To cache the last 10 commits locally

Q11. Why would you use a pre-receive link in your remote repository?

• You wouldn't use it in the local repository
• How to run a script when a remote control receives an impulse that fires before the references are updated
• How to trigger a script after making updates to the remote repository
• To debug all commit tags and release versions

Q12. Which option can you use to apply Git configurations to your entire Git environment?

• --at
• --Maestro
• - global
• --To update

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

• cache
• You can't git merge --squash is the only git command for this operation.
• Fuchs
• get going again

F14. What would happen if you clone an existing git repository?

• A new copy would overwrite the central repository
• A copy of the repository is created on your local computer
• Nothing, cloning is not a supported Git feature
• A copy of the repository would be made on the hosting platform.

Q15. How can you view a list of files added or changed on a specific commit?

• Locate the commit in the remote repository as that is the only place that stores this type of information.
• Use thedifference treeCommand with the commit hash.
• Rungit commit --infowith the commit hash.
• Access commit stash data withgit stash.

Q16. What files should this .gitignore file delete?

#.swiftbuild/*.txt*.metadata

• All files with a .swift, .txt, or metadata file extension, as well as the entire build directory
• Just the build directory
• All files in the build directory, as well as files ending in .txt or .metadata
• Only files with .swift and .txt extensions.

A line beginning with#serves as a comment. For this reason# .fastdoes not show anythingman ignored.

Q17. After making changes to a local repository, run the following command. What will that do?

git commit -a -m "refactor codebase"

• Nothing, you cannot use multiple options in the same command
• Add any new files to the staging area
• Confirm any new files with a message
• Adds all changed files to the staging area and then commits them with a message

Q18 After checking the git status it gets the following output showing the beta-notes.js file on commit but also unprepared. How can this situation happen?

Change to commit: (use "git reset HEAD <file>..." to remove stage) changed: beta-notes.jsChanges not ready to commit: (use "git add <file>..." to update what will be committed (use "git checkout --<file>..." to discard working directory changes) changed: beta-notes.js

• There were two copies of beta-notes.js, but one has been removed
• beta-notes.js was prepared and then modified, creating two different versions of the file
• Two copies of beta-notes.js were created, but only one is being crawled
• There are two tracked copies of beta-notes.js, but one has been uncommitted

Q19. Where are the files stored before being pushed to the local repository?

• saved files
• git documents
• stage area
• hidden from git

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

• ⠀

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

• ⠀

  (Video) Free FDF Answer Files of The LinkedIn Skill Assessment Test | Linkedin skill/Assessment Answer File

  git pull -u origen mastergit reset --hard master

• ⠀

  git pull origin mastergit reset --hard origin/myCurrentBranch

• ⠀

  git fetch --allgit reset --origen duro/maestro

• The commandfemale dogesSeekfollowed by someonetieÖZorro(in this case,tie). We don't want to merge. Merge would be an action for oursRepository. We just want to override ourslocal files.

Q21. Which statement is true when using the git add -A command?

• Only new files in the working directory are stored in the index.
• All new and updated files in the working directory are stored in the index.
• All files in the working directory are arranged in alphabetical order in the index.
• Only files updated in the working directory are stored in the index.

Q22. You notice that your project has a tag and a branch, both called push notifications, which causes confusion when trying to print the given reference. How can you indicate which branch you want to look at?

• Use git show refs/push-notifications
• Use git show push notifications
• Use git show heads/refs/push notifications
• Use git show refs/head/push-notifications

Reference

Q23. Your team lead needs a list of all commits that are being pushed before performing a reorganization. What command allows you to access this information?

• git rebase-record
• git rebase -i
• git rebase-verbose
• git rebase-all

Q24. Given the following Git commands, what does the operation do?

git bisect startgit bisect malo 5d41402abc4b2a76b9719d911017c592git bisect bueno 69faab6268350295550de7d587bc323d

• Executes a combination of a good commit spotted by a known bad commit and a known good commit
• Marks a commit for removal, using a known bad commit and a known good commit to determine which commit caused a bug
• Defines a bad commit and resets the HEAD using a known bad commit and a known good commit
• Performs a binary search of a known bad commit and a known good commit to determine which commit caused an error.

Q25. In a situation where you have multiple commits for a single task, what's the most efficient way to reorganize your commit history?

• Select the commits related to another branch.
• Delete task confirmations and confirm with new message.
• Group related commits into a single coherent commit.
• Store the related commits in a new hash.

Q26. Which of the following statements is true about the git push command?

• By default, a push does not send tags to the remote repository.
• Commits can only be marked when they are created.
• The tags are pushed to the remote repository with their respective commits.
• Only annotated tags are automatically pushed to the remote repository with a commit.

Reference

Q27. What shortcut can you use in the future after pushing commits to the remote repository for the first time with the following command?

git push -u original Maestro

• Git-Push-Meister
• git push origen
• As before, git push -u origin master
• git push

Q28. How would you create a custom shortcut or command in your git environment?

• Run git hotfix with the shortcut name.
• Assign a shortcut or command using the Git options file.
• Use the git custom-key command.
• Create an alias with the git config command.

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

Changes not ready to commit: (use "git add <file>..." to update what's being committed) (use "git checkout -- <file>..." to check out changes in the discard working directory) changed: beta-notes.js

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

Q30. Which command would allow you to change your previous commit?

• -arrange
• -quick solution
• -Change
• -change

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

• data matrix
• data register
• data snapshot
• data dictionary

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

git rm --cache testfile.js

• testfile.js is removed from the staging area and your changes are no longer tracked.
• testfile.js is removed from the staging area, but your changes are still tracked.
• A copy of testfile.js is cached on your desktop.
• The current copy of testfile.js is stored in the staging area.

Q33. After successfully merging two branches and committing the changes, what's the next step to keep your Git structure organized?

• Use git reset --soft HEAD to undo a commit.
• Run the git -d branch<branch name>to delete the merged branch.
• Use git clear-all to clean up all pending files.
• Run git rebase to move the current commit back to its original location.

Q34. When modifying a file, you are unexpectedly assigned an urgent bugfix on another branch. How can you temporarily store your work locally without committing yourself?

• This isn't possible because you can't save locally without a commit.
• Run git hold to save a local copy of your work that you can come back to later.
• Store your work with git local-cache.
• Use git stash to save your work and come back later and reapply the hidden commit.

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

• add to
• Start
• git new
• start git

Q36. While working on a feature branch, you try to use "git rerere" to resolve a recurring merge conflict, but nothing happens. What could be causing this problem?

• The -all option is not added to the command.
• "rerere.enabled" is not enabled in the configuration file.
• The commit hash is missing.
• The file path is not specified.

Q37. Which configuration determines which pager is used when generating Git pages?

• core.page
• book page
• people search
• core.pager

Q38. What does the commit object contain?

• A set of files that represent the status of a project at a specific point in time.
• Reference to main commit objects.
• A SHA1 name, a 40-character string that uniquely identifies the commit object.

Q39. What is the option to include the confirmer's name in a custom record format?

• % ce
• %cr
• %CD
• %cn

Q40. How many ways are there in Git to integrate changes from one branch to another?

• 3

• 5

• 2

• 4

• Explanation: There are two main ways in Git to incorporate changes from one branch into another: merging and rebasing.

• Referenzlink

  (Video) LinkedIn MS Word assessment Quiz Answers ✅ passed ( jan 2021 )

Q41. Which user should be created first during SSH setup?

• git
• Administration
• root
• None of them

Q42. Which command lists the tags with the string 1.4.2?

• Git-Tag 'v1.4.2'
• tag git -I ‘v1.4.2.*’
• Git-Tag-List "v1.4.2*"
• Git-Tag 'v1.4.2*'

Q43. Which of the following is an integration manager?

• lieutenants
• benevolent dictator
• Depends on the type of project
• Depends on the dates

Q44. Which Git command starts tracking a new file?

• add to
• Add file
• Start
• rail

Q45. Which of the following is called a dumb protocol?

• All these
• SSH
• Git
• HTTP

Q46. Which keystroke returns a set of hints to choose from when typing a Git command?

• control
• Change
• eyelash
• Alternative

Q47. Which of these terms best describes Git?

• Distributed version control system
• Issue-Tracking-System
• Integrated development environment
• Web based repository hosting service

Q48. Which command gets a copy of an existing Git repository?

• double
• replicate
• Copy
• Clone

Q49. How does Git think about your data?

• archive
• None of them
• snapshot
• file

Q50. Which option allows author name to be included in a custom record format?

• %Military
• %Notice
• %ae
• %And

Q51. What version forward did Git offer to restore a file as it looked when it was last committed?

• 1.7
• 1.6
• 2.0
• 1.8

Q52. What strategy does Git use to merge two branches?

• LIFO
• recursively
• FIFO
• Cracks

Q53. What does Refs store?

• Valor SHA-1
• None of them
• branch name
• project name

Q54. What language is used in GIT?

• C
• C++
• C#
• Java

Q55. What is usually the extension of the file containing the public key?

• sch
• Bar
• Taste
• Package

Q56. What is the difference between initializing a normal repository and a simple repository?

• Bare repositories store their Git history in a .git subfolder.
• Bare repositories do not have a .git extension.
• Bare repositories do not come with working or unprotected source files.
• Bare repositories should be used for local rather than remote repositories.

Q57. How many unique commits can a single repository have?

• any number of confirmations
• only one local commit per repository
• only three commits per branch
• only one commit per HEAD

Q58. What types of tags does Git support?

• heavy and concise
• light and unchanging
• weighed and rated
• light and spotted

Q59. After making a bunch of changes to the index, what command could you use to check them before committing?

• git diff - cached
• git difference
• git diff --HEAD
• git-status -v -v

Q60. What does the git stash drop command do?

• Delete the last hidden entry
• clear the stock
• list everything in stock
• discard the oldest entry

Q61. Which command creates a new branch from the currently checked out branch?

• git -b checkout <nombreDeLaSucursal>
• rama git
• git checkout <nombreDeLaSucursal>
• git checkout -b <nombreDeLaSucursal>

Q62. After accidentally indexing a file named myFile, how would you remove it from the index to exclude it from your next commit?

• Usa git reset HEAD^.
• Utility git reset myFile.txt.
• Use git -rm myfile.txt.
• USA-Git-Reset.

Q63. What happens when you run this command from your master branch?

git checkout -b prueba beta

• The beta test branch is pulled from the current commit.
• The beta test branch is checked out and removed.
• A new branch called Beta Testing will be created and moved there.
• The beta testing branch is merged into the master branch.

Q64. How does Git manage branches internally?

• Creating a pointer to the latest snapshot/commit for the branch.
• Creating an array of branches data in the same repository.
• Creating a dictionary for code change dates.
• creates a debug log that saves the repository changes.

Q65. You want to perform a git reset, but you can't restore all available options. What command would you use to display a description of it?

• Reset git help
• git -h reset
• Reset Git Options
• Git reset help

Q66. What is a remote repository?

• a version of the repository that reflects changes made to the local repository's master branch for open source collaboration efforts
• the main repository chosen by the Git arbiter, which resides in the local repositories of collaborating team members
• a read-only version of the repository stored on a backup server in case local repositories are lost or corrupted
• an internet or web-hosted version of the repository that is pushed or pulled by contributors

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

• git restore
• cancel
• sauber
• git checkout

Q68. After you start merging a feature branch into your master branch, you encounter a merge conflict and decide you don't want to merge. How can you stop the merge and restore the pre-merge state?

• Use git restore -p.
• USA git merge -u.
• Use git merge --abort.
• Usa git merge - undo.

Q69. If you have multiple commits for a single feature, what's the most efficient way to reorganize your commit history?

• Use git stash to consolidate commits under a new hash.
• Use git squash to consolidate commits into a single consistent commit.
• Delete task confirmations and confirm with new message.
• Use git cherry-pick to move the commits to another branch.

Q70. Which command correctly creates a lightweight tag?

• Label git v3.8.1
• tag git --light "v3.8.1"
• git etiqueta v3.8.1 --anotar -m "<tagMessage>"
• git-Tag -l v3.8.1

Q71. What is the main problem with using git rebase when working with multiple developers?

• Rebase only affects your repository and creates a diff on the main branch.
• Rebase creates a temporary copy of the master branch in the remote repository.
• Rebase moves the HEAD of the remote master branch forward by one commit.
• Rebase removes all commit history for the new feature branch.

Q72. What Git workflows are used by teams collaborating on a single branch and avoiding the creation of long-lived development branches?

• Git-Flow
• main flow
• Trunk-based development
• Github-Flow

Q73. What option in the git log command allows you to limit the output to commits made after specific dates?

• --out of
• --since when
• -<n>
• - by date

p. 74. How would you remove unreachable objects older than a certain time from your project's database?

• git cache --deprecated <time>
• git branch --rebase <time>
• git delete --inert <time>
• git prune --expire <time>

Q75. What conflicts can arise when a shot is forced after the pass?

• The remote master branch may overwrite existing changes.
• The source URL is reset to its default value.
• The current HEAD is deleted and cannot be reset.
• Nothing, it is common to force a jab after passing.

p. 76. How does this command change the currently checked out branch?

git reset --soft head^

• Reverts the working branch to the first commit.
• Sets HEAD to the previous commit and leaves the reverted commit changes on the stage/index.
• Removes all previous commits and resets the repository history to its initial state.
• Keeps HEAD on the current commit but deletes all previous commits.

p. 77. What is the difference between Git and SVN?

• Git only works on Linux while SVN works on all operating systems.
• SVN only works on Linux while Git works on all operating systems.
• SVN is a centralized system while Git is a distributed system.
• Git is a centralized system while SVN is a distributed system.

p. 78. This command is an example of what kind of label?

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

• detailed
• written down
• Licht
• postponed

p. 79. What is the difference between a soft reset (git restart --soft) and a hard reset (git reset –duro) ?

• A soft reset only changes the commit pointed to by HEAD, while a hard reset resets the index and working tree to match the specified commit and discards all changes.
• A soft reset caches the old HEAD pointer, while a hard reset removes it entirely.
• A hard reset only changes where the HEAD is pointing, while a soft reset changes both the HEAD and the index.
• A hard reset caches the old HEAD pointer, while a soft reset removes it entirely.

Q80. Consider the following Git workflow:

Which of the following options is correct?

• 1. Develop 2. Release 3. Patch 4. Feature 5. Master
• 1. Master 2. Version 3. Patch 4. Feature 5. Develop
• 1. Develop 2. Master 3. Hotfix 4. Feature 5. Develop
• 1. Master 2. Review 3. Develop 4. Feature 5. Release

Q81. What information does the Git configuration file store?

• Shell Scripts and Flags
• keychain and account information
• local and global repository options
• Precompile scripts and configurations

Reference

Q82. What is version control?

• a type of architecture used to manage large databases
• a system that displays, tracks, and controls changes to a set of files over time
• A programmatic design pattern used to manage code between multiple development teams
• a type of software that links a project to a GitHub repository

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

• git stash removes a commit from the repository history, while git stash pop saves changes to multiple branches.
• git stash stores changes in multiple branches, while git stash pop removes a commit from the repository history.
• git stash removes the latest commit, while git stash pop saves the current changes.
• git stash creates a hidden entry, while git stash pop puts the saved state in the working directory.

Q84. What 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

Q85. How would I configure Git to abort a commit when a Smoke test script fails?

• Create a post-commit shell script that triggers the action.
• Create a post commit link to activate the script.
• Create a precommit hook to activate the script.
• Create a pre-commit shell script that triggers the action.

Q86. Which use case is NOT a good candidate for a git hook?

• state-dependent environmental changes
• continuous integration
• increased code coverage
• enforcement of the rules of engagement

Q87. After starting work on a new feature and creating new files in its working directory, the client found that the feature was no longer needed. What command can be used to remove the untracked files from the working directory?

• git clean -f
• git rm
• git reset HEAD
• git checkout.

Q88. What information do Git reflogs (reference logs) store?

• Shell script pointer and keychain credentials
• Updates to branching notes and other references in the local repository
• Release Notes and Mandatory Script Values
• Tag and version information

Q89. You have just finished reorganizing your master branch and need to manually update the remote master even though there is a merge conflict. how can you get this

• git push --overwrite
• git push --update
• git push --assert
• git push --force-with-lease

Q90 What's the difference betweenSeekamdpull git

• Seekcreates a new branch from the main branch whilepull gitcreates a new branch of the main branch of the local repository.
• pull gitdownloads new data from a remote repository without integrating it into local files whileSeekupdates the current HEAD branch with the latest changes from the remote server.
• Seekupdates remote tracking branches with changes from a remote repository whilepull gitupdates remote tracking branches with changes from a remote repository and merges them with their corresponding local branches.
• Seekdownloads and merges data from the local repository whilepull gitYou tell your colleagues that you will be making changes to the main office.

Q91. Which command shows the difference between the working tree and the stage/index area and the files that Git doesn't track?

• actually
• Git-Status
• git lokal
• Context git

Q92. Your current repository has three branches: master, beta, and push notifications. You've just completed the notification feature and committed changes to the push notification branch, and you want to add them to the beta branch. how can you get this

• Check out the beta branch and run git merge push notifications.
• Take a look at the push notifications branch and run git merge beta .
• Look at the master branch and run git merge beta -> Push Notifications.
• delete push notifications branch; it is automatically passed to the master branch.

Q93. You want to restore some previously hidden work to a new branch. How can you do that?

• Eins the git branch.
• Add the hidden commits to the current commit and then create a new branch.
• USA git checkout -b.
• Run the Git storage branch.

reference here

Q94. What is the difference between git branch -d and git branch -D?

• -D deletes the local branch, while -d deletes the branch regardless of push and merge status.
• -d removes the current commit header, while -D removes the entire branch.
• -d deletes local branch while -D deletes local branch regardless of push and merge status.
• -D removes the current commit header, while -d removes the entire branch.

Q95. You have hidden three changesets but cannot remember the contents of the first hidden entry. What command would you use to show the details of the changes to the first of the three hidden entries?

• git stash show -p[email protected]{2}
• Git hide list
• git stash show -p[email protected]{1}
• git stash show -p

reference here

Q96. Which statement about the git push command is correct?

• By default, a push does not send tags to the remote repository.
• Only annotated tags are automatically pushed to the remote repository with a commit.
• The tags are pushed to the remote repository with their respective commits.
• Commits can only be marked when they are created.

reference here

Q97 How would you delete a remote branch in your repository?

• Usegit --delete <branch_name>.
• Usegit push <remote_name> --d <branch_name>.
• Usegit push <remote_name> --D.
• Usegit push <remote_name> --delete <branch_name>.

reference here

Q98 What is the default forGit-Relogif no subcommands are specified?

• extinguish
• go out
• show
• To update

reference here