Microsoft GH-500 GitHub Advanced Security Exam Exam Practice Test

For compiled languages, CodeQL performs extraction by monitoring the normal build process . This means it watches your usual build commands (like make, javac, or dotnet build) and extracts the relevant data from the actual build steps being executed. CodeQL uses this information to construct a semantic database of the application.

This approach ensures that CodeQL captures a precise, real-world representation of the code and its behavior as it is compiled, including platform-specific configurations or conditional logic used during build.

In a query suite (a .qls file), the **query** key is used to specify the paths to one or more .ql files that should be included in the suite.

Example:

- query: path/to/query.ql

qls is the file format.

qlpack is used for packaging queries, not in suite syntax.

Dependabot alerts can identify vulnerable direct dependencies declared in a manifest and vulnerable indirect or transitive dependencies when GitHub can determine their versions from a lockfile. GitHub's dependency graph extracts dependency information from supported manifest and lock files and compares identified package versions against security advisories in the GitHub Advisory Database. Direct dependencies explicitly declared in manifests therefore qualify for vulnerability detection. Transitive dependencies recorded with resolvable versions in lockfiles can also generate alerts. A “loose” dependency declaration may not provide GitHub with a sufficiently specific installed version to establish that the project actually uses a vulnerable release, while a particular time such as 08:00 UTC has nothing to do with whether a dependency qualifies for an alert. Thus, A and C are correct.

Using the Custom setting allows you to subscribe to specific event types, such as Dependabot alerts or vulnerability notifications, without being overwhelmed by all repository activity. This is essential for repository maintainers who need fine-grained control over what kinds of events trigger notifications.

This setting is configurable per repository and allows users to stay aware of critical issues while minimizing notification noise.

When using a SARIF-compatible tool within GitHub Actions, it's necessary to explicitly add a step in your workflow to upload the analysis results. This is typically done using the upload-sarif action, which takes the SARIF file generated by your tool and uploads it to GitHub for processing and display in the Security tab. Without this step, the results won't be available in GitHub's code scanning interface.​

When integrating CodeQL outside of GitHub Actions (e.g., in Jenkins, CircleCI):

Install the CLI : Needed to run CodeQL commands.

Analyze code : Perform the CodeQL analysis on your project with the CLI.

Upload scan results : Export the results in SARIF format and use GitHub’s API to upload them to your repo’s security tab.

You don’t need to write custom queries unless extending functionality. “Processing alerts” happens after GitHub receives the results.

Comprehensive and Detailed Explanation:

To receive Dependabot alert notifications for a repository, you can utilize the following Watch settings:

Custom setting: Allows you to tailor your notifications, enabling you to subscribe specifically to security alerts, including those from Dependabot.​

All Activity setting: Subscribes you to all notifications for the repository, encompassing issues, pull requests, and security alerts like those from Dependabot.​

The Participating and @mentions setting limits notifications to conversations you're directly involved in or mentioned, which may not include security alerts. The Ignore setting unsubscribes you from all notifications, including critical security alerts.​

GitHub Docs

+1

GitHub Docs

+1

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.​

For the organization-owned private repository scenario tested by this question, C is the intended answer. GitHub Secret Protection supports secret scanning for private and internal repositories owned by organizations using an eligible GitHub Team or GitHub Enterprise plan with Secret Protection enabled. Licensing is managed at the organization or enterprise level; an individual license is not uploaded to a repository or attached directly to a user's account. Current GitHub documentation has expanded availability in some enterprise scenarios, including certain user-owned repositories under Enterprise Managed Users and GitHub Enterprise Server. However, for the standard GitHub Advanced Security organization model represented by the question, an organization-owned repository is the applicable prerequisite among the supplied choices.

The Allow for all organizations policy permits repository administrators throughout organizations owned by the enterprise to enable applicable Advanced Security capabilities on their repositories. GitHub enterprise policy can determine whether repository administrators are allowed to enable GitHub Secret Protection, GitHub Code Security, or legacy GitHub Advanced Security features. Selecting an option limited to chosen organizations would restrict availability rather than permit it enterprise-wide. A prohibition such as Never allow would prevent repository administrators from enabling the feature, while No policy does not explicitly establish the enterprise-wide permission requested. GitHub's current documentation describes this policy as controlling availability across all organizations or specified organizations, with organization owners and security managers retaining broader security-management capabilities. Therefore, B matches the stated requirement to allow repository administrators throughout all enterprise organizations.

By default, secret scanning is enabled automatically for all public repositories . For private or internal repositories, secret scanning must be enabled manually unless configured at the organization or enterprise level.

This default behavior helps protect open-source projects without requiring additional configuration.

In a repository's Security tab, you can view:

Secret scanning alerts : Exposed credentials or tokens

Dependabot alerts : Vulnerable dependencies from the advisory database

Code scanning alerts : Vulnerabilities in code detected via static analysis (e.g., CodeQL)

