GH-500 Exam dumps PDF | Exam-Dumps.net (Page: 2)

QUESTION: 9

[Describe GitHub Advanced Security Best Practices]

As a contributor, you discovered a vulnerability in a repository.
Where should you look for the instructions on how to report the vulnerability?

support.md
readme.md
contributing.md
security.md

Answer(s): D

Explanation:

The correct place to look is the SECURITY.md file. This file provides contributors and security researchers with instructions on how to responsibly report vulnerabilities. It may include contact methods, preferred communication channels (e.g., security team email), and disclosure guidelines.

This file is considered a GitHub best practice and, when present, activates a "Report a vulnerability" button in the repository's Security tab.

Reference:

GitHub Docs Adding a security policy to your repository

Reveal Solution Next Question

QUESTION: 10

[Configure and Use Dependency Management]

Assuming there is no custom Dependabot behavior configured, where possible, what does Dependabot do after sending an alert about a vulnerable dependency in a repository?

Creates a pull request to upgrade the vulnerable dependency to the minimum possible secure version
Scans repositories for vulnerable dependencies on a schedule and adds those files to a manifest
Constructs a graph of all the repository's dependencies and public dependents for the default branch
Scans any push to all branches and generates an alert for each vulnerable repository

Answer(s): A

Explanation:

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.

Reference:

GitHub Docs About Dependabot alerts; About Dependabot security updates

Reveal Solution Next Question

QUESTION: 11

[Configure and Use Secret Scanning]

What is the first step you should take to fix an alert in secret scanning?

Archive the repository.
Update your dependencies.
Revoke the alert if the secret is still valid.
Remove the secret in a commit to the main branch.

Answer(s): C

Explanation:

The first step when you receive a secret scanning alert is to revoke the secret if it is still valid. This ensures the secret can no longer be used maliciously. Only after revoking it should you proceed to remove it from the code history and apply other mitigation steps.

Simply deleting the secret from the code does not remove the risk if it hasn't been revoked -- especially since it may already be exposed in commit history.

Reference:

GitHub Docs About secret scanning alerts; Remediating a secret scanning alert

Reveal Solution Next Question

QUESTION: 12

[Configure and Use Dependency Management]

A dependency has a known vulnerability.
What does the warning message include?

The security impact of these changes
An easily understandable visualization of dependency change
How many projects use these components
A brief description of the vulnerability

Answer(s): D

Explanation:

When a vulnerability is detected, GitHub shows a warning that includes a brief description of the vulnerability. This typically covers the name of the CVE (if available), a short summary of the issue, severity level, and potential impact. The message also links to additional advisory data from the GitHub Advisory Database.

This helps developers understand the context and urgency of the vulnerability before applying the fix.

Reference:

GitHub Docs About Dependabot alerts; Reviewing and managing alerts

Reveal Solution Next Question

QUESTION: 13

[Configure and Use Dependency Management]

Assuming that notification and alert recipients are not customized, what does GitHub do when it identifies a vulnerable dependency in a repository where Dependabot alerts are enabled? (Each answer presents part of the solution. Choose two.)

It generates a Dependabot alert and displays it on the Security tab for the repository.
It notifies the repository administrators about the new alert.
It generates Dependabot alerts by default for all private repositories.
It consults with a security service and conducts a thorough vulnerability review.

Answer(s): A,B

Explanation:

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.

Reference:

GitHub Docs About Dependabot alerts; Configuring notifications for Dependabot alerts

Reveal Solution Next Question

QUESTION: 14

[Configure and Use Secret Scanning]

What do you need to do before you can define a custom pattern for a repository?

Provide a regular expression for the format of your secret pattern.
Add a secret scanning custom pattern.
Enable secret scanning on the repository.
Provide match requirements for the secret format.
Stack Overflow

Answer(s): C

Explanation:

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.

Reference:

GitHub Docs Managing alerts from secret scanning

Reveal Solution Next Question

QUESTION: 15

[Configure and Use Dependency Management]

Assuming that no custom Dependabot behavior is configured, who has the ability to merge a pull request created via Dependabot security updates?

An enterprise administrator
A user who has write access to the repository
A user who has read access to the repository
A repository member of an enterprise organization

Answer(s): B

Explanation:

Comprehensive and Detailed Explanation;
By default, users with write access to a repository have the ability to merge pull requests, including those created by Dependabot for security updates. This access level allows contributors to manage and integrate changes, ensuring that vulnerabilities are addressed promptly.

Users with only read access cannot merge pull requests, and enterprise administrators do not automatically have merge rights unless they have write or higher permissions on the specific repository.

Reference:

GitHub Docs About Dependabot security updates; Configuring Dependabot security updates

Reveal Solution Next Question

QUESTION: 16

[Configure and Use Code Scanning]

Who can fix a code scanning alert on a private repository?

Users who have the Triage role within the repository
Users who have Read permissions within the repository
Users who have Write access to the repository
Users who have the security manager role within the repository

Answer(s): C

Explanation:

Comprehensive and Detailed Explanation;
In private repositories, users with write access can fix code scanning alerts. They can do this by committing changes that address the issues identified by the code scanning tools. This level of access ensures that only trusted contributors can modify the code to resolve potential security vulnerabilities.

GitHub Docs

Users with read or triage roles do not have the necessary permissions to make code changes, and the security manager role is primarily focused on managing security settings rather than directly modifying code.

Reference:

GitHub Docs Resolving code scanning alerts

GitHub Docs

Reveal Solution Next Question

Microsoft GH-500 Exam (page: 2) Microsoft GitHub Advanced Security Updated on: 31-Mar-2026

QUESTION: 9

Explanation:

Reference:

QUESTION: 10

Explanation:

Reference:

QUESTION: 11

Explanation:

Reference:

QUESTION: 12

Explanation:

Reference:

QUESTION: 13

Explanation:

Reference:

QUESTION: 14

Explanation:

Reference:

QUESTION: 15

Explanation:

Reference:

QUESTION: 16

Explanation:

Reference:

Microsoft GH-500 Exam (page: 2)
Microsoft GitHub Advanced Security
Updated on: 31-Mar-2026