GitHub Foundations (GH-900) · 9% practice allocation

GitHub GH-900: Manage Projects with GitHub Practice Questions

5 free sample questions from the Manage Projects with GitHub domain, with answers and explanations. The full GH-900 bank has 150 questions across 7 domains. Questions are scenario-based and written from the official GitHub exam guide.

1.

A scrum team plans in two-week cycles and wants a project field that automatically generates the current and upcoming time-boxed periods so items can be assigned to a cycle and burndown reported per cycle. Which custom field type should they add?

  • A. Date
  • B. Iteration✓ Correct
  • C. Number
  • D. Single select
Explanation

The iteration field type creates repeating, configurable time periods (with breaks if desired) and powers iteration-based grouping, filtering, and insights. Single select would require manually creating and maintaining an option for every sprint. A date field captures a single point in time, not a period. A number field stores numeric values such as estimates.

2.

A release manager needs a visual timeline showing when each epic starts and ends over the next two quarters, using the project's "Start date" and "Target date" fields. Which Projects (v2) layout meets this need?

  • A. Roadmap layout✓ Correct
  • B. Board layout with swimlanes
  • C. Milestone page in the repository
  • D. Table layout grouped by iteration
Explanation

Roadmap layout plots project items horizontally over time based on date or iteration fields, which is precisely a start/end timeline. Table layout grouped by iteration lists items but shows no timeline bars. Board layout is column-based status tracking, not time-based. A repository milestone page shows a single due date and progress bar per milestone, not a multi-item timeline.

3.

A team lead wants to see all issues and pull requests for a project in a spreadsheet-like view where custom fields such as "Priority" and "Estimate" appear as columns that can be sorted and grouped. Which GitHub Projects (v2) layout should they use?

  • A. Roadmap layout
  • B. Table layout✓ Correct
  • C. Insights layout
  • D. Board layout
Explanation

Table layout presents items as rows with fields as columns, supporting sorting, grouping, and inline editing — exactly like a spreadsheet. Board layout is a Kanban-style column view grouped by a single field, not a spreadsheet grid. Roadmap layout plots items on a timeline using date fields. Insights is not a layout; it is a separate charting/reporting area of a project.

4.

An engineering director wants a single place to track the same high-level initiatives that span six repositories, with shared custom fields and a roadmap. Which approach best fits GitHub's recommended model?

  • A. Use a milestone with the same name in each of the six repositories and view them together
  • B. Create one organization-level project and add issues from all six repositories✓ Correct
  • C. Create six repository-level projects and link them to each other
  • D. Create one repository-level project in the busiest repository and grant everyone access to that repository
Explanation

Organization-level projects are built to aggregate items from many repositories under one set of custom fields and views, including roadmaps. Six separate projects fragment the data, and projects cannot be linked into a single consolidated roadmap. A repository-level project can accept items from other repositories only in limited ways and forces unnecessary repository access. Milestones are repository-scoped with no cross-repository rollup view.

5.

Select THREE actions that can be performed with built-in (no-code) Projects (v2) workflows.

  • A. Automatically assign a code reviewer based on file paths changed
  • B. Automatically add newly opened items from a chosen repository to the project✓ Correct
  • C. Set the Status field when an item is closed✓ Correct
  • D. Automatically create a new repository when a status changes to Done
  • E. Set the Status field when a pull request is merged✓ Correct
Explanation

Built-in project workflows include item-closed and PR-merged triggers that set Status, and an auto-add workflow that pulls in newly created issues/PRs matching a filter from a repository. Creating repositories is an administrative action outside project workflows. Reviewer assignment by file path is handled by CODEOWNERS or team review assignment, not by project workflows.

Test yourself across every GH-900 domain

The free GH-900 practice test mixes about 20 questions weighted like the exam. The full 150-question bank adds instant grading, flashcards and a timed mock exam.

Take the free GH-900 practice testPractice the full bank

Study this domain

Manage Projects with GitHub study guide (GH-900) →

Other GH-900 domains

← All GitHub Foundations study resources