[Configure and Use Code Scanning]Who can fix a code scanning alert on a private repository?
Answer(s): 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 DocsUsers 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 Resolving code scanning alertsGitHub Docs
[Describe the GHAS Security Features and Functionality]Which of the following information can be found in a repository's Security tab?
Answer(s): A
The Security tab in a GitHub repository provides a central location for viewing security-related information, especially when GitHub Advanced Security is enabled. The following can be accessed:Number of alerts related to:Code scanningSecret scanningDependency (Dependabot) alertsSummary and visibility into open, closed, and dismissed security issues.It does not show 2FA options, access control settings, or configuration panels for GHAS itself. Those belong to account or organization-level settings.
GitHub Docs Managing security and analysis settings for your repository
[Configure and Use Secret Scanning]How many alerts are created when two instances of the same secret value are in the same repository?
When multiple instances of the same secret value appear in a repository, only one alert is generated. Secret scanning works by identifying exposed credentials and token patterns, and it groups identical matches into a single alert to reduce noise and avoid duplication.This makes triaging easier and helps teams focus on remediating the actual exposed credential rather than reviewing multiple redundant alerts.
GitHub Docs About secret scanning alerts
[Configure and Use Secret Scanning]What happens when you enable secret scanning on a private repository?
When secret scanning is enabled on a private repository, GitHub performs a read-only analysis of the repository's contents. This includes the entire Git history and files to identify strings that match known secret patterns or custom-defined patterns.GitHub does not alter the repository, and enabling secret scanning does not automatically enable code scanning or dependency review -- each must be configured separately.
GitHub Docs Managing secret scanning for repositories
[Configure and Use Dependency Management]You have enabled security updates for a repository. When does GitHub mark a Dependabot alert as resolved for that repository?
Answer(s): D
A Dependabot alert is marked as resolved only after the related pull request is merged into the repository. This indicates that the vulnerable dependency has been officially replaced with a secure version in the active codebase.Simply generating a PR or passing checks does not change the alert status; merging is the key step.
GitHub Docs About Dependabot security updates; Managing Dependabot alerts
Post your Comments and Discuss GitHub GitHub Advanced Security exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the GitHub Advanced Security content, but please register or login to continue.