Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
-- [Configure and Use Dependency Management]
In the pull request, how can developers avoid adding new dependencies with known vulnerabilities?
To detect and block vulnerable dependencies before merge, developers should use the Dependency Review GitHub Action in their pull request workflows. It scans all proposed dependency changes and flags any packages with known vulnerabilities.
This is a preventative measure during development, unlike Dependabot, which reacts after the fact.
-- [Use Code Scanning with CodeQL]
When using the advanced CodeQL code scanning setup, what is the name of the workflow file?
Comprehensive and Detailed Explanation:
In the advanced setup for CodeQL code scanning, GitHub generates a workflow file named codeql-analysis.yml. This file is located in the .github/workflows directory of your repository. It defines the configuration for the CodeQL analysis, including the languages to analyze, the events that trigger the analysis, and the steps to perform during the workflow.
-- [Configure and Use Secret Scanning]
How many alerts are created when two instances of the same secret value are in the same repository?
When multiple instances of the same secret value appear in a repository, only one alert is generated. Secret scanning works by identifying exposed credentials and token patterns, and it groups identical matches into a single alert to reduce noise and avoid duplication.
This makes triaging easier and helps teams focus on remediating the actual exposed credential rather than reviewing multiple redundant alerts.
-- [Configure and Use Secret Scanning]
What is a prerequisite to define a custom pattern for a repository?
You must enable secret scanning before defining custom patterns. Secret scanning provides the foundational capability for detecting exposed credentials, and custom patterns build upon that by allowing organizations to specify their own regex-based patterns for secrets unique to their environment.
Without enabling secret scanning, GitHub will not process or apply custom patterns.
-- [Use Code Scanning with CodeQL]
The autobuild step in the CodeQL workflow has failed. What should you do?
If autobuild fails (which attempts to automatically detect how to build your project), you should disable it in your workflow and replace it with explicit build commands, using steps like run: make or run: ./gradlew build.
This ensures CodeQL can still extract and analyze the code correctly.
75 questions covering all exam domains, starting from $20
Exam domains verified against: Official Microsoft GH-500 exam guide, last checked August 2026.
Understand GitHub Security suites and architecture, including how Code Security, Secret Protection, and Supply Chain Security fit together. Learn to navigate the Security Overview and recognize how feature availability differs between public and enterprise repositories.
Explain the differences between prevention-first and gate-based security approaches using GitHub's tools. Design end-to-end secure workflows and use security campaigns to reduce organizational risk.
Identify how vulnerabilities and secrets are detected across the platform. Manage alerts through policies and workflows, and understand the implications of dismissing alerts versus remediating them.
Control who can access and act on alerts using role-based permissions and delegated bypass. Understand supply chain security concepts and track alerts across the full software development lifecycle.
Enable Secret Protection at repository and organization levels and configure its behavior for different repository types. Use Push Protection to prevent secrets at source and manage the alert lifecycle from detection to remediation.
Use dependency and vulnerability management tools to understand supply chain risk. Generate dependency graphs and SBOMs, then detect and prioritize alerts using EPSS scoring and security campaigns.
Sample question from this domain above: Q1
Choose between CodeQL and third-party analysis tools for code scanning. Configure workflows using GitHub Actions, manage scan results and dataflow analysis, and handle SARIF file ingestion.
Prioritize and manage security work at scale using severity rulesets and campaign-based remediation. Apply CVE and CWE knowledge to guide remediation and collaborate across teams with appropriate role assignments.
Enable and configure security features at enterprise, organization, and repository levels. Define policies, roles, and enforcement boundaries, and use APIs for large-scale governance and automation.
Common questions about the exam itself