Question 1
A secret scanning alert should be closed as “used in tests” when a secret is:
- in a test file.
- solely used for tests.
- in the readme.md file.
- not a secret in the production environment.
Question 2
What happens when you enable secret scanning on a private repository?
- Repository administrators can view Dependabot alerts.
- Dependency review, secret scanning, and code scanning are enabled.
- Your team is subscribed to security alerts.
- GitHub performs a read-only analysis on the repository.
Question 3
Which of the following statements best describes secret scanning push protection?
- Buttons for sensitive actions in the GitHub UI are disabled.
- Commits that contain secrets are blocked before code is added to the repository.
- Users need to reply to a 2FA challenge before any push events.
- Secret scanning alerts must be closed before a branch can be merged into the repository.
Question 4
What is a security policy?
- a security alert issued to a community in response to a vulnerability
- a file in a GitHub repository that provides instructions to users about how to report a security vulnerability
- an alert about dependencies that are known to contain security vulnerabilities
- an automatic detection of security vulnerabilities and coding errors in new or modified code
Question 5
Which of the following information can be found in a repository’s Security tab?
- number of alerts per GHAS feature
- GHAS settings
- access management
- two-factor authentication (2FA) options