Manage SSH Keys for Authentication GITLAB-CERTIFIED-GIT-ASSOCIATE Practice Questions (Page 3)

Questions 11–15

1. 11expert · hard

   A user has added their SSH key to GitLab and can successfully run ssh -T git@gitlab.com. However, when they run git clone git@gitlab.com:group/project.git, they get 'ERROR: Project not found'. What is the most likely cause?

   • AThe SSH key has expired.
   • BThe project path in the URL is incorrect.
   • CThe SSH key is not associated with the correct GitLab account.
   • DThe user is not using the correct SSH port.
   Reveal Solution Discussion Select an answer first
2. 12expert · hard

   A user has multiple SSH keys and uses an SSH config file. They run ssh -T git@gitlab.com and it works, but when they run git push using a remote URL that uses a Host alias, they get 'Permission denied (publickey)'. What is the most likely cause?

   • AThe SSH agent has the wrong key loaded.
   • BThe private key file permissions are too open.
   • CThe public key is not added to GitLab.
   • DThe Host alias in the remote URL does not match any entry in the SSH config.
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   What is the role of the private key in GitLab SSH authentication?

   • AIt is stored on GitLab's servers to verify your identity.
   • BIt signs a challenge from the server to prove you own the corresponding public key.
   • CIt is used to encrypt your Git credentials before sending them to GitLab.
   • DIt is used to encrypt all data transmitted during Git operations.
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   What is the purpose of using an SSH config file with multiple Host entries?

   • ATo store multiple public keys for the same account.
   • BTo bypass SSH key authentication entirely.
   • CTo encrypt the SSH connection with different algorithms.
   • DTo define different connection settings, such as keys and usernames, for different hosts.
   Reveal Solution Discussion Select an answer first
6. 15expert · hard

   A developer has two SSH keys: one for GitLab.com and one for a self-hosted GitLab instance at gitlab.company.com. They have configured ~/.ssh/config with entries for both hosts. When they run git push to the self-hosted instance, SSH uses the wrong key and authentication fails. What is the most likely cause?

   • AThe public key for the self-hosted instance is not added to the SSH agent.
   • BThe remote URL uses the hostname 'gitlab.company.com' but the config entry uses a different Host alias.
   • CThe config file has the Host entries in the wrong order.
   • DThe private key for the self-hosted instance has a passphrase that is not cached.
   Reveal Solution Discussion Select an answer first