Microsoft · GH-500
Validates expertise in configuring, managing, and operating GitHub Advanced Security tools including code scanning, secret scanning, and dependency management to secure software development workflows.
Practice Questions
299
≈ 5 practice exams
Duration
100 minutes
Passing Score
Not publicly disclosed
Difficulty
IntermediateLast Updated
Jan 2025
Use this GH-500 practice exam to prepare for GitHub Advanced Security (GH-500) with realistic questions, detailed explanations, and focused study modes. The practice bank includes 299 questions for Microsoft GH-500, so you can review the exam steadily instead of relying on one long cram session.
As you practice, pay extra attention to recurring topics such as GHAS Security Features, Secret Scanning, Dependabot & Dependency Review, Code Scanning with CodeQL, and Security Best Practices. Start with short sessions to identify weak areas, then move into timed quizzes once your accuracy is consistent.
The explanations are especially useful when you want to connect exam wording to the responsibilities and scenarios described in the official certification guidance. Use the free preview first, then unlock the full question bank when you are ready to build a complete study routine.
The GitHub Advanced Security (GH-500) certification validates proficiency in configuring, managing, and operationalizing the full suite of GitHub Advanced Security (GHAS) tools to secure modern software development workflows. Candidates demonstrate mastery across three core security pillars: secret scanning (including push protection and custom patterns), dependency management via Dependabot and Dependency Review, and automated code analysis using CodeQL and third-party SARIF-compatible tools. The exam also covers Security Overview, alert management, and enforcement of security policies through Repository Rulesets and GitHub Actions workflows.
The certification is maintained by GitHub and administered through Microsoft's Pearson VUE testing infrastructure. It was updated in 2025 to reflect a revised seven-domain structure, expanding coverage of GitHub Enterprise configuration and sharpening the weight given to best practices and corrective measures. Holding this credential demonstrates the ability to shift security left—embedding automated vulnerability detection directly into the development lifecycle rather than treating it as a post-deployment concern. The certification is valid for two years from the date of achievement.
The GH-500 exam targets system administrators, software developers, application administrators, and IT professionals who work with GitHub Enterprise Cloud (GHEC) or GitHub Enterprise Server (GHES) and are responsible for securing codebases at scale. Ideal candidates include DevSecOps engineers integrating security gates into CI/CD pipelines, application security specialists managing organizational vulnerability programs, and GitHub administrators enforcing repository and organization-level security policies.
Candidates should have hands-on experience enabling and configuring GHAS features across repositories and organizations, familiarity with GitHub Actions workflows, and an understanding of software supply chain security concepts including dependency graphs, SBOMs, and CVE/CWE classification. The intermediate difficulty level assumes prior GitHub platform experience; this is not an entry-level credential.
Microsoft does not list formal prerequisites for GH-500, but the official audience profile specifies intermediate-level experience with GitHub Enterprise Administration. Candidates are expected to understand GitHub's repository, organization, and enterprise permission model before attempting the exam, as access control questions appear across multiple domains.
Recommended preparation includes practical experience enabling GHAS features on private repositories, working knowledge of GitHub Actions (creating and modifying workflow YAML files), familiarity with CodeQL query suites and SARIF output formats, and experience interpreting Dependabot alerts and dependency graphs. Completing the official Microsoft Learn training course GH-500T00-A: GitHub Advanced Security provides structured coverage of all exam objectives and is the primary recommended prerequisite resource.
The GH-500 exam is delivered through Pearson VUE and includes a 100-minute time limit. The exam is proctored and may include interactive lab components in addition to standard multiple-choice and scenario-based questions. Candidates can experience the question interface in advance via the official exam sandbox at GHCertDemo.starttest.com before scheduling.
The exam is available in English, Spanish, Portuguese (Brazil), Korean, and Japanese. Pricing is approximately $99 USD, varying by country or region of testing. No official passing score is published on the Microsoft Learn certification page; third-party sources cite 700/1000 as a commonly reported threshold, but this should be verified against official communications at time of registration. If a candidate fails, a retake is permitted 24 hours after the first attempt; subsequent retake wait times vary per Microsoft's standard retake policy. A free practice assessment is available on Microsoft Learn (assessment ID 590484996).
Professionals holding the GH-500 certification are positioned for roles such as DevSecOps engineer, application security engineer, GitHub Enterprise administrator, and security-focused software developer. As software supply chain security has become a regulatory and enterprise priority — driven by executive orders, frameworks like SLSA, and incidents targeting dependency ecosystems — the ability to operationalize GHAS tools within existing GitHub workflows is a differentiated and in-demand skill. The certification is relevant across both enterprise cloud environments (GitHub Enterprise Cloud) and self-hosted deployments (GitHub Enterprise Server), broadening its applicability across industries.
Because the credential is issued by GitHub (administered via Microsoft) rather than a generic cloud provider, it signals specific platform expertise to employers already standardized on GitHub for source control and CI/CD. It complements adjacent certifications such as GitHub Actions (GH-200), GitHub Administration (GH-700), and Microsoft's AZ-500 (Azure Security Engineer) for professionals building a security specialization. The two-year validity period requires periodic renewal, keeping certified professionals current with an actively evolving product.
5 sample questions with answers and explanations. The full bank has 299 questions, enough for 5 full-length practice exams.
Preview — answers shown1. DataCloud Corp has multiple development teams with different security requirements and wants to implement custom secret scanning patterns for their proprietary authentication systems. Each team uses different internal API token formats. How should they approach implementing custom secret scanning across their organization?
Explanation
Organizations with diverse authentication systems should implement repository-specific custom secret scanning patterns that are tailored to each team's specific authentication systems and API token formats. This approach allows each team to define patterns that match their proprietary credential formats while avoiding false positives from other teams' different token structures. Repository-specific configuration provides the granular control needed for diverse development environments while ensuring comprehensive coverage of organization-specific credential types.
2. InnovateCode Corporation has implemented secret scanning organization-wide and wants to establish appropriate access controls for security alerts. They have different teams with varying security responsibilities and need to ensure the right people can view and respond to secret exposures. The organization wants to balance security oversight with operational efficiency. How should they configure access to secret scanning alerts?
Explanation
InnovateCode should configure access controls so repository administrators and security teams have automatic access, with additional access granted to specific people or teams as needed. GitHub automatically provides secret scanning alert access to repository administrators, organization owners, and users with custom roles that include security alert permissions. Additional access can be granted through the repository's Advanced Security settings by searching for and adding specific people or teams. This approach ensures that those responsible for security oversight and repository management can respond to alerts while allowing granular access control for other team members who may need visibility for specific projects or responsibilities. This configuration balances security with operational needs by providing appropriate access levels based on roles and responsibilities.
3. CyberGuard Technologies has implemented secret scanning across their organization and wants to establish a continuous improvement process that optimizes their security program based on operational experience and evolving threats. They need to balance security effectiveness with team productivity and developer experience. Which approach best supports continuous improvement of their secret scanning program?
Explanation
CyberGuard should establish regular review cycles that analyze alert patterns, team feedback, detection effectiveness, and industry threat intelligence to optimize their secret scanning program. This continuous improvement approach includes regular assessment of alert accuracy and false positive rates, collection of feedback from development teams about program impact and usability, analysis of detection effectiveness against known credential exposure incidents, and incorporation of emerging threat intelligence about new credential types and attack patterns. The review process should result in configuration adjustments such as pattern refinements, exclusion rule updates, and process improvements that enhance security effectiveness while maintaining developer productivity. This systematic improvement approach ensures that the secret scanning program evolves with both organizational needs and the threat landscape while maintaining team confidence through responsive program management.
4. GlobalTech Enterprises has repositories that contain both production code and extensive test suites with mock credentials and example configurations. They want to implement secret scanning that protects production secrets while avoiding false positives from legitimate test content. How should they configure their secret scanning approach?
Explanation
GlobalTech should use path exclusions in .github/secret_scanning.yml to exclude test directories while maintaining scanning for production code, combined with clear guidelines for test credential management. This approach allows them to maintain comprehensive security coverage for production code while eliminating false positives from test content. The exclusion configuration supports pattern matching to exclude specific test directories, mock data files, and example configuration directories. Additionally, they should establish development guidelines that promote secure test practices such as using environment variables for test configurations, clearly marking test credentials, and using standardized test data that doesn't resemble production credentials. This combined approach maintains security effectiveness while reducing operational overhead from false positives and educating developers about secure testing practices.
5. TechFlow Industries has enabled secret scanning on their organization and receives numerous alerts daily. Their development team is overwhelmed by the volume of notifications and many alerts appear to be false positives from test files and generated content. The security team wants to optimize their configuration to reduce noise while maintaining comprehensive security coverage. How should they configure secret scanning to address these issues?
Explanation
TechFlow should create a .github/secret_scanning.yml file to exclude directories and files that generate false positives from secret scanning. This configuration file allows them to specify paths-ignore patterns to exclude test files, directories with randomly generated content, and other sources of false alerts while maintaining scanning coverage for production code. The file supports special characters like asterisks for pattern matching, enabling flexible exclusion rules. This approach reduces alert fatigue and allows the security team to focus on genuine security threats while preserving comprehensive scanning for actual application code. Completely disabling scanning would eliminate security coverage, while manual review of all alerts doesn't address the root cause of excessive false positives.
Microsoft Certified: Fabric Data Engineer Associate (DP-700)
DP-700 · 819 questions
GitHub Actions (GH-200)
GH-200 · 310 questions
GitHub Administration (GH-100)
GH-100 · 447 questions
GitHub Copilot (GH-300)
GH-300 · 352 questions
Microsoft Certified: Identity and Access Administrator Associate (SC-300)
SC-300 · 489 questions
Microsoft Certified: Fabric Analytics Engineer Associate (DP-600)
DP-600 · 792 questions
$17.99
One-time access to this exam