cert
cert-1
cert-2

Pass Microsoft GH-100 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
GH-100 Exam - Verified By Experts
GH-100 Premium File

GH-100 Premium File

$69.99
$76.99
  • Premium File 171 Questions & Answers. Last Update: Nov 19, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 11 downloads in the last 7 days
block-screenshots
Microsoft GH-100 Practice Test 29

Question 280

GitHub Enterprise administration scenario — Standardize security configurations across new repositories. In an enterprise development environment: A security team enables secret scanning and code scanning one repository at a time, but newly created organization repositories repeatedly lack these controls. 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.

  1. Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure.
  2. An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route.
  3. Path-specific review can direct sensitive changes to authorized subject-matter owners before merge.
  4. Create and apply an approved security baseline to eligible repositories with exception ownership and periodic coverage reports.
  5. Sample existing and new repositories have the required supported scanning controls or documented exceptions.
  6. Organization-level security configuration can provide consistent supported coverage when applied and monitored across repositories.

Explanation

Correct Answers

D:

Create and apply an approved security baseline to eligible repositories with exception ownership and periodic coverage reports. Organization-level security configuration can provide consistent supported coverage when applied and monitored across repositories. Sample existing and new repositories have the required supported scanning controls or documented exceptions.

E:

Sample existing and new repositories have the required supported scanning controls or documented exceptions. Create and apply an approved security baseline to eligible repositories with exception ownership and periodic coverage reports. Organization-level security configuration can provide consistent supported coverage when applied and monitored across repositories.

F:

Organization-level security configuration can provide consistent supported coverage when applied and monitored across repositories. Create and apply an approved security baseline to eligible repositories with exception ownership and periodic coverage reports. Sample existing and new repositories have the required supported scanning controls or documented exceptions.

Incorrect Answers

A:

Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure. It does not implement the governing rule for this approval: A security team enables secret scanning and code scanning one repository at a time, but newly created organization repositories repeatedly lack these controls. Create and apply an approved security baseline to eligible repositories with exception ownership and periodic coverage reports. Sample existing and new repositories have the required supported scanning controls or documented exceptions.

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 security team enables secret scanning and code scanning one repository at a time, but newly created organization repositories repeatedly lack these controls. Sample existing and new repositories have the required supported scanning controls or documented exceptions. Create and apply an approved security baseline to eligible repositories with exception ownership and periodic coverage reports.

C:

Path-specific review can direct sensitive changes to authorized subject-matter owners before merge. It is not the rule that supports the proposed change and acceptance test: A security team enables secret scanning and code scanning one repository at a time, but newly created organization repositories repeatedly lack these controls. Organization-level security configuration can provide consistent supported coverage when applied and monitored across repositories. Create and apply an approved security baseline to eligible repositories with exception ownership and periodic coverage reports.

Question 281

GitHub Enterprise administration scenario — Enforce enterprise security policy consistently. In an enterprise development environment: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. 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.

  1. Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure.
  2. Coordinated vulnerability disclosure needs restricted collaboration and a tracked remediation process.
  3. Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling.
  4. Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses.

Explanation

Correct Answer

C:

Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling. Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries. Apply a centrally approved policy baseline and allow only formally approved supported exceptions.

Incorrect Answers

A:

Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure. It does not govern the condition described: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling.

B:

Coordinated vulnerability disclosure needs restricted collaboration and a tracked remediation process. It does not govern the condition described: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling.

D:

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: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling.

Question 282

GitHub Enterprise administration scenario — Enforce enterprise security policy consistently. In an enterprise development environment: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage.
  2. Inspect the active branch rulesets, required tools, alert thresholds and the checkout of the merge commit.
  3. Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries.
  4. Review supported languages, build commands, checkout depth, workflow logs and the failed extraction stage.

Explanation

Correct Answer

C:

Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries. Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling. Apply a centrally approved policy baseline and allow only formally approved supported exceptions.

Incorrect Answers

A:

Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage. That check would not establish the decisive facts for this condition: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries.

B:

