GitHub-Foundations GitHub Foundations Exam Practice Test

Page: 1 / 14
Total 75 questions
Question 1

What folder is the definition files stored in when creating custom issue forms?



Answer : C

When creating custom issue forms on GitHub, the definition files are stored in the .github/ISSUE_TEMPLATE folder. This directory is used to define issue templates and forms that help standardize the information collected when users open new issues in the repository. The .github folder is a special directory used for various repository configurations and workflows.


Question 2

What qualifier finds issues that mention a certain user?



Answer : A

The qualifier mentions: is used in GitHub's search functionality to find issues that mention a certain user. For example, if you want to find all issues where a specific user is mentioned, you would use mentions:username. This helps in tracking where a user has been involved in discussions across issues or pull requests.


Question 3

After 30 minutes of inactivity, a GitHub Codespace will:



Answer : D

After 30 minutes of inactivity, a GitHub Codespace will time out. This is designed to conserve resources when the Codespace is not being actively used. The session will be paused, and you'll need to reconnect to resume your work. However, the Codespace is not deleted, and any unsaved changes might not be lost but should be committed or saved to prevent data loss.


Question 4

What is the minimum access needed to contribute to a repository?



Answer : D

To contribute to a GitHub repository, a user typically needs to be able to create branches, push changes, and open pull requests. These actions require Write access, which is the minimum level of access needed to contribute code directly to a repository.

Write Access:

Option D is correct because 'Write' access allows users to contribute to the repository by pushing changes, creating branches, and opening pull requests. This is the minimum required access level for contributing code.

Incorrect Options:

Option A (Read) is incorrect because 'Read' access only allows viewing the repository, not making changes.

Option B (Triage) is incorrect because while Triage access allows managing issues and pull requests, it does not allow pushing code.

Option C (Maintain) is incorrect because 'Maintain' access includes additional permissions beyond those needed for basic contributions, such as managing repository settings.


GitHub Docs: Repository Roles for an Organization

Question 5

Which of the following best describes GitHub Copilot?



Answer : C

GitHub Copilot is described as an AI pair programmer that offers autocomplete-style suggestions. It is a tool integrated into development environments like Visual Studio Code that helps developers by providing code suggestions as they type. Copilot can suggest entire lines or blocks of code based on the context of what you're writing, making it a valuable assistant in coding, but not a replacement for developers.


Question 6

Where can you go to discover, browse, and install tools?



Answer : A

The GitHub Marketplace is the place where users can discover, browse, and install various tools and integrations that extend the functionality of GitHub. These tools can include CI/CD services, security checks, and other development utilities that enhance workflow automation and project management.


Question 7

Which of the following best describes GitHub flow?



Answer : C

GitHub Flow is a simple, yet powerful, branching strategy that is widely used in modern software development. It emphasizes collaboration and flexibility.

GitHub Flow:

Option C is correct because GitHub Flow is a lightweight workflow designed for safe experimentation and collaboration. It involves creating branches for new features or fixes, opening pull requests for review, and merging changes back into the main branch after approval.

Incorrect Options:

Option A is incorrect because GitHub Flow uses a single main branch, not multiple primary branches.

Option B is incorrect because GitHub Flow is not specifically designed around releases; it is more focused on continuous development and integration.

Option D is incorrect because GitHub Flow is not strict or linear; it encourages branching and pull requests rather than direct changes on the main branch.


GitHub Docs: Understanding the GitHub Flow

GitHub Guides: The GitHub Flow

Page:    1 / 14   
Total 75 questions