GH-900 GitHub Foundations braindump and exam questions

GH-900 GitHub Foundations Questions & Answers

Despite the title of this article, this isn’t a GitHub Foundations braindump in the traditional sense of the word.

I don’t believe in cheating.

The term braindump usually means someone took the actual exam and then tried to rewrite every question they could remember, basically dumping the contents of their brain onto the internet.

That’s not only unethical, it’s a direct violation of the certification’s terms and conditions. There’s no pride or professionalism in that.

This set of GitHub Foundations exam questions and answers isn’t that.

An honest approach to GitHub certification

All of the questions here come from my GitHub Foundations Udemy course or the certificationexams.pro certification website, which hosts hundreds of original practice questions focused on GitHub certifications.

Each GitHub Foundations exam question in this article has been carefully created to match the topics and skills covered in the real exam without copying or leaking any actual GitHub foundations questions.

The goal is to help you learn honestly, build confidence, and truly understand how GitHub works, from repositories and pull requests to issues, workflows, and project organization.

If you can confidently answer these questions and understand why the wrong answers are wrong, you won’t just pass the GitHub Foundations exam. You’ll walk away with a stronger understanding of Git, GitHub, and how teams use these tools to collaborate and build software the right way.

So here you go, call it a GitHub Foundations braindump if you want, but really it’s a smart, ethical study guide designed to help you think like a pro.

More practice exam questions can be found in this GitHub Foundations Udemy course.

The questions are challenging, but each one includes a full explanation along with tips and strategies to help you handle similar questions on the real exam.

Have fun, stay curious, and good luck on your GitHub Foundations certification journey.

Honest GitHub Foundations Exam Questions

Question 1

In the GitHub Network graph, what is the maximum number of most recently updated branches that can be displayed?

• A. Up to 90 branches
• B. Up to 120 branches
• C. Up to 60 branches

Question 2

Under what conditions can a GitHub Actions workflow invoke a reusable workflow from the same repository or from a different repository?

• A. Only in a public repository
• B. Same repository or allowed public repository or private repository with access
• C. Only when both repositories are in the same organization
• D. Only in the same repository

Question 3

In a GitHub Discussions thread using the question and answer format, how can a moderator highlight the reply that resolves the question for readers?

• A. Convert the discussion to an issue
• B. Mark the reply as the accepted answer
• C. Pin the reply at the top

Question 4

Which GitHub Enterprise Server feature enforces deployment protection rules for private and internal repositories?

• A. GitHub Advanced Security
• B. GitHub Actions environments
• C. Protected branches
• D. GitHub Connect

Question 5

Which information is displayed on the Security tab in a GitHub repository?

• A. Insights traffic and clone analytics
• B. Unified dashboard of dependency alerts, code scanning results and secret scanning detections
• C. Catalog of repository issues labeled for security
• D. Organization audit logs and SAML SSO configuration

Question 6

Which GitHub feature categorizes repositories to improve discovery and help contributors find related projects?

• A. GitHub Explore
• B. Repository labels
• C. Repository topics
• D. GitHub Projects

Question 7

How does a GitHub issue template differ from an issue form in terms of supporting structured required inputs?

• A. Issue forms are only available in public repositories
• B. Issue templates are for pull requests and issue forms are for issues
• C. Template is Markdown guidance and form is YAML with structured required fields

Question 8

Which features are available only in the new GitHub Projects and not in Projects Classic? (Choose 2)

• A. Projects supports columns and cards
• B. Table and roadmap views with advanced automation
• C. Insights available in new Projects
• D. Copilot Chat in boards
• E. Project templates only in Projects Classic

Question 9

Which feature is exclusive to GitHub Desktop and not available on GitHub.com?

• A. Create a pull request
• B. View repository insights and traffic analytics
• C. Interactive commit and branch graph view
• D. Create new repositories

Question 10

Which events can trigger a GitHub Actions workflow run, including pushes, manual runs, a schedule that runs every 45 minutes, and REST API calls?

• A. Only commits to the default branch can start a workflow
• B. Workflows can run only when a repository administrator uses the “Run workflow” button
• C. Pushes, manual runs, schedules, and REST API calls can all start a workflow run
• D. A GitHub App webhook is required because workflows cannot be started by schedules or the REST API

GitHub Foundations Certification Exam Answers

Fine more GitHub certification exams on certificationexams.pro and on Udemy

Question 1

In the GitHub Network graph, what is the maximum number of most recently updated branches that can be displayed?

• B. Up to 120 branches

The correct option is Up to 120 branches.

In the GitHub Network graph, the view is capped to show only the most recently updated branches so the visualization remains responsive and understandable even in repositories with many branches. This cap helps ensure performance and keeps the graph readable by focusing on recent activity.

The option Up to 90 branches is incorrect because the Network graph can display more branches than this and choosing it would underestimate the supported limit.