Inspect the active branch rulesets, required tools, alert thresholds and the checkout of the merge commit. That check would not establish the decisive facts for this condition: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries.

D:

Review supported languages, build commands, checkout depth, workflow logs and the failed extraction stage. That check would not establish the decisive facts for this condition: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries.

Question 283

GitHub Enterprise administration scenario — Enforce enterprise security policy consistently. In an enterprise development environment: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. 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.

  1. Apply a centrally approved policy baseline and allow only formally approved supported exceptions.
  2. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.
  3. Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure.
  4. Move the classified content into a private repository with explicit reviewed team access and retention safeguards.

Explanation

Correct Answer

A:

Apply a centrally approved policy baseline and allow only formally approved supported exceptions. Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries. Both organizations follow the same mandatory repository security rule without accidental creation of public assets.

Incorrect Answers

B:

Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process. That change would leave the reported problem unresolved: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Apply a centrally approved policy baseline and allow only formally approved supported exceptions.

C:

Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure. That change would leave the reported problem unresolved: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Apply a centrally approved policy baseline and allow only formally approved supported exceptions.

D:

Move the classified content into a private repository with explicit reviewed team access and retention safeguards. That change would leave the reported problem unresolved: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Apply a centrally approved policy baseline and allow only formally approved supported exceptions.

Question 284

GitHub Enterprise administration scenario — Enforce enterprise security policy consistently. In an enterprise development environment: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. 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.

  1. Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries.
  2. Inspect workflow event triggers, token permissions, secret exposure paths and the executed checkout reference.
  3. Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations.
  4. Both organizations follow the same mandatory repository security rule without accidental creation of public assets.
  5. A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge.

Explanation

Correct Answers

A:

Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries. Both organizations follow the same mandatory repository security rule without accidental creation of public assets. Apply a centrally approved policy baseline and allow only formally approved supported exceptions.

D:

Both organizations follow the same mandatory repository security rule without accidental creation of public assets. Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries. Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling.

Incorrect Answers

B:

Inspect workflow event triggers, token permissions, secret exposure paths and the executed checkout reference. It would not provide the evidence needed for the paired diagnosis and follow-up: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries. Both organizations follow the same mandatory repository security rule without accidental creation of public assets.

C:

Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations. It would not provide the evidence needed for the paired diagnosis and follow-up: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries. Both organizations follow the same mandatory repository security rule without accidental creation of public assets.

E:

A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge. It would not verify whether the proposed change works: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Both organizations follow the same mandatory repository security rule without accidental creation of public assets. Apply a centrally approved policy baseline and allow only formally approved supported exceptions.

Question 285

GitHub Enterprise administration scenario — Enforce enterprise security policy consistently. In an enterprise development environment: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. 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.

  1. Known-format test tokens trigger alerts without overwhelming benign repository files.
  2. Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access.
  3. Both organizations follow the same mandatory repository security rule without accidental creation of public assets.
  4. Apply a centrally approved policy baseline and allow only formally approved supported exceptions.
  5. Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling.
  6. Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight.

Explanation

Correct Answers

C:

Both organizations follow the same mandatory repository security rule without accidental creation of public assets. Apply a centrally approved policy baseline and allow only formally approved supported exceptions. Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling.

D:

Apply a centrally approved policy baseline and allow only formally approved supported exceptions. Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling. Both organizations follow the same mandatory repository security rule without accidental creation of public assets.

E:

Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling. Apply a centrally approved policy baseline and allow only formally approved supported exceptions. Both organizations follow the same mandatory repository security rule without accidental creation of public assets.

Incorrect Answers

A:

Known-format test tokens trigger alerts without overwhelming benign repository files. It would not independently demonstrate that the control works: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Both organizations follow the same mandatory repository security rule without accidental creation of public assets. Apply a centrally approved policy baseline and allow only formally approved supported exceptions.

B:

Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access. It is not the rule that supports the proposed change and acceptance test: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling. Apply a centrally approved policy baseline and allow only formally approved supported exceptions.

