Mod 3 - What happens when secret scanning detects a secret in a repository?

• a) It automatically revokes the secret

• b) It notifies all repository administrators about the commit

• c) It deletes the repository

• 4. d) It encrypts the secret for added security

Mod 3 - When does secret scanning send a notification to repository administrators?

• a) When a public repository is created

• b) When a secret with a known pattern is committed

• c) When a security incident is detected

• 3. d) When a branch is deleted

Mod 3 - What does secret scanning do in GitHub Advanced Security?

• a) Scans repositories for known types of secrets

• b) Analyzes code for vulnerabilities

• c) Generates automated pull requests for dependency updates

• 2. d) Audits user access and permissions

Mod 3 - What is required to enable secret scanning on private repositories owned by organizations on an enterprise plan?

• a) A GitHub Actions workflow must be created.

• b) The repository must be made public.

• c) GitHub Advanced Security must be enabled for the organization.

• 5. d) The repository must have at least 100 stars.

Mod 3 - Who is secret scanning available to in GitHub?

• a) Only users with a paid GitHub subscription

• b) All public repositories and private repositories owned by organizations on an enterprise plan with GitHub Advanced Security

• c) Only repository owners and administrators

• 1. d) Only developers using GitHub Actions

Mod 3 - How can you enable secret scanning on a private repository?

• a) It is automatically enabled for all private repositories.

• b) Navigate to Settings > Security & analysis and click the Enable button next to Secret scanning.

• c) Secret scanning cannot be enabled on private repositories.

• 1. d) Secret scanning is only available for public repositories.

Mod 3 - How can you enable secret scanning for an organization?

• a) Secret scanning is automatically enabled for all organizations.

• b) Navigate to Settings > Security & analysis in the organization, and click the Enable all button next to Secret scanning.

• c) Secret scanning cannot be enabled for organizations.

• 4. d) Secret scanning can only be enabled on an organization if GitHub Advanced Security is disabled.

What happens when you click the "Enable all" button next to Secret scanning for an organization, and check "Enable for eligible repositories"

• a) Secret scanning is only enabled for new repositories in the organization.

• b) Secret scanning is enabled for all existing and new repositories in the organization.

• c) Secret scanning is disabled for all repositories in the organization.

• 5. d) Secret scanning can only be enabled for specific branches in the organization's repositories.

Mod 3 - How can you exclude certain files from being scanned by secret scanning?

• a) Create a .secret_scanning.yml file and list the files to be excluded.

• b) Exclude files directly in the repository's settings.

• c) Create a .github/secret_scanning.yml file and use paths-ignore to specify the files to exclude.

• 1. d) Secret scanning cannot exclude specific files from being scanned.

Mod 3 - What happens if the secret_scanning.yml file is larger than 1 MB?

• a) Secret scanning will still scan the entire file, but it will take longer to complete.

• 3. d) Secret scanning will prompt the user to split the file into smaller parts.

• c) Secret scanning will exclude the first 1,000 directories from the scans.

• d) Secret scanning will ignore the entire file and not apply any exclusions.