Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.

AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by Microsoft
Exam Format
Registration
Validity
Skills this practice test covers
- Turn on secret scanning and push protection, and choose a response to a leaked secret.
- Configure Dependabot alerts, security updates and rules, and group updates in a dependabot.yml file.
- Add a dependency review workflow that checks licenses and severity on every pull request.
- Set up CodeQL code scanning in GitHub Actions, or upload SARIF results from a third-party tool.
- Read a code scanning alert, follow its data flow, and decide whether to fix or dismiss it.
- Enforce CodeQL and dependency review across repositories with repository rulesets.
Explore related topics
GH-500 exam content
5 domains · 40 topics · 224 of 232 questions sorted by domain
Describe the GHAS security features and functionality15%32 questions
This domain sets out what each GHAS feature does and how the features work together. Candidates contrast the free features for open source projects with what GHAS adds on GitHub Enterprise Cloud (GHEC) and GitHub Enterprise Server (GHES), and explain who acts on an alert.
Skills tested
- Separate the features open source projects get automatically from those that need GHAS with GHEC or GHES.
- Contrast secret scanning with code scanning, and show how both work with Dependabot across the development life cycle.
- Describe what Security Overview shows and which roles can see each type of alert.
- Explain the risk of ignoring an alert and the developer's role when one appears.
Questions by topic
- Describe the features and benefits of Security Overview5
- Differentiate the security features that come automatically for open source projects, and what features are available when GHAS is paired with GHEC or GHES4
- Describe the differences between secret scanning and code scanning4
- Contrast a security scenario with isolated security review and an advanced scenario, with security integrated into each step of the software development life cycle5
- Explain the role of a developer when they discover a security alert5
- Describe the differences in access management to view alerts for different security features4
- Integrated security in SDLC2
- Choose how to act on alerts from GHAS2
- Describe how code scanning can be configured to identify and remediate vulnerabilities earlier (scanning upon pull request)1
Configure and use secret scanning15%32 questions
Secret scanning finds tokens, keys and other credentials committed to a repository. Candidates describe push protection and validity checks, pick a response to an alert, and change the default behavior with alert recipients, excluded files and custom patterns.
Skills tested
- Describe how push protection blocks a commit that contains a secret.
- Explain validity checks and how they show whether a leaked secret is still active.
- Compare secret scanning in public and private repositories, and enable it for private ones.
- Configure who receives secret scanning alerts, and exclude files from scanning.
- Enable custom secret scanning for a repository.
Questions by topic
- Describe push protection5
- Describe validity checks4
- Enable custom secret scanning for a repository5
- Exclude certain files from being scanned for secrets4
- Configure the recipients of a secret scanning alert (also includes how to provide access to members and teams other than admins)4
- Pick an appropriate response to a secret scanning alert5
- Describe secret scanning2
- Contrast secret scanning availability for public and private repositories2
- Determine if a given user role will see secret scanning alerts and how they will be notified1
Configure and use Dependabot and Dependency Review35%82 questions
The largest domain follows a vulnerable dependency from detection to fix. Candidates explain the dependency graph, SBOMs and the GitHub Advisory Database, then configure Dependabot alerts, security updates, Dependabot rules and dependency review workflows.
Skills tested
- Explain how the dependency graph is built from manifest files and checked against the GitHub Advisory Database.
- Describe a Software Bill of Materials (SBOM) and the SPDX format GitHub uses for it.
- Write a valid dependabot.yml file that groups security updates.
- Create a Dependabot rule that auto-dismisses low severity alerts until a patch is available.
- Build a dependency review workflow in GitHub Actions with license checks and a custom severity threshold.
Official topics
- Describe tools for managing vulnerabilities in dependencies
- Enable and configure tools for managing vulnerable dependencies
- Identify and remediate vulnerable dependencies
Configure and use Code Scanning with CodeQL25%47 questions
This domain is about finding vulnerable code before it ships. Candidates run CodeQL in GitHub Actions or a third-party CI tool, choose when scans run, upload SARIF results, and read, troubleshoot or dismiss the alerts.
Skills tested
- Choose a trigger for a code scanning workflow, such as a schedule or a pull request on specific files.
- Edit the default workflow template to fit an active, open source, production repository.
- Upload third-party results through the SARIF endpoint and explain why a SARIF category is set.
- Troubleshoot a failing CodeQL workflow by creating or changing its custom configuration.
- Follow data flow with the show paths view and decide whether an alert needs to be dismissed.
Questions by topic
- Troubleshoot a failing code scanning workflow using CodeQL, including creating or changing a custom configuration in the CodeQL workflow11
- Upload 3rd party SARIF results via the SARIF endpoint4
- Follow the data flow through code using the show paths experience4
- Choose a triggering event for a given development pattern (for example, in a pull request and for specific files)5
- Determine if and why a code scanning alert needs to be dismissed4
- Contrast how to implement CodeQL analysis in a GitHub Actions workflow versus a third-party CI tool5
- Describe how to view code scanning results from CodeQL analysis4
- Explain the purpose of defining a SARIF category5
- Use code scanning with third-party tools4
- Describe how CodeQL analyzes code and produces results, including differences between compiled and interpreted language1
Describe GitHub Advanced Security best practices, results, and how to take corrective measures10%31 questions
The smallest domain turns results into decisions. Candidates describe alerts with CVE and CWE identifiers, document dismissals, choose CodeQL query suites, and use repository rulesets and pull request checks to catch problems earlier.
Skills tested
- Describe an alert with its CVE and CWE identifiers and list possible fixes.
- Document why an alert is closed or dismissed, and base the decision on data.
- Compare the default CodeQL query suites and how CodeQL handles compiled and interpreted languages.
- Enforce CodeQL and dependency review workflows with repository rulesets.
- Split security work between the development team and the security team.
Questions by topic
- Explain how CodeQL & Dependency Review workflows can be enforced with Repository Rulesets5
- Describe how CodeQL analyzes code and produces results, including differences between compiled and interpreted language3
- Describe the default CodeQL query suites5
- Integrated security in SDLC1
- Use a Common Vulnerabilities and Exposures (CVE) and Common Weakness Enumeration (CWE) to describe a GitHub Advanced Security alert and list potential remediation6
- Describe the decision-making process for closing and dismissing security alerts (documenting the dismissal, making a decision based on data)5
- Describe how code scanning can be configured to identify and remediate vulnerabilities earlier (scanning upon pull request)2
- Describe how the severity threshold for code scanning pull request status checks can be changed2
- Explain how filters and sorting can be used to prioritize secret scanning remediation (validity:active)2
Requirements
- No formal prerequisites: anyone can book the exam.
- Recommended: intermediate-level experience administering GitHub Enterprise.
- Recommended: hands-on experience securing software development workflows, and a solid grasp of GitHub's security features.
About the GH-500 exam
For developers, administrators and IT staff who protect code on GitHub Enterprise, GH-500 is the exam on GitHub Advanced Security (GHAS). It covers secret scanning, Dependabot with dependency review, and code scanning with CodeQL. It also asks how to act on the alerts these tools raise. Microsoft delivers the exam, while GitHub maintains the exam and the certification. Passing earns the GitHub Advanced Security certification, which stays valid for two years.
Dependabot and Dependency Review is the largest domain, and it also has the most questions in the PlanetCert practice test. The explanations help where two features sound alike: a Dependabot alert reports a vulnerable dependency already in the repository, while dependency review checks the dependencies a pull request would add. Study Mode suits the code scanning questions, where a workflow file or a SARIF upload needs a careful read. Brainy AI Assistant can explain why a CodeQL alert fired or walk through a dependabot.yml file line by line.
How to earn the certification
- Earns
- GitHub Advanced SecurityIntermediate
The certification stays valid for two years.
- Before
- GH-900 GitHub Foundations
Optional. GitHub's entry-level exam, for candidates who are new to the platform.
- GH-200 GitHub Actions
Optional. It teaches GitHub Actions in depth, and code scanning and dependency review run as Actions workflows.
- GH-900 GitHub Foundations
How to prepare for GH-500
- 1
Switch on GHAS in a test repository
Use a public repository, which gets many of these features automatically, or a test organization with GHAS. Turn on secret scanning, push protection, Dependabot alerts and code scanning, and note what each one reports.
- 2
Set off each alert type
Push a sample secret to see push protection respond, add an outdated package to raise a Dependabot alert, and commit a known flaw for CodeQL to find. Then resolve each alert the way the objectives describe.
- 3
Give dependencies the most hours
Dependabot and Dependency Review is the largest domain. Write a dependabot.yml that groups security updates, add a Dependabot rule for low severity alerts, and build a dependency review workflow with license checks.
- 4
Repair a failing CodeQL workflow
Change a workflow's triggers, add a custom configuration and upload a SARIF file from another tool. When a run fails, read its log and fix it, because troubleshooting a failing workflow is an objective.
- 5
Finish with alert triage questions
Take the GH-500 practice test in Timed Mode, then review every question about dismissing or prioritizing alerts. Ask Brainy AI Assistant to compare two answers that look alike, such as two dismissal reasons.
Start a timed GH-500run
Microsoft Learn offers Course GH-500T00-A: GitHub Advanced Security, and the self-paced learning paths GitHub Advanced Security Part 1 of 2 and Part 2 of 2.
Who GH-500 is for
- Developers who fix the security alerts that GitHub raises on their code and pull requests.
- GitHub Enterprise administrators who enable and tune GHAS for many repositories.
- Application security and DevSecOps engineers who own code and supply chain security.
Typical job titles: DevSecOps engineer · Application security engineer · GitHub Enterprise administrator · Software developer · Security automation engineer
GH-500 glossary
18 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- CodeQL
- GitHub's code analysis engine, which turns code into a database and runs queries on it to find security flaws.
- Common Vulnerabilities and Exposures (CVE)
- Public identifiers for individual known vulnerabilities, such as one flaw in one version of a package.
- Common Weakness Enumeration (CWE)
- A public catalog of software weakness types, used to name the kind of flaw an alert describes.
- Default query suites
- The standard sets of CodeQL queries that code scanning runs; larger suites such as security-extended add more queries.
- Dependabot alerts
- Notices that a repository depends on a package version with a known vulnerability.
- Dependabot security updates
- Pull requests that Dependabot opens to move a vulnerable dependency to a version that fixes the flaw.
- dependabot.yml
- The Dependabot configuration file that sets which package ecosystems to check, on what schedule, and how update pull requests are grouped.
- Dependency graph
- GitHub's list of the packages a repository depends on, built from its manifest and lock files.
- Dependency Review
- A pull request check that lists the dependencies a change adds, removes or updates, and can fail when a new one is vulnerable.
- GitHub Advisory Database
- GitHub's database of known security vulnerabilities. Dependabot alerts come from matching the dependency graph against it.
- GitHub Enterprise Server
- The self-hosted edition of GitHub that an organization runs on its own infrastructure, often shortened to GHES.
- Push protection
- A secret scanning setting that blocks a push when it contains a supported secret, before the secret reaches the repository.
- Repository Rulesets
- Rules that control pushes and merges in a repository, for example by requiring code scanning results before a pull request can merge.
- SARIF
- Static Analysis Results Interchange Format: the standard file format in which code scanning tools report their results.
- Secret scanning
- A GHAS feature that searches a repository for credentials such as tokens and private keys, and raises an alert when it finds one.
- Security Overview
- A view for an organization or enterprise that sums up security alerts and shows which repositories use each feature.
- Software Bill of Materials (SBOM)
- A list of all the components and dependencies in a piece of software; GitHub exports it from the dependency graph in SPDX format.
- Validity checks
- A secret scanning feature that asks the secret's provider whether a found credential still works, so active secrets can be fixed first.