# Free GH-900 practice questions

> 10 free GH-900 practice questions with the correct answer and an explanation.

Page: https://devopscodelab.com/exams/github-gh-900/free-practice-questions/
Practice exams: https://devopscodelab.com/exams/github-gh-900/

### Question 1 of 10

Which statement correctly describes the relationship between Git and GitHub?

- A. GitHub is the command-line client used to run Git commands, while Git is the website that stores repositories
- B. Git is an open-source distributed version control tool; GitHub is a platform that hosts Git repositories and adds collaboration
- C. Git is the paid enterprise edition of GitHub that adds self-hosting and auditing on top of the free cloud service
- D. Git and GitHub are two names for the same product: GitHub is simply the company that develops, maintains and sells licenses for Git

**Answer:** B

**Explanation:** Git is a free, open-source distributed version control system that runs locally, and GitHub is a hosting platform built around Git that adds pull requests, issues, Actions and more. Git is not a paid edition of GitHub; the self-hosted product is GitHub Enterprise Server. GitHub is not a command-line client, and Git was created by Linus Torvalds, not developed and sold by GitHub.

### Question 2 of 10

A marketing team stores campaign copy in shared folders and often overwrites each other's edits without knowing who changed what. Which benefit of a version control system addresses this problem MOST directly?

- A. Scheduled backups of the shared folders to a second location every night
- B. A full change history showing who changed what and when, with earlier versions restorable
- C. Automatic compression of large binary files so that shared folders consume less storage space
- D. Real-time co-editing of the same document, similar to an online word processor

**Answer:** B

**Explanation:** Version control records every change as a snapshot with an author, timestamp and message, so the team can see who changed what and roll back to any earlier version. Compression saves space but does not track authorship. Real-time co-editing is a word-processor feature, not version control, and nightly backups only capture one point per day without per-change attribution.

### Question 3 of 10

A company has 12 separate GitHub organizations, one per business unit. Leadership wants to centrally manage billing, enforce policies and view audit data across all of them. What should the company use?

- A. An enterprise account that owns all 12 organizations
- B. A single personal account with owner permissions in each of the 12 organizations
- C. A parent repository with all organizations referenced as Git submodules
- D. A thirteenth organization that has every other organization added to it as a team member

**Answer:** A

**Explanation:** An enterprise account sits above organizations and provides a single point for billing, policy enforcement and audit visibility across all of them. Organizations cannot be added as members of another organization, a personal account with owner rights in each organization still manages them one at a time, and submodules link repositories, not organizations or policies.

### Question 4 of 10

A developer creates a repository from a template that has several branches, but the new repository only contains the default branch. What should they have done to get the other branches too?

- A. Selected Include all branches when creating from the template
- B. Forked the template instead, because templates never copy branches
- C. Enabled the Template repository setting on their new repository
- D. Run git pull --all in the new repository right after creation

**Answer:** A

**Explanation:** When creating from a template, the Include all branches option copies every branch; by default only the default branch is included. Forking would create a linked fork rather than an independent repository, pulling cannot fetch branches that the new repository never received, and enabling the template setting on the new repository only lets others use it as a template.

### Question 5 of 10

A platform team wants every new microservice repository to start with the same folder structure, workflow files and README skeleton, but without sharing commit history with the original. What should they set up?

- A. Create a branch in the starter repository for every new microservice
- B. Store the starter files in a public gist and copy them into new repositories
- C. Fork the starter repository into the organization each time a new service is needed
- D. Mark a starter repository as a template repository and create new repositories from it

**Answer:** D

**Explanation:** A template repository lets anyone create a new repository with the same files and folders but a fresh, unrelated history. A fork keeps a link to and the full history of the upstream repository, and a branch per service keeps every service in one repository. A gist can hold files but cannot generate a repository with workflows and structure in one step.

### Question 6 of 10

An open-source project receives many questions such as "How do I configure X?" that clutter its issue tracker. Maintainers want a forum-style space for Q&A and ideas, with the ability to mark an answer. Which feature should they enable?

- A. GitHub Discussions
- B. GitHub Projects
- C. GitHub Wikis
- D. GitHub Gists

**Answer:** A

**Explanation:** Discussions provide a forum for open-ended conversations, with categories, Q&A formats where an answer can be marked, and polls, keeping the issue tracker for actionable work. Wikis host documentation pages, gists share snippets of code, and Projects plan and track work items, none of which offer threaded Q&A with accepted answers.

### Question 7 of 10

A new contributor needs to start coding on a large project within minutes, with the correct runtimes, extensions and tools already installed, using only a browser. What should the maintainers provide?

- A. A github.dev link so contributors can edit files in the web-based editor
- B. A dev container configuration so contributors can launch a GitHub Codespace
- C. A README that lists every tool and version contributors must install
- D. A GitHub Actions workflow that installs the tools on a hosted runner

**Answer:** B

**Explanation:** Codespaces are cloud development environments defined by a devcontainer.json, giving a ready-to-use machine with runtimes, extensions and a terminal in the browser or VS Code. github.dev is a lightweight editor without a terminal or compute, so it cannot run the project. An Actions runner executes workflows rather than providing an interactive environment, and a README still requires manual local setup.

### Question 8 of 10

A product owner wants to visualize work items as cards moving through columns such as Todo, In Progress and Done. Which GitHub Projects layout should they use?

- A. Insights chart
- B. Board layout
- C. Roadmap layout
- D. Table layout

**Answer:** B

**Explanation:** The board layout shows items as cards in columns based on a field such as Status, giving a kanban view. The table layout is a spreadsheet-style grid, the roadmap layout shows items on a timeline using date or iteration fields, and insights charts visualize progress rather than moving cards between columns.

### Question 9 of 10

Which repository visibility option is available only to repositories owned by organizations in an enterprise, and makes the repository visible to all enterprise members but not to the public?

- A. Internal
- B. Public
- C. Restricted
- D. Private

**Answer:** A

**Explanation:** Internal repositories can be viewed by every member of the enterprise, which supports InnerSource, while staying hidden from the public. Private repositories are visible only to people explicitly granted access, public repositories are visible to everyone on the internet, and Restricted is not a GitHub repository visibility level.

### Question 10 of 10

A large company wants teams to share code and contribute to each other's internal projects using pull requests and open collaboration, while keeping the code private to employees. What is this practice called?

- A. Dual licensing
- B. Open core
- C. Monorepo
- D. InnerSource

**Answer:** D

**Explanation:** InnerSource applies open-source practices such as transparency, pull requests and shared ownership inside an organization, often using internal repositories. Open core is a business model with an open base and proprietary extensions, dual licensing offers code under two licenses, and a monorepo is a repository layout, not a collaboration culture.

Ready for a timed run? Take the free 15-question GH-900 mini exam: https://devopscodelab.com/app/exams/github-gh-900/mini/

DevOpsCode Lab is not affiliated with GitHub. GH-900 and related names are trademarks of their owners. We write every question ourselves; these are not real exam questions.