The option Up to 60 branches is incorrect for the same reason since the interface supports a higher cap and this number is too low.

Exam Tip

When a question mentions a UI limit, look for qualifiers such as up to and most recently updated and choose the number that aligns with a realistic product cap rather than a rounded guess.

Question 2

Under what conditions can a GitHub Actions workflow invoke a reusable workflow from the same repository or from a different repository?

• B. Same repository or allowed public repository or private repository with access

The correct option is Same repository or allowed public repository or private repository with access.

GitHub Actions supports reusable workflows that are defined with the workflow_call trigger. A workflow in one repository can call a reusable workflow in the same repository, in a different repository that is public, or in a private repository when the caller has been granted the necessary access through repository or organization settings. This aligns with the platform design that enables cross repository reuse when permissions are configured correctly.

Only in a public repository is incorrect because you can also call a reusable workflow in the same repository and you can call one in a private repository if access is granted.

Only when both repositories are in the same organization is incorrect because calls to reusable workflows in public repositories can work across organizations and private reuse can work as well when access is explicitly allowed.

Only in the same repository is incorrect because GitHub Actions supports calling reusable workflows across repositories when the target repository is public or when private access has been configured.

Exam Tip

Look for language that mentions workflow_call along with access or permissions. Answers that restrict reuse to a single repository or to the same organization are usually too narrow for GitHub Actions.

Question 3

In a GitHub Discussions thread using the question and answer format, how can a moderator highlight the reply that resolves the question for readers?

• B. Mark the reply as the accepted answer

The correct option is Mark the reply as the accepted answer.

In a GitHub Discussion that uses the question and answer format, a moderator or maintainer can choose the single reply that resolves the question. GitHub then highlights that reply with a check and elevates it so readers can quickly find the solution.

Convert the discussion to an issue is a different workflow that creates or links an issue and it does not highlight any reply as solving the discussion.

Pin the reply at the top is not supported for individual replies in Discussions since pinning applies to entire discussions or issues rather than to a single reply.

Exam Tip

Look for options that use the same wording as the product UI. Terms like mark as answer or accepted answer usually indicate the Q and A resolution feature rather than unrelated actions.

Question 4

Which GitHub Enterprise Server feature enforces deployment protection rules for private and internal repositories?

• B. GitHub Actions environments

The correct option is GitHub Actions environments.

On Enterprise Server, GitHub Actions environments provide deployment protection rules that gate deployments to private and internal repositories. You can require reviewers, set wait timers, manage environment secrets, and restrict which branches or tags can deploy to an environment. These protections are evaluated at deployment time so a workflow cannot deploy until all rules are satisfied.

GitHub Advanced Security focuses on code scanning, secret scanning, and supply chain security features. It does not enforce deployment approvals or environment gates for workflows.

Protected branches control merge and push policies on branches through rules like required reviews and status checks. They do not manage deployment approvals or environment-specific protections for workflows.

GitHub Connect links Enterprise Server with GitHub Enterprise Cloud to enable features such as data and feature integration. It does not provide deployment protection rules for repositories.

Exam Tip

When a question mentions deployment approvals or wait timers think environments in Actions. When it focuses on merge or push rules think branch protection. Map the workflow stage to the feature that controls it.

Question 5

Which information is displayed on the Security tab in a GitHub repository?

• B. Unified dashboard of dependency alerts, code scanning results and secret scanning detections

The correct option is Unified dashboard of dependency alerts, code scanning results and secret scanning detections.

The Security tab in a repository is a centralized place to monitor and manage security signals. It brings together Dependabot dependency alerts, code scanning alerts, and secret scanning detections so maintainers can review issues and start remediation from one location.

Insights traffic and clone analytics is incorrect because traffic and clone data are shown in the Insights area rather than in Security.

Catalog of repository issues labeled for security is incorrect because issues appear in the Issues tab and labels do not move them into the Security tab.

Organization audit logs and SAML SSO configuration is incorrect because these are organization level features found in organization settings rather than in a repository Security tab.

Exam Tip

Map features to the right GitHub area. If you see vulnerabilities code scanning or secrets think Security. If you see traffic or clones think Insights. If you see authentication or audit logs think Organization settings.

Question 6

Which GitHub feature categorizes repositories to improve discovery and help contributors find related projects?

• C. Repository topics

The correct option is Repository topics.

Repository topics let maintainers add searchable keywords to a repository so related projects can be grouped together. These topics surface in search and browsing which helps contributors quickly find similar work.

GitHub Explore helps users discover projects through curated collections and recommendations, yet it does not allow maintainers to categorize their own repositories with tags, so it is not the feature used to classify repositories.

Repository labels organize issues and pull requests within a repository, not the repository itself, so they do not categorize repositories for discovery.

GitHub Projects is a planning and tracking tool for tasks and roadmaps, and it does not classify repositories for search or browsing.

Exam Tip

