GH-500 Exam Dumps - Microsoft GitHub Administrator Questions and Answers

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.

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

Comprehensive and Detailed Explanation:

Before defining a custom pattern for secret scanning in a repository, you must enable secret scanning for that repository. Secret scanning must be active to utilize custom patterns, which allow you to define specific formats (using regular expressions) for secrets unique to your organization.​

Once secret scanning is enabled, you can add custom patterns to detect and prevent the exposure of sensitive information tailored to your needs.​

After generating an alert for a vulnerable dependency, Dependabot automatically attempts to create a pull request to upgrade that dependency to the minimum required secure version —if a fix is available and compatible with your project.

This automated PR helps teams fix vulnerabilities quickly with minimal manual intervention. You can also configure update behaviors using dependabot.yml, but in the default state, PR creation is automatic.

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.

A GitHub personal access token (PAT) is a credential and is therefore a type of value that secret scanning is designed to detect. GitHub supports patterns for GitHub-issued tokens and can generate secret scanning alerts when supported PAT formats are committed to repositories. GitHub also performs validity checks for certain GitHub tokens and can distinguish active from inactive credentials. SQL injection, cross-site scripting, and server-side request forgery are application vulnerabilities rather than exposed credentials; those issues are detected through code scanning tools such as CodeQL. The distinction is important: secret scanning looks for credentials, API keys, passwords, tokens, and similar sensitive values, whereas code scanning analyzes source code for insecure programming patterns. Therefore, only the GitHub PAT belongs to secret scanning.

You can customize CodeQL scanning by including additional query packs or by specifying individual queries :

Packs : These are reusable collections of CodeQL queries bundled into a single package.

Queries : You can point to specific files or directories containing .ql queries to include in the analysis.

github/codeql refers to a pack by name but is not a method or field. Scope is not a valid field used for configuration in this context.

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

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 .

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.