GH-500 - Describe GitHub Security suites, features, and ecosystem - Section 1.5

Explain alert access management, roles, delegated bypass, and enforcement, and describe supply chain security concepts across the SDLC.

Explain alert access management, security roles, delegated bypass permissions, and enforcement policies within GitHub Security suites. Describe how supply chain security concepts apply across the full SDLC, from development through to production dependencies.

alert access managementdelegated bypassenforcementsupply chain security concepts

Practice question for this objective

Free sampleDescribe GitHub Security suites, features, and ecosystemmedium

A security manager team has been granted the security manager role at organisation level. A repository in that organisation also restricts who may dismiss Dependabot alerts. A member of the security manager team needs to dismiss a Dependabot alert in that repository as not affecting the project. They have no other team membership granting write access to the repository. What can they do with respect to that alert?

  • AThey can view the alert but cannot dismiss it, because dismissing a Dependabot alert always requires write access to the repository in addition to any security role.
  • BThey can view and dismiss the alert, because the security manager role grants read access to repositories plus the ability to view and manage security alerts and configuration organisation-wide. Correct
  • CThey can dismiss the alert only after an organisation owner adds them to the repository as an administrator for the duration of the triage.
  • DThey can dismiss the alert but the dismissal is recorded as anonymous, because security managers act on behalf of the organisation rather than as individual users.
The organisation security manager role grants read access plus security alert and configuration management across all repositories without general write or admin. The security manager role exists to give a central security function the ability to read code and view, dismiss, and manage security alerts and configurations across every repository in the organisation, without the write or administrative rights that would let them change settings or push code.

Why A is wrong: This is the trap for candidates who remember that ordinary alert dismissal needs write access; the security manager role grants alert management across the organisation precisely so security staff can dismiss without separate write access, so the absolute claim is wrong.

Why B is correct: The security manager role is designed to let a non-administrative security function triage and dismiss alerts across every repository in the organisation, with read access to code, without granting general write or admin, which is exactly this scenario.

Why C is wrong: Requiring temporary admin defeats the purpose of the security manager role and overstates the access needed; the role already covers alert management, so this is an unnecessary and incorrect escalation.

Why D is wrong: Dismissals are attributed to the acting user for the audit trail regardless of role; the idea of anonymous organisational dismissal is fabricated, so this is wrong even though it sounds like a governance nicety.

See more GH-500 practice questions, answers explained.

More in this domain

Back to all Describe GitHub Security suites, features, and ecosystem objectives, or the GH-500 cert hub.

Examworthy is not affiliated with or endorsed by GitHub. Original, blueprint-aligned practice material only.