Ace Microsoft GitHub Advanced Security Exam GH-500: Your Key to Cloud Security Mastery
-- [Configure and Use Dependency Management]
Which security feature shows a vulnerable dependency in a pull request?
Correct : B
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.
Start a Discussions
-- [Configure and Use Code Scanning]
Who can fix a code scanning alert on a private repository?
Correct : C
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.
GitHub Docs
Start a Discussions
-- [Use Code Scanning with CodeQL]
The autobuild step in the CodeQL workflow has failed. What should you do?
Correct : C
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.
Start a Discussions
-- [Configure and Use Secret Scanning]
Which of the following statements best describes secret scanning push protection?
Correct : A
Comprehensive and Detailed Explanation:
Secret scanning push protection is a proactive feature that scans for secrets in your code during the push process. If a secret is detected, the push is blocked, preventing the secret from being added to the repository. This helps prevent accidental exposure of sensitive information.
GitHub Docs
Start a Discussions
-- [Configure and Use Secret Scanning]
Which details do you have to provide to create a custom pattern for secret scanning? (Each answer presents part of the solution. Choose two.)
Correct : A, B
When defining a custom pattern for secret scanning, two key fields are required:
Name of the pattern: A unique label to identify the pattern
Secret format: A regular expression that defines what the secret looks like (e.g., token format)
You can optionally specify additional match requirements (like required context keywords), but they're not mandatory. Listing repositories is also not part of the required fields during pattern creation.
Start a Discussions
Total 75 questions