You won’t see general "security status alerts" (not a formal category) or permission-related alerts here.

Known vulnerable dependencies detected in a repository are presented as Dependabot alerts. GitHub uses the dependency graph to determine which packages and versions the repository depends on and compares that information with vulnerability data from the GitHub Advisory Database. When a match is found, an alert appears in the repository's Security and quality area under Dependabot vulnerabilities. Each alert can provide the affected dependency, vulnerability details, severity, the affected manifest or lockfile, and a secure version when one is available. Secret scanning alerts relate to exposed credentials, while code scanning alerts represent vulnerabilities or coding errors in source code. Security advisories are vulnerability records and disclosure mechanisms rather than the repository-specific list of vulnerable dependencies.

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.

When a public repository contains credentials that match known secret formats, GitHub will automatically notify the service provider that issued the secret. This process is known as "secret scanning partner notification" . The provider may then revoke the secret or contact the user directly.

GitHub does not publicly display the alert and does not send internal repository notifications for public detections.

Comprehensive and Detailed Explanation:

A CodeQL database contains a representation of your codebase, including the build of the code and extracted data. This database is used to run CodeQL queries to analyze your code for potential vulnerabilities and errors.​

GitHub Docs

GitHub secret scanning examines the repository comprehensively rather than limiting analysis to selected files or dependency metadata. GitHub states that secret scanning scans the entire Git history across all branches for supported secrets. Consequently, both current files and historical versions of files can be inspected, which is why simply deleting a leaked credential in a later commit does not eliminate the security risk. The feature searches repository content for supported provider, generic, and other enabled secret patterns. Dependencies themselves are handled primarily through dependency graph and Dependabot functionality and are not a secret-scanning scope category. Therefore, the correct selections are all branches, the full commit history, and all files in the repository.

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.​

By default , no repositories receive Dependabot alerts unless configuration is explicitly enabled. GitHub does not enable Dependabot alerts automatically for any repositories unless:

The feature is turned on manually

It's configured at the organization or enterprise level via security policies

This includes public, private, and enterprise-owned repositories — manual activation is required .

To exclude .txt and .md files from triggering workflows on pull requests to the main branch:

on: defines the event (e.g., pull_request)

pull_request: is the trigger

paths-ignore: is the key used to ignore file patterns

Example YAML:

yaml

CopyEdit

on:

pull_request:

branches:

- main

paths-ignore:

- '*.md'

- '*.txt'

Using paths: would include only specific files instead — not exclude. paths-ignore: is correct here.

Dependency review and secret scanning are capabilities associated with GitHub Advanced Security. In GitHub's current product structure, dependency review is included with GitHub Code Security, while secret scanning is a central capability of GitHub Secret Protection. Both products are components of the broader GitHub Advanced Security offering, and legacy GHAS licenses can include the combined capabilities. The dependency graph is an important supply-chain feature and provides the underlying dependency inventory, but it is broadly available beyond the licensed GHAS feature set and is enabled by default for public repositories. A repository security policy, normally provided through SECURITY.md, is also a general repository capability rather than one of the licensed Advanced Security features being tested. Therefore, dependency review and secret scanning are the correct selections.

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.

Dependabot alerts utilize standardized identifiers to describe vulnerabilities:​

CVE (Common Vulnerabilities and Exposures): A widely recognized identifier for publicly known cybersecurity vulnerabilities.​

CWE (Common Weakness Enumeration): A category system for software weaknesses and vulnerabilities.​

These identifiers help developers understand the nature of the vulnerabilities and facilitate the search for more information or remediation strategies.​

Dependabot alert and advisory details can include a CVE identifier, a GHSA identifier, and associated CWE classifications. CVE provides the standardized identifier for a publicly known vulnerability. GitHub assigns a unique GHSA ID to advisories in the GitHub Advisory Database, while CWE identifies the underlying category or class of software weakness associated with the vulnerability. GitHub's Dependabot alert interface exposes these values when they are available. EPSS is also now surfaced by GitHub and can be used to prioritize alerts, but EPSS is a probability-based exploit-risk score, not one of the three vulnerability identifiers/classifications being tested by this question. SAST describes a security-analysis methodology rather than an advisory classification. Therefore, the intended selections are CVE, GHSA, and CWE: C, D, and E.

The config-file input is used with the github/codeql-action/init action to specify the path to a custom CodeQL configuration file. This configuration can define additional query packs, custom queries, directories to include or exclude, and other CodeQL analysis settings. GitHub's official workflow documentation shows config-file under the with: section of the CodeQL initialization step. The queries input is used to specify additional query suites or query packs directly, rather than referencing a configuration file. source-root and db-location are not the appropriate init inputs for supplying the configuration-file path. Therefore, when the CodeQL workflow must load settings from a separate YAML configuration file, config-file is the correct parameter.

To create or modify a code scanning workflow file (typically under .github/workflows/codeql-analysis.yml), you must have Write access to the repository.

