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 26

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.

  1. Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
  2. An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route.
  3. Automated security update pull requests support remediation but must still pass review, compatibility and CI checks.
  4. A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge.
  5. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.
  6. 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.

Question 251

GitHub Enterprise administration scenario — Enforce secret scanning push protection. In an enterprise development environment: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. 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. Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses.
  2. Path-specific review can direct sensitive changes to authorized subject-matter owners before merge.
  3. Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase.
  4. Public exposure and historical clones require incident scoping beyond a later repository visibility change.

Explanation

Correct Answer

A:

Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses. Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance. Enable supported push protection and establish a documented response for verified false positives and genuine exposures.

Incorrect Answers

B:

Path-specific review can direct sensitive changes to authorized subject-matter owners before merge. It does not govern the condition described: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses.

C:

Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase. It does not govern the condition described: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses.

D:

Public exposure and historical clones require incident scoping beyond a later repository visibility change. It does not govern the condition described: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses.

Question 252

GitHub Enterprise administration scenario — Enforce secret scanning push protection. In an enterprise development environment: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Compare current token ownership, required API endpoints, repository selection and supported GitHub App permission model.
  2. Review provider validity signals where supported, issuing system logs, secret age and code ownership.
  3. Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies.
  4. Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance.

Explanation

Correct Answer

D:

Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance. Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses. Enable supported push protection and establish a documented response for verified false positives and genuine exposures.

Incorrect Answers

A:

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: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance.

B:

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: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance.

C:

Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies. That check would not establish the decisive facts for this condition: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance.

Question 253

GitHub Enterprise administration scenario — Enforce secret scanning push protection. In an enterprise development environment: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. 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. Enable appropriate external collection before incidents and document search sources by event type.
  2. Enable supported security update pull requests with owned reviewers and controlled merge rules.
  3. Enable supported push protection and establish a documented response for verified false positives and genuine exposures.
  4. Correct the authorized build environment for the analysis job and rerun full relevant coverage.

Explanation

Correct Answer

C:

Enable supported push protection and establish a documented response for verified false positives and genuine exposures. Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance. A representative recognized test secret is blocked before merge and all bypasses are attributable.

Incorrect Answers

A:

Enable appropriate external collection before incidents and document search sources by event type. That change would leave the reported problem unresolved: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. Enable supported push protection and establish a documented response for verified false positives and genuine exposures.

B:

Enable supported security update pull requests with owned reviewers and controlled merge rules. That change would leave the reported problem unresolved: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. Enable supported push protection and establish a documented response for verified false positives and genuine exposures.

D:

Correct the authorized build environment for the analysis job and rerun full relevant coverage. That change would leave the reported problem unresolved: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. Enable supported push protection and establish a documented response for verified false positives and genuine exposures.

Question 254

GitHub Enterprise administration scenario — Enforce secret scanning push protection. In an enterprise development environment: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. 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. A representative recognized test secret is blocked before merge and all bypasses are attributable.
  2. Compare current repository security setting inventories, configured baseline policies and exception classes.
  3. Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance.
  4. The security analysis produces a valid database and findings for the intended compiled component.
  5. Compare workspace manifests, package lockfiles, supported ecosystem behavior and current dependency graph entries.

Explanation

Correct Answers

A:

A representative recognized test secret is blocked before merge and all bypasses are attributable. Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance. Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses.

C:

Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance. A representative recognized test secret is blocked before merge and all bypasses are attributable. Enable supported push protection and establish a documented response for verified false positives and genuine exposures.

Incorrect Answers

B:

Compare current repository security setting inventories, configured baseline policies and exception classes. It would not provide the evidence needed for the paired diagnosis and follow-up: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance. A representative recognized test secret is blocked before merge and all bypasses are attributable.

D:

The security analysis produces a valid database and findings for the intended compiled component. It would not verify whether the proposed change works: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. A representative recognized test secret is blocked before merge and all bypasses are attributable. Enable supported push protection and establish a documented response for verified false positives and genuine exposures.

E:

Compare workspace manifests, package lockfiles, supported ecosystem behavior and current dependency graph entries. It would not provide the evidence needed for the paired diagnosis and follow-up: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance. A representative recognized test secret is blocked before merge and all bypasses are attributable.

Question 255

GitHub Enterprise administration scenario — Enforce secret scanning push protection. In an enterprise development environment: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. 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. A fork PR can run safe checks but cannot access production deployment credentials.
  2. Organization-level security configuration can provide consistent supported coverage when applied and monitored across repositories.
  3. Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses.
  4. Enable supported push protection and establish a documented response for verified false positives and genuine exposures.
  5. A representative recognized test secret is blocked before merge and all bypasses are attributable.
  6. Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure.

Explanation

Correct Answers

C:

Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses. Enable supported push protection and establish a documented response for verified false positives and genuine exposures. A representative recognized test secret is blocked before merge and all bypasses are attributable.

D:

Enable supported push protection and establish a documented response for verified false positives and genuine exposures. Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses. A representative recognized test secret is blocked before merge and all bypasses are attributable.

E:

A representative recognized test secret is blocked before merge and all bypasses are attributable. Enable supported push protection and establish a documented response for verified false positives and genuine exposures. Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses.

