GitHub Certification GitHub-Advanced-Security Syllabus Exam Questions Answers

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

To create or modify acode scanning workflow file(typically under .github/workflows/codeql-analysis.yml), you must haveWriteaccess to the repository.

Write permission allows you to commit the workflow file, which is required to run or configure code scanning using GitHub Actions.

To detect and blockvulnerable dependencies before merge, developers should use theDependency Review GitHub Actionin their pull request workflows. It scans all proposed dependency changes and flags any packages with known vulnerabilities.

This is apreventative measureduring development, unlike Dependabot, which reactsafter the fact.

Secrets committed and then deleted are still accessible in therepository’s Git history. To locate them, navigate to theCommitstab. GitHub's secret scanning can detect secrets in both current and historical commits, which is why remediation should also includerevoking the secret, not just removing it from the latest code.