Write permission allows you to commit the workflow file, which is required to run or configure code scanning using GitHub Actions.

Under GitHub's current documented behavior, the minimum repository permission that can bypass ordinary repository push protection is Write, making B correct. GitHub states that, when delegated bypass is not enabled, a contributor with write access can bypass a push-protection block by providing an allowed reason. The bypass is recorded, and repository-level push protection can generate a corresponding alert and audit-log entry. The PDF marks Admin, which reflects older or more restrictive behavior and is no longer the best answer under current GitHub documentation. Organizations can also enable delegated bypass, which changes the model by requiring contributors without bypass privileges to request approval from designated reviewers. Organization owners, security managers, or specifically authorized roles can then manage those requests. For the default non-delegated model, Write is sufficient.

Enabling the dependency graph allows GitHub to analyze supported manifest and lock files and build a representation of the repository's direct and transitive dependencies. GitHub receives read-only access to the dependency files, parses supported manifests when the feature is first enabled, and then updates the graph as repository content changes. Dependabot alerts and Dependabot security updates are separate capabilities: enabling the dependency graph alone does not automatically mean that security-update pull requests will be generated. Likewise, the dependency graph setting for one repository does not require administrators to manually enable dependency information for every newly created repository unless their organization's configuration requires that behavior. Therefore, the applicable result among the supplied options is that repository administrators can view the dependency information exposed by the dependency graph.

When a person's access to a private repository is removed, GitHub deletes that person's private forks belonging to the repository's network. This prevents the GitHub-hosted fork from remaining available after the user loses authorization to the upstream private repository. GitHub cannot, however, automatically erase local clones that the person previously downloaded to their own computers; the documentation explicitly states that local clones are retained. Removing one individual's access also does not necessarily revoke an entire team's access, because team permissions are managed separately. Nor does GitHub automatically delete confidential information that may have been copied outside the repository. GitHub therefore advises organizations to ensure that former collaborators appropriately dispose of confidential or proprietary information. The direct platform behavior described in the question is deletion of the user's private forks.

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).

Current GitHub documentation requires Write access or higher to list, dismiss, and delete code scanning alerts. The PDF marks Triage, but that is not correct under the current repository-role permissions documented by GitHub. A user with Triage access can view code scanning alerts associated with pull requests, but Triage does not grant the broader permission required to manage the repository's code scanning alert list. Because Write is not one of the supplied choices, Maintain is the lowest listed role that exceeds Write and therefore has the required management capability. Read access does not permit alert management, and “View” is not one of GitHub's standard organization repository roles in this context. Accordingly, based on current official documentation, the technically correct option from the choices provided is B. Maintain.

Comprehensive and Detailed Explanation:

Dependabot alerts are generated based on data from various sources:​

National Vulnerability Database (NVD): A comprehensive repository of known vulnerabilities, which GitHub integrates into its advisory database.​

GitHub Docs

Security Advisories Reported on GitHub: GitHub allows maintainers and security researchers to report and discuss vulnerabilities, which are then included in the advisory database.​

The dependency graph and manifest/lock files are tools used by GitHub to determine which dependencies are present in a repository but are not sources of vulnerability disclosures themselves.​

The dependency graph in a repository is built by parsing manifest and lock files (like package.json, pom.xml, requirements.txt). It helps GitHub detect dependencies and cross-reference them with known vulnerability databases for alerting.

It is specific to each repository and does not show org-wide or cross-repo summaries.

Secret scanning for a private repository is enabled through the repository's security configuration/settings, currently located under Settings → Security and quality → Advanced Security. In current GitHub terminology, enabling Secret Protection enables secret scanning alerts for an eligible private or internal repository. Repository rulesets control policies such as branch protection, required checks, and merge conditions; they are not the primary mechanism for enabling secret scanning. GitHub also does not use a secret.yml file to activate the feature. Code scanning default setup configures CodeQL analysis and is separate from secret detection. Organization owners can additionally enable Secret Protection and secret-scanning capabilities at scale by applying security configurations to repositories. Consequently, the code security or Advanced Security settings area is the correct location, making A the correct answer.

Dependency review runs as part of a pull request and shows which dependencies are being added, removed, or changed — and highlights vulnerabilities associated with any added packages.

It works in real-time and is specifically designed for use during pull request workflows.

The dependency graph is an overview, Dependabot alerts notify post-merge, and the Security tab shows the aggregated alert list.

A Dependabot alert is only marked as resolved when the related vulnerability is no longer present in your code — specifically after you merge a pull request that updates the vulnerable dependency.

Simply viewing alerts or graphs does not affect their status. Ignoring the alert by leaving the repo unchanged keeps the vulnerability active and unresolved.

The security-extended query suite includes additional CodeQL queries that detect lower severity issues than those in the default security-and-quality suite.

It’s often used when projects want broader visibility into code hygiene and potential weak spots beyond critical vulnerabilities.

The other options listed are paths to language packs , not query suites themselves.