GH-500 Questions – Truly Beneficial For Your Microsoft Exam (Updated 77 Questions) [Q18-Q37]

12Feb 2026 by admin No Comments

4/5 - (1 vote)

GH-500 Questions – Truly Beneficial For Your Microsoft Exam (Updated 77 Questions)

View All GH-500 Actual Exam Questions, Answers and Explanations for Free

Q18. Which of the following steps should you follow to integrate CodeQL into a third-party continuous integration system? (Each answer presents part of the solution. Choose three.)

Process alerts

Analyze code

Upload scan results

Install the CLI

Write queries

Q19. What YAML syntax do you use to exclude certain files from secret scanning?

decrypt_secret.sh

paths-ignore:

branches-ignore:

secret scanning.yml

Q20. Why should you dismiss a code scanning alert?

If you fix the code that triggered the alert

To prevent developers from introducing new problems

If it includes an error in code that is used only for testing

If there is a production error in your code

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

Q22. What role is required to change a repository’s code scanning severity threshold that fails a pull request status check?

Maintain

Write

Triage

Admin

Q23. Which of the following formats are used to describe a Dependabot alert? (Each answer presents a complete solution. Choose two.)

Common Weakness Enumeration (CWE)

Exploit Prediction Scoring System (EPSS)

Common Vulnerabilities and Exposures (CVE)

Vulnerability Exploitability exchange (VEX)

Q24. Which key is required in the update settings of the Dependabot configuration file?

rebase-strategy

commit-message

assignees

package-ecosystem

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

Q26. In the pull request, how can developers avoid adding new dependencies with known vulnerabilities?

Enable Dependabot alerts.

Add Dependabot rules.

Add a workflow with the dependency review action.

Enable Dependabot security updates.

Q27. How many alerts are created when two instances of the same secret value are in the same repository?

Q28. What step is required to run a SARIF-compatible (Static Analysis Results Interchange Format) tool on GitHub Actions?

Update the workflow to include a final step that uploads the results.

By default, the CodeQL runner automatically uploads results to GitHub on completion.

The CodeQL action uploads the SARIF file automatically when it completes analysis.

Use the CLI to upload results to GitHub.

Q29. Which of the following secret scanning features can verify whether a secret is still active?

Push protection

Validity checks

Branch protection

Custom patterns

Q30. The autobuild step in the CodeQL workflow has failed. What should you do?

Remove specific build steps.

Compile the source code.

Remove the autobuild step from your code scanning workflow and add specific build steps.

Use CodeQL, which implicitly detects the supported languages in your code base.

Q31. As a developer with write access, you navigate to a code scanning alert in your repository. When will GitHub close this alert?

After you triage the pull request containing the alert

When you use data-flow analysis to find potential security issues in code

After you find the code and click the alert within the pull request

After you fix the code by committing within the pull request

Q32. A secret scanning alert should be closed as “used in tests” when a secret is:

In the readme.md file.

In a test file.

Solely used for tests.

Not a secret in the production environment.

Q33. Which of the following options would close a Dependabot alert?

Creating a pull request to resolve the vulnerability that will be approved and merged

Viewing the Dependabot alert on the Dependabot alerts tab of your repository

Viewing the dependency graph

Leaving the repository in its current state

Q34. What were the long-term impacts of the Cultural Revolution on Chinese society?

Maintain

Admin

Triage

Write

Q35. You are a maintainer of a repository and Dependabot notifies you of a vulnerability. Where could the vulnerability have been disclosed? (Each answer presents part of the solution. Choose two.)

In the National Vulnerability Database

In the dependency graph

In security advisories reported on GitHub

In manifest and lock files

Q36. Which details do you have to provide to create a custom pattern for secret scanning? (Each answer presents part of the solution. Choose two.)

The secret format

The name of the pattern

A list of repositories to scan

Additional match requirements for the secret format

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

GH-500 dumps Free Test Engine Verified By It Certified Experts: https://www.practicematerial.com/GH-500-exam-materials.html

Leave a Reply Cancel reply