When the question asks about improving discovery at the repository level, look for features that add searchable metadata to the repository itself. Topics classify repositories while labels classify issues and pull requests.

Question 7

How does a GitHub issue template differ from an issue form in terms of supporting structured required inputs?

• C. Template is Markdown guidance and form is YAML with structured required fields

The correct option is Template is Markdown guidance and form is YAML with structured required fields.

Markdown files in the .github/ISSUE_TEMPLATE directory provide guidance and suggested sections to help reporters share useful information. They are free text and do not enforce mandatory inputs.

YAML definitions in the same directory can render an interactive web form for creating an issue. These definitions support typed fields such as input, textarea, checkboxes, and dropdowns. They can mark fields as required which enforces structured input before submission.

Issue forms are only available in public repositories is incorrect because forms are supported in public, private, and internal repositories on GitHub.com, subject to normal permissions.

Issue templates are for pull requests and issue forms are for issues is incorrect because templates exist for both issues and pull requests. Forms are a specific YAML based format for issues only and pull requests continue to use Markdown templates.

Exam Tip

Look for the keywords YAML and required fields to identify issue forms. Look for Markdown guidance to identify issue templates.

Question 8

Which features are available only in the new GitHub Projects and not in Projects Classic? (Choose 2)

• B. Table and roadmap views with advanced automation
• C. Insights available in new Projects

The correct options are Insights available in new Projects and Table and roadmap views with advanced automation.

Insights available in new Projects is a capability introduced with the modern Projects experience that provides built in charts and metrics directly on a project so teams can track progress and trends without exporting data. It supports configurable visualizations that are driven by project fields and filters which was not available in Projects Classic.

The capabilities captured by Table and roadmap views with advanced automation distinguish the new Projects because it offers a spreadsheet like table and a timeline style roadmap view and it includes workflow rules that automatically keep fields and statuses in sync as issues and pull requests change.

Projects supports columns and cards is not unique to the new Projects because it describes the classic project board pattern that both offerings can represent as a board view. Projects Classic has been sunset which makes this framing less likely to appear on newer exams.

Copilot Chat in boards is incorrect because there is no embedded chat experience on project boards in the new Projects.

Project templates only in Projects Classic is incorrect because the new Projects also provides templates to start projects quickly so templates are not exclusive to the classic product.

Exam Tip

When you see wording that asks what is unique or only in a product compare the features across versions in your head and confirm which ones exist exclusively in the newer offering.

Question 9

Which feature is exclusive to GitHub Desktop and not available on GitHub.com?

• C. Interactive commit and branch graph view

The correct capability is Interactive commit and branch graph view.

This is a feature of GitHub Desktop that provides a rich visual history where you can browse commits, follow branches, and compare changes in a local client experience. It lets you interact with the commit graph as part of your desktop workflow which is different from the web interface on GitHub.com.

Create a pull request is available on GitHub.com and is a core part of the web workflow for proposing and reviewing changes.

View repository insights and traffic analytics is provided on GitHub.com where you can access graphs for traffic, clones, and other repository metrics.

Create new repositories is supported on GitHub.com where you can start a repository from the web interface.

Exam Tip

When a question contrasts GitHub Desktop with GitHub.com, map features to where they live. Web focused actions like pull requests, insights, and creating repositories belong on GitHub.com while interactive visualizations and local Git workflows point to Desktop.

Question 10

Which events can trigger a GitHub Actions workflow run, including pushes, manual runs, a schedule that runs every 45 minutes, and REST API calls?

• C. Pushes, manual runs, schedules, and REST API calls can all start a workflow run

The correct option is Pushes, manual runs, schedules, and REST API calls can all start a workflow run.

GitHub Actions supports push events on any branches or tags when you configure filters as needed. Manual runs are enabled with the workflow_dispatch event from the Run workflow button or by calling the REST API. Scheduled workflows use cron and can be configured to run every forty five minutes. The REST API can also start runs by invoking workflow dispatch or repository dispatch.

Only commits to the default branch can start a workflow is wrong because workflows can run on many events and pushes can be filtered to any branches or tags rather than only the default branch.

Workflows can run only when a repository administrator uses the “Run workflow” button is wrong because manual runs are not limited to administrators and workflows can also start from pushes, schedules, or the REST API.

A GitHub App webhook is required because workflows cannot be started by schedules or the REST API is wrong because schedules are supported natively and the REST API can trigger workflows without a GitHub App.

Exam Tip

Match events in the prompt to the on keys in workflows such as push, workflow_dispatch, schedule, and repository_dispatch and confirm that a REST API endpoint exists to trigger them.

Cameron McKenzie is an AWS Certified AI Practitioner, Machine Learning Engineer, Solutions Architect and author of many popular books in the software development and Cloud Computing space. His growing YouTube channel training devs in Java, Spring, AI and ML has well over 30,000 subscribers.