Module assessment

1.

What is the primary purpose of a security campaign in GitHub Advanced Security?

To automatically fix all security alerts across repositories

To group related security alerts across repositories so teams can coordinate remediation

To replace code scanning and dependency scanning tools

To prevent all vulnerabilities from being introduced into code

2.

Which GitHub features generate the security alerts used in campaigns?

Code scanning, secret scanning, and dependency alerts

GitHub Issues, Projects, and Discussions

GitHub Actions only

Pull requests and commits

3.

What is the correct workflow for remediation in GitHub Advanced Security campaigns?

Fix alerts directly inside the campaign dashboard

Delete repositories with high alert volume

Use pull requests and standard GitHub workflows to resolve alerts in repositories

Wait for GitHub to automatically close alerts

4.

How do organizations measure the effectiveness of a security campaign?

By the number of repositories created during the campaign

By tracking alert volume, remediation speed, and new alert trends over time

By the number of developers assigned to alerts

By disabling security scanning tools

5.

What is the main outcome of applying prevention-first controls?

Elimination of all security alerts

Reduced introduction of new vulnerabilities into code

Replacement of security campaigns with automated fixes

Removal of the need for pull requests

Check your knowledge