Pass the Microsoft GitHub Administrator GH-500 Questions and answers with CertsForce

GitHub automatically closes a code scanning alert when the vulnerable code is fixed in the same branch where the alert was generated , usually via a commit inside a pull request . Simply clicking or triaging an alert does not resolve it. The alert is re-evaluated after each push to the branch, and if the issue no longer exists, it is marked as resolved.

The best proactive control is push protection . It scans for secrets during a git push and blocks the commit before it enters the repository.

Other options (like CODEOWNERS or security managers) help with oversight but do not prevent secret leaks.

Making a repo public would increase the risk, not reduce it.

At organization scope, enabling Dependabot alerts broadly applies the feature to the organization's eligible repositories, rather than limiting it solely to private repositories or repositories licensed for the broader GitHub Advanced Security product. Dependabot alerts support public, private, and internal repositories, subject to repository eligibility and applicable organization or enterprise configuration. GitHub's current documentation describes organization-level management as enabling Dependabot alerts across all eligible repositories through security configurations. The feature is distinct from licensed GitHub Code Security or Secret Protection capabilities, so the setting is not restricted merely to repositories where those products are enabled. Consequently, All repositories is the intended answer in the supplied choices, with the practical qualification that GitHub applies the configuration to repositories that are eligible for the feature.

Comprehensive and Detailed Explanation:

When GitHub identifies a vulnerable dependency in a repository with Dependabot alerts enabled, it performs the following actions:​

Generates a Dependabot alert: The alert is displayed on the repository's Security tab, providing details about the vulnerability and affected dependency.​

Notifies repository maintainers: By default, GitHub notifies users with write, maintain, or admin permissions about new Dependabot alerts.​

GitHub Docs

These actions ensure that responsible parties are informed promptly to address the vulnerability.​

To systematically analyze newly introduced source code for security weaknesses, you should configure code scanning. GitHub code scanning can use CodeQL or supported third-party analysis tools and can run automatically when developers push changes or create pull requests. This places vulnerability detection directly into the development workflow rather than depending on manual review. The extended CodeQL query suite broadens the set of queries executed, but it only has an effect after code scanning itself is configured. CODEOWNERS determines who reviews specific paths and does not perform vulnerability analysis. A security policy explains how vulnerabilities should be reported but does not scan source code. Therefore, enabling and properly configuring code scanning is the foundational mechanism for ensuring new code is automatically analyzed.

To exclude specific files or directories from being scanned by secret scanning in GitHub Actions, you can use the paths-ignore: key within your YAML workflow file.

This tells GitHub to ignore specified paths when scanning for secrets, which can be useful for excluding test data or non-sensitive mock content.

Other options listed are invalid:

branches-ignore: excludes branches, not files.

decrypt_secret.sh is not a YAML key.

secret scanning.yml is not a recognized filename for configuration.

When a CodeQL workflow uses a language matrix, the autobuild step attempts to build each compiled language listed in that matrix. This differs from a workflow without a language matrix, where autobuild attempts to build the supported compiled language with the greatest number of source files in the repository. A matrix is therefore useful when a repository contains multiple languages that require separate CodeQL analysis jobs. GitHub's current CodeQL build documentation explicitly describes this matrix behavior. The analysis may use newer build modes such as none for some compiled languages, depending on language and configuration, but when the workflow specifically uses autobuild with a language matrix, each compiled language represented by that matrix is processed independently. Therefore, option D correctly describes the behavior.

Dependabot security updates are automated pull requests triggered when GitHub detects a vulnerability in a dependency listed in your manifest or lockfile. These PRs upgrade the dependency to the minimum safe version that fixes the vulnerability.

This is separate from regular updates (which keep versions current even if not vulnerable).

Dependabot alerts are generated as soon as GitHub detects a known vulnerability in one of your dependencies. GitHub does this by analyzing your repository’s dependency graph and matching it against vulnerabilities listed in the GitHub Advisory Database. Once a match is found, the system raises an alert automatically without waiting for a PR or manual action.

This allows organizations to proactively mitigate vulnerabilities as early as possible, based on real-time detection.

Repository rulesets provide centralized enforcement of repository policies before changes can be merged. Rulesets can require workflows or status checks to succeed, and GitHub specifically supports security-oriented enforcement such as dependency review and code scanning merge protection. For dependency review, an organization can require the dependency review workflow through a ruleset so that vulnerable dependency changes prevent merging. Code scanning rulesets can likewise require acceptable code scanning results and define alert thresholds. “Security GuardRails” and “status enforcement” are not GitHub repository features with the functionality described here, while Insights is primarily used for repository statistics and reporting. Therefore, repository rulesets provide the policy mechanism needed to enforce these security gates before code reaches protected branches.