# GitHub GH-500 practice exams

> GH-500 practice exams: 290 questions in 5 timed tests covering Describe GitHub Security suites. Every answer explained, with a score for each domain.

Page: https://devopscodelab.com/exams/github-gh-500/

290 questions in 5 timed practice tests. Each test has about 61 questions and a 100-minute limit. The pass mark is 70%. Results are split across the 6 exam domains.

## Exam at a glance

| Setting | Value |
| --- | --- |
| Practice tests | 5 |
| Questions in total | 290 |
| Questions per test | About 61 |
| Time limit per test | 100 minutes |
| Pass mark | 70% |
| Question types | Single answer and multiple answer (30 multiple-answer questions) |
| Level | Associate |
| Category | DevOps & Cloud Native |

These are the settings of our practice tests. Check the official GitHub exam page for the current format before you book.

## Domains and weights

| Domain | Weight | Questions in our bank |
| --- | --- | --- |
| Describe GitHub Security suites, features, and ecosystem | 19% | 55 |
| Configure and use Secret Protection | 19% | 55 |
| Configure and use supply chain security | 18% | 52 |
| Configure and use Code Security | 13% | 38 |
| Security operations: best practices, prioritization, and remediation | 18% | 52 |
| GitHub Security suites administration | 13% | 38 |

## Price and access

- GH-500 practice exams: $12.99 for 12 months of access.
- Free mini exam: 15 questions with explanations (free account): https://devopscodelab.com/app/exams/github-gh-500/mini/
- All-Access subscription includes every exam: https://devopscodelab.com/pricing/
- 10 free questions with answers: https://devopscodelab.com/exams/github-gh-500/free-practice-questions/

## Sample questions

### Question 1 of 3

A maintainer of a public open source repository on GitHub.com asks which security features they can use without buying any GitHub security product. Which answer is correct?

- A. Code scanning is free for public repositories, but secret scanning only works after the owner joins the secret scanning partner program
- B. Secret scanning with push protection, CodeQL code scanning and Dependabot alerts are all available at no cost for public repositories
- C. Only Dependabot alerts are free, because secret scanning and code scanning require GitHub Secret Protection and GitHub Code Security licenses
- D. Secret scanning is free for public repositories, but CodeQL analysis requires an enterprise account with a Code Security license

**Answer:** B

**Explanation:** GitHub provides secret scanning, push protection, code scanning with CodeQL, dependency review and Dependabot features for public repositories at no charge. The licensing requirements apply to private and internal repositories owned by organizations. The partner program is for token issuers that want to receive leaked credentials, not something a repository owner joins, and CodeQL on public repositories does not need an enterprise license.

### Question 2 of 3

A developer reports that the repository's Security tab shows code scanning alerts, but the same developer cannot see any secret scanning alerts even though the security team says several exist. The developer has the Write role. What is the MOST likely reason?

- A. Secret scanning alerts are hidden until a validity check has confirmed that the detected secret is still active
- B. Writers see only alerts for their own commits; the full list is for admins, security managers and granted users
- C. Secret scanning alerts appear only in the organization-level security overview and never in the repository Security tab
- D. Secret scanning alerts are shown only after the commit author acknowledges the email notification about the alert

**Answer:** B

**Explanation:** Because exposed credentials are sensitive, writers and maintainers can directly view secret scanning alerts only for their own commits, while the full alert list is limited to repository admins, organization owners, security managers and users or teams granted access. Validity checks add status information but do not gate visibility. Alerts do appear in the repository Security tab, and visibility does not depend on acknowledging an email.

### Question 3 of 3

A developer is blocked by push protection for a test credential that is intentionally fake and stored in a test fixture. The repository does not use delegated bypass. What should the developer do to complete the push in the documented way?

- A. Push the commit to a fork first and open a pull request, because push protection does not evaluate pull requests from forks
- B. Follow the URL in the push error, choose the reason that the secret is used in tests, and push again within the allowed window
- C. Ask a repository admin to disable secret scanning temporarily, push the commit, and then turn secret scanning back on
- D. Amend the commit to rename the file with a .test extension so that push protection ignores files used by test frameworks

**Answer:** B

**Explanation:** When delegated bypass is not configured, a contributor can bypass a block by visiting the link in the error message, selecting a reason such as used in tests, and pushing again. File extensions do not exempt content from push protection. Disabling secret scanning is a heavy-handed change that removes protection for everyone, and a fork-based route does not avoid the scan of the content being pushed.


## Study plans

### Two weeks

1. Day 1: take practice test 1 in exam mode to get a baseline.
2. Days 2 to 5: domain mode on Describe GitHub Security suites, features, and ecosystem and Configure and use Secret Protection, the two most heavily weighted domains.
3. Day 6: practice test 2 in exam mode, then the mistakes quiz.
4. Days 7 to 12: practice tests 3 to 5, one every other day, each followed by its mistakes quiz.
5. Days 13 and 14: final mode. Book the exam when your readiness stays above the pass mark.

### Four weeks

1. Week 1: one practice test in practice mode, reading every explanation. Note your two lowest domains.
2. Week 2: domain mode on those two domains, then a second practice test in exam mode.
3. Week 3: practice tests 3 and 4 in exam mode, with the mistakes and flagged quizzes after each.
4. Week 4: practice test 5 and final mode until your readiness holds above the pass mark.

## Questions about the GH-500 practice exams

**Are these real GH-500 exam questions?**

No. We write every question ourselves and map it to the published GH-500 exam objectives. We do not use leaked or recalled questions.

**Do the time limit and pass mark match the official exam?**

They match the settings of our practice tests. Exam providers change their format from time to time, so check the official exam page before you book.

**Can I try it before I pay?**

Yes. The free mini exam has 15 questions with full explanations and needs no account.

**How long do I keep access?**

A single-exam purchase gives you 12 months of access. All-Access includes this exam for as long as your subscription runs.

**What happens after I finish a test?**

You get a score, a pass or fail against the pass mark, a score per domain and every answer with its explanation.

Last updated November 2026.

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