Microsoft GH-100 Practice Test 25
Question 240
GitHub Enterprise administration scenario — Require code scanning results before protected merges. In an enterprise development environment: A repository uses CodeQL, yet maintainers routinely merge security-sensitive changes while required analyses are absent or failing. A controlled enterprise configuration review requires a coherent rationale, approved change and confirmed outcome. Select EXACTLY THREE: the governing GitHub administration principle, the proportionate authorized intervention AND the independently observable outcome for this scenario.
- Unreviewed pull requests cannot merge when mandatory scanning is missing, while clean approved changes proceed.
- The tool performs its required repository operation without reading unrelated repositories or changing organization settings.
- Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance.
- Code scanning can be integrated into branch rulesets to make approved security checks a meaningful merge gate.
- Add appropriate code scanning status requirements through the owning organization ruleset with a carefully approved bypass process.
- Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure.
Explanation
Correct Answers
A:Unreviewed pull requests cannot merge when mandatory scanning is missing, while clean approved changes proceed. Add appropriate code scanning status requirements through the owning organization ruleset with a carefully approved bypass process. Code scanning can be integrated into branch rulesets to make approved security checks a meaningful merge gate.
D:Code scanning can be integrated into branch rulesets to make approved security checks a meaningful merge gate. Add appropriate code scanning status requirements through the owning organization ruleset with a carefully approved bypass process. Unreviewed pull requests cannot merge when mandatory scanning is missing, while clean approved changes proceed.
E:Add appropriate code scanning status requirements through the owning organization ruleset with a carefully approved bypass process. Code scanning can be integrated into branch rulesets to make approved security checks a meaningful merge gate. Unreviewed pull requests cannot merge when mandatory scanning is missing, while clean approved changes proceed.
Incorrect Answers
B:The tool performs its required repository operation without reading unrelated repositories or changing organization settings. It would not independently demonstrate that the control works: A repository uses CodeQL, yet maintainers routinely merge security-sensitive changes while required analyses are absent or failing. Unreviewed pull requests cannot merge when mandatory scanning is missing, while clean approved changes proceed. Add appropriate code scanning status requirements through the owning organization ruleset with a carefully approved bypass process.
C:Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance. It does not implement the governing rule for this approval: A repository uses CodeQL, yet maintainers routinely merge security-sensitive changes while required analyses are absent or failing. Add appropriate code scanning status requirements through the owning organization ruleset with a carefully approved bypass process. Unreviewed pull requests cannot merge when mandatory scanning is missing, while clean approved changes proceed.
F:Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure. It is not the rule that supports the proposed change and acceptance test: A repository uses CodeQL, yet maintainers routinely merge security-sensitive changes while required analyses are absent or failing. Code scanning can be integrated into branch rulesets to make approved security checks a meaningful merge gate. Add appropriate code scanning status requirements through the owning organization ruleset with a carefully approved bypass process.
Question 241
GitHub Enterprise administration scenario — Enable Dependabot vulnerability alerts for dependencies. In an enterprise development environment: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. The administrator must identify the controlling access, governance or platform principle rather than an unrelated configuration fix. Which principle BEST addresses this condition? Choose ONE best answer.
- Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses.
- Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling.
- Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
- Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories.
Explanation
Correct Answer
C:Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope. Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies. Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership.
Incorrect Answers
A:Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses. It does not govern the condition described: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
B:Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling. It does not govern the condition described: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
D:Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories. It does not govern the condition described: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
Question 242
GitHub Enterprise administration scenario — Enable Dependabot vulnerability alerts for dependencies. In an enterprise development environment: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies.
- Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance.
- Collect alert severity, exploitability, asset criticality, creation time and current assigned owner.
- Review the app manifest permissions, selected repositories and the organization policy controlling installations.
Explanation
Correct Answer
A:Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies. Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope. Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership.
Incorrect Answers
B:Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance. That check would not establish the decisive facts for this condition: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies.
C:Collect alert severity, exploitability, asset criticality, creation time and current assigned owner. That check would not establish the decisive facts for this condition: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies.
D:Review the app manifest permissions, selected repositories and the organization policy controlling installations. That check would not establish the decisive facts for this condition: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies.
Question 243
GitHub Enterprise administration scenario — Enable Dependabot vulnerability alerts for dependencies. In an enterprise development environment: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. The enterprise administrator needs a least-privilege corrective change with accountable approval and rollback. Which action BEST resolves the reported GitHub configuration or governance problem? Choose ONE best answer.
- Limit bypass authority and require an approved accountable emergency pathway with post-event review.
- Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership.
- Add appropriate code scanning status requirements through the owning organization ruleset with a carefully approved bypass process.
- Enable appropriate external collection before incidents and document search sources by event type.
Explanation
Correct Answer
B:Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership. Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies. The vulnerable test package is associated with a reviewable alert and its owning team is notified.
Incorrect Answers
A:Limit bypass authority and require an approved accountable emergency pathway with post-event review. That change would leave the reported problem unresolved: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership.
C:Add appropriate code scanning status requirements through the owning organization ruleset with a carefully approved bypass process. That change would leave the reported problem unresolved: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership.
D:Enable appropriate external collection before incidents and document search sources by event type. That change would leave the reported problem unresolved: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership.
Question 244
GitHub Enterprise administration scenario — Enable Dependabot vulnerability alerts for dependencies. In an enterprise development environment: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.
- Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies.
- The vulnerable test package is associated with a reviewable alert and its owning team is notified.
- The integration continues after the creator is offboarded and only its installed repositories are reachable.
- Inspect the application's authorization flow, granted scopes or granular installation permissions, and its repository targets.
- Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets.
Explanation
Correct Answers
A:Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies. The vulnerable test package is associated with a reviewable alert and its owning team is notified. Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership.
B:The vulnerable test package is associated with a reviewable alert and its owning team is notified. Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies. Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
Incorrect Answers
C:The integration continues after the creator is offboarded and only its installed repositories are reachable. It would not verify whether the proposed change works: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. The vulnerable test package is associated with a reviewable alert and its owning team is notified. Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership.
D:Inspect the application's authorization flow, granted scopes or granular installation permissions, and its repository targets. It would not provide the evidence needed for the paired diagnosis and follow-up: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies. The vulnerable test package is associated with a reviewable alert and its owning team is notified.
E:Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets. It would not provide the evidence needed for the paired diagnosis and follow-up: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies. The vulnerable test package is associated with a reviewable alert and its owning team is notified.
Question 245
GitHub Enterprise administration scenario — Enable Dependabot vulnerability alerts for dependencies. In an enterprise development environment: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. A controlled enterprise configuration review requires a coherent rationale, approved change and confirmed outcome. Select EXACTLY THREE: the governing GitHub administration principle, the proportionate authorized intervention AND the independently observable outcome for this scenario.
- Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
- Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership.
- Compromise of an app credential calls for immediate containment and rotation of the underlying signing material.
- The security analysis produces a valid database and findings for the intended compiled component.
- The vulnerable test package is associated with a reviewable alert and its owning team is notified.
- Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
Explanation
Correct Answers
A:Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope. Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership. The vulnerable test package is associated with a reviewable alert and its owning team is notified.
B:Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership. Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope. The vulnerable test package is associated with a reviewable alert and its owning team is notified.
E:The vulnerable test package is associated with a reviewable alert and its owning team is notified. Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership. Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
Incorrect Answers
C:Compromise of an app credential calls for immediate containment and rotation of the underlying signing material. It is not the rule that supports the proposed change and acceptance test: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope. Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership.
D:The security analysis produces a valid database and findings for the intended compiled component. It would not independently demonstrate that the control works: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. The vulnerable test package is associated with a reviewable alert and its owning team is notified. Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership.
F:Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results. It does not implement the governing rule for this approval: Security managers receive CVE notices for a Java dependency but the affected repository's dependency graph and security alert settings have never been reviewed. Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership. The vulnerable test package is associated with a reviewable alert and its owning team is notified.
Question 246
GitHub Enterprise administration scenario — Use Dependabot security update pull requests safely. In an enterprise development environment: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. The administrator must identify the controlling access, governance or platform principle rather than an unrelated configuration fix. Which principle BEST addresses this condition? Choose ONE best answer.
- Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
- Git and other audit event types have different availability windows, so required forensic data must be retained proactively.
- Automated security update pull requests support remediation but must still pass review, compatibility and CI checks.
- Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance.
Explanation
Correct Answer
C:Automated security update pull requests support remediation but must still pass review, compatibility and CI checks. Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage. Enable supported security update pull requests with owned reviewers and controlled merge rules.
Incorrect Answers
A:Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope. It does not govern the condition described: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. Automated security update pull requests support remediation but must still pass review, compatibility and CI checks.
B:Git and other audit event types have different availability windows, so required forensic data must be retained proactively. It does not govern the condition described: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. Automated security update pull requests support remediation but must still pass review, compatibility and CI checks.
D:Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance. It does not govern the condition described: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. Automated security update pull requests support remediation but must still pass review, compatibility and CI checks.
Question 247
GitHub Enterprise administration scenario — Use Dependabot security update pull requests safely. In an enterprise development environment: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Compare workspace manifests, package lockfiles, supported ecosystem behavior and current dependency graph entries.
- Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events.
- Review required events, streaming destination, service ownership, delivery health and external retention policy.
- Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage.
Explanation
Correct Answer
D:Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage. Automated security update pull requests support remediation but must still pass review, compatibility and CI checks. Enable supported security update pull requests with owned reviewers and controlled merge rules.
Incorrect Answers
A:Compare workspace manifests, package lockfiles, supported ecosystem behavior and current dependency graph entries. That check would not establish the decisive facts for this condition: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage.
B:Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events. That check would not establish the decisive facts for this condition: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage.
C:Review required events, streaming destination, service ownership, delivery health and external retention policy. That check would not establish the decisive facts for this condition: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage.
Question 248
GitHub Enterprise administration scenario — Use Dependabot security update pull requests safely. In an enterprise development environment: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. The enterprise administrator needs a least-privilege corrective change with accountable approval and rollback. Which action BEST resolves the reported GitHub configuration or governance problem? Choose ONE best answer.
- Rotate or revoke the exposed app private key, investigate token activity and update the application secret store.
- Enable supported security update pull requests with owned reviewers and controlled merge rules.
- Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.
- Produce a repeatable cross-organization effective-control report and assign remediation to owners of exceptions.
Explanation
Correct Answer
B:Enable supported security update pull requests with owned reviewers and controlled merge rules. Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage. A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge.
Incorrect Answers
A:Rotate or revoke the exposed app private key, investigate token activity and update the application secret store. That change would leave the reported problem unresolved: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. Enable supported security update pull requests with owned reviewers and controlled merge rules.
C:Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement. That change would leave the reported problem unresolved: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. Enable supported security update pull requests with owned reviewers and controlled merge rules.
D:Produce a repeatable cross-organization effective-control report and assign remediation to owners of exceptions. That change would leave the reported problem unresolved: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. Enable supported security update pull requests with owned reviewers and controlled merge rules.
Question 249
GitHub Enterprise administration scenario — Use Dependabot security update pull requests safely. In an enterprise development environment: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.
- Both organizations follow the same mandatory repository security rule without accidental creation of public assets.
- Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage.
- Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies.
- Compare current token ownership, required API endpoints, repository selection and supported GitHub App permission model.
- A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge.
Explanation
Correct Answers
B:Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage. A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge. Enable supported security update pull requests with owned reviewers and controlled merge rules.
E:A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge. Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage. Automated security update pull requests support remediation but must still pass review, compatibility and CI checks.
Incorrect Answers
A:Both organizations follow the same mandatory repository security rule without accidental creation of public assets. It would not verify whether the proposed change works: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge. Enable supported security update pull requests with owned reviewers and controlled merge rules.
C:Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies. It would not provide the evidence needed for the paired diagnosis and follow-up: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage. A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge.
D:Compare current token ownership, required API endpoints, repository selection and supported GitHub App permission model. It would not provide the evidence needed for the paired diagnosis and follow-up: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage. A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge.
Question 250
GitHub Enterprise administration scenario — Use Dependabot security update pull requests safely. In an enterprise development environment: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. A controlled enterprise configuration review requires a coherent rationale, approved change and confirmed outcome. Select EXACTLY THREE: the governing GitHub administration principle, the proportionate authorized intervention AND the independently observable outcome for this scenario.
- Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
- An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route.
- Automated security update pull requests support remediation but must still pass review, compatibility and CI checks.
- A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge.
- Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.
- Enable supported security update pull requests with owned reviewers and controlled merge rules.
Explanation
Correct Answers
C:Automated security update pull requests support remediation but must still pass review, compatibility and CI checks. Enable supported security update pull requests with owned reviewers and controlled merge rules. A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge.
D:A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge. Enable supported security update pull requests with owned reviewers and controlled merge rules. Automated security update pull requests support remediation but must still pass review, compatibility and CI checks.
F:Enable supported security update pull requests with owned reviewers and controlled merge rules. Automated security update pull requests support remediation but must still pass review, compatibility and CI checks. A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge.
Incorrect Answers
A:Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope. It is not the rule that supports the proposed change and acceptance test: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. Automated security update pull requests support remediation but must still pass review, compatibility and CI checks. Enable supported security update pull requests with owned reviewers and controlled merge rules.
B:An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route. It would not independently demonstrate that the control works: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge. Enable supported security update pull requests with owned reviewers and controlled merge rules.
E:Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process. It does not implement the governing rule for this approval: A repository has actionable dependency alerts, yet there is no repeatable workflow for proposing compatible patches to vulnerable packages. Enable supported security update pull requests with owned reviewers and controlled merge rules. A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge.