GitHub Foundations Practice Exam
Validates foundational knowledge of GitHub — repositories, collaboration, issues/PRs, Actions basics, and the GitHub ecosystem.
Practice 709 exam-style GitHub Foundations questions with full answer explanations, then take timed mock exams that score like the real thing.
What the GitHub Foundations exam covers
- Introduction to GitHub155 questions
- Working with Repositories170 questions
- Collaboration Features171 questions
- Modern Development213 questions
Free GitHub Foundations sample questions
A sample of 10 questions with answers and explanations. Sign up free to practice all 709.
-
What is a Git repository?
- AA DNS zone
- BA project's version-controlled collection of files and its complete change historyCorrect
- CA container image
- DA subnet
✓ Correct answer: BGit is the distributed version control system that underlies GitHub. Commits represent immutable snapshots of code changes with unique SHA hashes. Branches enable parallel development lines. Understanding Git concepts is fundamental to using GitHub effectively for version control and collaboration.
Why the other options are wrong- AA DNS zone is incorrect because DHCP, DNS, VLAN, and IP configuration are network infrastructure protocols and concepts unrelated to GitHub Actions, Git version control, or GitHub platform features.
- CA container image is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
- DA subnet is incorrect because DHCP, DNS, VLAN, and IP configuration are network infrastructure protocols and concepts unrelated to GitHub Actions, Git version control, or GitHub platform features.
-
Where can an organization owner review how many GitHub Actions minutes and storage have been consumed to manage cost?
- AThe organization's billing and plans / usage settingsCorrect
- BA pull request's Files changed tab
- CThe .gitignore file
- DThe repository's README file
✓ Correct answer: AActions are reusable automation units that encapsulate common tasks in workflows. They can be implemented as JavaScript-based actions, Docker container actions, or composite actions that combine multiple steps. The GitHub Actions marketplace provides thousands of pre-built actions for common tasks like checkout, caching, and deployment.
Why the other options are wrong- BA pull request's Files changed tab is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
- CThe .gitignore file is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
- DThe repository's README file is incorrect because README files are documentation artifacts, gists are code snippets, stars are social features for marking favorite repositories, and printers are hardware devices - none are GitHub Actions or Git functionality.
-
Reviewers are overwhelmed by huge pull requests that mix many unrelated changes. Which collaboration design practice most improves review quality?
- AKeep pull requests small and focused on a single concernCorrect
- BSkip review and merge directly to main
- CDisable required reviewers to merge faster
- DCombine an entire quarter of work into one PR
✓ Correct answer: APull requests represent proposed changes in GitHub, enabling collaborative code review. A pull request is created from a source branch and targets a destination branch. Pull requests support discussion, approval workflows, and automated checks before merging, providing control over code quality and change management.
Why the other options are wrong- BSkip review and merge directly to main is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
- CDisable required reviewers to merge faster is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
- DCombine an entire quarter of work into one PR is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
-
Which event keyword schedules a GitHub Actions workflow to run on a recurring cron timer?
- Arelease
- Bissues
- Cworkflow_dispatch
- DScheduleCorrect
✓ Correct answer: DGitHub Actions workflows are the fundamental automation mechanism in GitHub, defined through YAML configuration that specifies triggers, jobs, and steps. Workflows execute on events like pushes, pull requests, or manual dispatch, providing CI/CD capabilities integrated directly into repositories. Understanding workflow structure and configuration is essential for GitHub Actions certification.
Why the other options are wrong- Arelease is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
- Bissues is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
- Cworkflow_dispatch is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
-
What does enabling dependency review on a pull request show reviewers?
- AThe number of stars each dependency has
- BA live chat with the dependency maintainers
- CThe IP addresses of dependency authors
- DThe security impact of dependency changes, including newly introduced known vulnerabilities, before mergingCorrect
✓ Correct answer: DPull requests represent proposed changes in GitHub, enabling collaborative code review. A pull request is created from a source branch and targets a destination branch. Pull requests support discussion, approval workflows, and automated checks before merging, providing control over code quality and change management.
Why the other options are wrong- AThe number of stars each dependency has is incorrect because README files are documentation artifacts, gists are code snippets, stars are social features for marking favorite repositories, and printers are hardware devices - none are GitHub Actions or Git functionality.
- BA live chat with the dependency maintainers is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
- CThe IP addresses of dependency authors is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
-
Which feature lets a project signal that it welcomes newcomers by tagging beginner-friendly tasks?
- ALabels such as good first issue applied to issuesCorrect
- BBranch protection rules on the default branch
- CSecret scanning push protection
- DRequired status checks on pull requests
✓ Correct answer: AThis concept represents a key capability within GitHub Actions or GitHub's version control system. Proper understanding ensures effective automation and collaboration workflows. GitHub certification requires mastery of core platform features and best practices.
Why the other options are wrong- BBranch protection rules on the default branch is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
- CSecret scanning push protection is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
- DRequired status checks on pull requests is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
-
Which best describes what happens when you fork a repository compared to using 'Use this template'?
- AA fork copies the full history and keeps a link to the upstream repository, while a template generates an independent repository without that history or linkCorrect
- BA fork and a template both keep the original commit history and stay linked to the source
- CA fork creates an independent repository, while a template stays linked to the original
- DBoth forking and templating require deleting the original repository first
✓ Correct answer: AThis concept represents a key capability within GitHub Actions or GitHub's version control system. Proper understanding ensures effective automation and collaboration workflows. GitHub certification requires mastery of core platform features and best practices.
Why the other options are wrong- BA fork and a template both keep the original commit history and stay linked to the source is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
- CA fork creates an independent repository, while a template stays linked to the original is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
- DBoth forking and templating require deleting the original repository first is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
-
Which TWO views are available under a repository's Insights to help understand project activity? (Choose TWO)
- AThe Traffic view, showing page views and clones over the recent periodCorrect
- BThe Pulse view, summarizing recent merged PRs, open issues, and activityCorrect
- CA view that rewrites the repository's commit history
- DA view that automatically deletes inactive branches
✓ Correct answer: A, BThe Pulse view, summarizing recent merged PRs, open issues, and activity. These answers correctly identify valid GitHub Actions features or patterns. Both represent correct implementations for the scenario described in the question.
Why the other options are wrong- CA view that rewrites the repository's commit history is incorrect because it does not represent a valid GitHub feature or pattern.
- DA view that automatically deletes inactive branches is incorrect because it does not represent a valid GitHub feature or pattern.
-
When you fork a public repository on GitHub, what is the relationship between your fork and the original repository?
- AYour fork is a separate copy under your account, linked to the original as its upstream/parent for syncing and pull requestsCorrect
- BYour fork becomes the new official version and the original is hidden
- CYour fork shares the same commit history as a live mirror, so any commit you make appears in the original instantly
- DYour fork is read-only and you cannot make any commits to it
✓ Correct answer: AGit is the distributed version control system that underlies GitHub. Commits represent immutable snapshots of code changes with unique SHA hashes. Branches enable parallel development lines. Understanding Git concepts is fundamental to using GitHub effectively for version control and collaboration.
Why the other options are wrong- BYour fork becomes the new official version and the original is hidden is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
- CYour fork shares the same commit history as a live mirror, so any commit you make appears in the original instantly is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
- DYour fork is read-only and you cannot make any commits to it is incorrect because it incorrectly claims a feature or capability does not exist when GitHub Actions or Git actually supports it.
-
A developer wants to make a quick text edit to a file in a repository directly in the browser without cloning, and does NOT need to run or build the code. Which tool is the most appropriate?
- AThe github.dev web-based editorCorrect
- BA full GitHub Codespace
- CGitHub Actions
- DGitHub Packages
✓ Correct answer: AThe github.dev web-based editor.
Why the other options are wrong- BA full GitHub Codespace is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario. GitHub Actions is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
- CThis concept represents a key capability within GitHub Actions or GitHub's version control system. Proper understanding ensures effective automation and collaboration workflows. GitHub certification requires mastery of core platform features and best practices.
- DGitHub Packages is incorrect because it does not represent the appropriate GitHub feature, configuration, or best practice for this scenario.
GitHub Foundations practice exam FAQ
How many questions are in the GitHub Foundations practice exam on CertGrid?
CertGrid has 709 practice questions for GitHub Foundations, covering 4 exam domains. The real GitHub Foundations exam has about 60 questions.
What is the passing score for GitHub Foundations?
The GitHub Foundations exam passing score is 700, and you have about 90 minutes to complete it. CertGrid scores your practice attempts the same way so you know when you are ready.
Are these official GitHub Foundations exam questions?
No. CertGrid is an independent practice platform. Questions are written to mirror the style and concepts of GitHub Foundations, with full explanations, but they are not official or copied vendor exam items. They are original practice questions designed to help you genuinely learn the material.
Can I practice GitHub Foundations for free?
Yes. You can start practicing GitHub Foundations for free with daily practice and sample questions. Paid plans unlock full timed exams, complete explanations, and domain analytics.