F:

Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight. It does not implement the governing rule for this approval: Two GitHub organizations use incompatible repository creation and access policies despite a corporate rule prohibiting unreviewed public exposure. Apply a centrally approved policy baseline and allow only formally approved supported exceptions. Both organizations follow the same mandatory repository security rule without accidental creation of public assets.

Question 286

GitHub Enterprise administration scenario — Protect main branches and release tags with rulesets. In an enterprise development environment: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. 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.

  1. Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls.
  2. Dependency graph completeness depends on supported manifests and any required submission or extraction configuration.
  3. Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.
  4. OAuth apps and GitHub Apps have different authorization models, token scopes and installation permission boundaries.

Explanation

Correct Answer

A:

Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls. Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.

Incorrect Answers

B:

Dependency graph completeness depends on supported manifests and any required submission or extraction configuration. It does not govern the condition described: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls.

C:

Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy. It does not govern the condition described: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls.

D:

OAuth apps and GitHub Apps have different authorization models, token scopes and installation permission boundaries. It does not govern the condition described: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls.

Question 287

GitHub Enterprise administration scenario — Protect main branches and release tags with rulesets. In an enterprise development environment: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Review provider validity signals where supported, issuing system logs, secret age and code ownership.
  2. Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs.
  3. Compare current token ownership, required API endpoints, repository selection and supported GitHub App permission model.
  4. Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations.

Explanation

Correct Answer

B:

Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs. Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.

Incorrect Answers

A:

Review provider validity signals where supported, issuing system logs, secret age and code ownership. That check would not establish the decisive facts for this condition: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs.

C:

Compare current token ownership, required API endpoints, repository selection and supported GitHub App permission model. That check would not establish the decisive facts for this condition: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs.

D:

Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations. That check would not establish the decisive facts for this condition: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs.

Question 288

GitHub Enterprise administration scenario — Protect main branches and release tags with rulesets. In an enterprise development environment: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. 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.

  1. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.
  2. Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure.
  3. Enable appropriate external collection before incidents and document search sources by event type.
  4. Define and track risk-based remediation targets with approved escalation for overdue high-risk findings.

Explanation

Correct Answer

A:

Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures. Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.

Incorrect Answers

B:

Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure. That change would leave the reported problem unresolved: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.

C:

Enable appropriate external collection before incidents and document search sources by event type. That change would leave the reported problem unresolved: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.

D:

Define and track risk-based remediation targets with approved escalation for overdue high-risk findings. That change would leave the reported problem unresolved: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.

Question 289

GitHub Enterprise administration scenario — Protect main branches and release tags with rulesets. In an enterprise development environment: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. 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.

  1. Inspect the active branch rulesets, required tools, alert thresholds and the checkout of the merge commit.
  2. A representative recognized test secret is blocked before merge and all bypasses are attributable.
  3. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.
  4. Inspect the application's authorization flow, granted scopes or granular installation permissions, and its repository targets.
  5. Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs.

Explanation

Correct Answers

C:

Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits. Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs. Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls.

E:

Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.

Incorrect Answers

A:

Inspect the active branch rulesets, required tools, alert thresholds and the checkout of the merge commit. It would not provide the evidence needed for the paired diagnosis and follow-up: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.

B:

A representative recognized test secret is blocked before merge and all bypasses are attributable. It would not verify whether the proposed change works: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.

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: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.

Question 290

GitHub Enterprise administration scenario — Protect main branches and release tags with rulesets. In an enterprise development environment: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. 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.

  1. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.
  2. Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls.
  3. Evaluate the product's supported integration model and approve only the least-privilege application type and rights.
  4. The bot comments in its assigned repository and access checks fail for unrelated private repositories.
  5. Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.
  6. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.

Explanation

Correct Answers

A:

Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures. Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls.

B:

Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.

F:

Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures. Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.

Incorrect Answers

C:

Evaluate the product's supported integration model and approve only the least-privilege application type and rights. It does not implement the governing rule for this approval: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.

D:

The bot comments in its assigned repository and access checks fail for unrelated private repositories. It would not independently demonstrate that the control works: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.

E:

Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy. It is not the rule that supports the proposed change and acceptance test: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.

GitHub Administration (GH-100) Practice Tests