Incorrect Answers

A:

A fork PR can run safe checks but cannot access production deployment credentials. It would not independently demonstrate that the control works: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. A representative recognized test secret is blocked before merge and all bypasses are attributable. Enable supported push protection and establish a documented response for verified false positives and genuine exposures.

B:

Organization-level security configuration can provide consistent supported coverage when applied and monitored across repositories. It is not the rule that supports the proposed change and acceptance test: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses. Enable supported push protection and establish a documented response for verified false positives and genuine exposures.

F:

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: Developers repeatedly attempt to commit live cloud tokens, and existing repository alerts only notify security after the secret reaches Git history. Enable supported push protection and establish a documented response for verified false positives and genuine exposures. A representative recognized test secret is blocked before merge and all bypasses are attributable.

Question 256

GitHub Enterprise administration scenario — Define custom secret-detection patterns. In an enterprise development environment: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. 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. Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats.
  2. Automated security update pull requests support remediation but must still pass review, compatibility and CI checks.
  3. Commit identity assurance and independent code-review controls address different aspects of source integrity.
  4. Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access.

Explanation

Correct Answer

A:

Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats. Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities. Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement.

Incorrect Answers

B:

Automated security update pull requests support remediation but must still pass review, compatibility and CI checks. It does not govern the condition described: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats.

C:

Commit identity assurance and independent code-review controls address different aspects of source integrity. It does not govern the condition described: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats.

D:

Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access. It does not govern the condition described: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats.

Question 257

GitHub Enterprise administration scenario — Define custom secret-detection patterns. In an enterprise development environment: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. 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 sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities.
  3. Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs.
  4. Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits.

Explanation

Correct Answer

B:

Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities. Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats. Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement.

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 company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities.

C:

Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs. That check would not establish the decisive facts for this condition: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities.

D:

Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits. That check would not establish the decisive facts for this condition: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities.

Question 258

GitHub Enterprise administration scenario — Define custom secret-detection patterns. In an enterprise development environment: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. 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. Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
  2. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners.
  3. Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure.
  4. Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement.

Explanation

Correct Answer

D:

Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement. Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities. Known-format test tokens trigger alerts without overwhelming benign repository files.

Incorrect Answers

A:

Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results. That change would leave the reported problem unresolved: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement.

B:

Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners. That change would leave the reported problem unresolved: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement.

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: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement.

Question 259

GitHub Enterprise administration scenario — Define custom secret-detection patterns. In an enterprise development environment: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. 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 sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities.
  2. Check the repository's private advisory facilities, downstream impact and the reporter's preferred disclosure channel.
  3. Compare workspace manifests, package lockfiles, supported ecosystem behavior and current dependency graph entries.
  4. The integration continues after the creator is offboarded and only its installed repositories are reachable.
  5. Known-format test tokens trigger alerts without overwhelming benign repository files.

Explanation

Correct Answers

A:

Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities. Known-format test tokens trigger alerts without overwhelming benign repository files. Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement.

E:

Known-format test tokens trigger alerts without overwhelming benign repository files. Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities. Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats.

Incorrect Answers

B:

Check the repository's private advisory facilities, downstream impact and the reporter's preferred disclosure channel. It would not provide the evidence needed for the paired diagnosis and follow-up: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities. Known-format test tokens trigger alerts without overwhelming benign repository files.

C:

Compare workspace manifests, package lockfiles, supported ecosystem behavior and current dependency graph entries. It would not provide the evidence needed for the paired diagnosis and follow-up: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities. Known-format test tokens trigger alerts without overwhelming benign repository files.

D:

The integration continues after the creator is offboarded and only its installed repositories are reachable. It would not verify whether the proposed change works: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. Known-format test tokens trigger alerts without overwhelming benign repository files. Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement.

Question 260

GitHub Enterprise administration scenario — Define custom secret-detection patterns. In an enterprise development environment: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. 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. Signed commits can be validated, but unreviewed changes still cannot enter protected branches.
  2. Known-format test tokens trigger alerts without overwhelming benign repository files.
  3. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners.
  4. Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats.
  5. Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement.
  6. Public exposure and historical clones require incident scoping beyond a later repository visibility change.

Explanation

Correct Answers

B:

Known-format test tokens trigger alerts without overwhelming benign repository files. Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement. Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats.

D:

Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats. Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement. Known-format test tokens trigger alerts without overwhelming benign repository files.

E:

Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement. Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats. Known-format test tokens trigger alerts without overwhelming benign repository files.

Incorrect Answers

A:

Signed commits can be validated, but unreviewed changes still cannot enter protected branches. It would not independently demonstrate that the control works: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. Known-format test tokens trigger alerts without overwhelming benign repository files. Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement.

C:

Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners. It does not implement the governing rule for this approval: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement. Known-format test tokens trigger alerts without overwhelming benign repository files.

F:

Public exposure and historical clones require incident scoping beyond a later repository visibility change. It is not the rule that supports the proposed change and acceptance test: A company uses internally issued API keys that its default secret scanning rules do not detect, while employees routinely store them in scripts. Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats. Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement.

GitHub Administration (GH-100) Practice Tests