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 28

Question 270

GitHub Enterprise administration scenario — Manage a private vulnerability advisory. In an enterprise development environment: A maintainer learns privately about an exploitable library flaw but proposes opening a public issue before a fixed version is ready. 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. The contractor's compromised session cannot read repositories and legitimate access is reissued only after approved recovery.
  2. Retain required reviews and use signature verification as a complementary control when supported and justified.
  3. Coordinated vulnerability disclosure needs restricted collaboration and a tracked remediation process.
  4. Maintainers and the reporter can collaborate privately and a patched release has a documented disclosure timeline.
  5. API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance.
  6. Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure.

Explanation

Correct Answers

C:

Coordinated vulnerability disclosure needs restricted collaboration and a tracked remediation process. Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure. Maintainers and the reporter can collaborate privately and a patched release has a documented disclosure timeline.

D:

Maintainers and the reporter can collaborate privately and a patched release has a documented disclosure timeline. Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure. Coordinated vulnerability disclosure needs restricted collaboration and a tracked remediation process.

F:

Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure. Coordinated vulnerability disclosure needs restricted collaboration and a tracked remediation process. Maintainers and the reporter can collaborate privately and a patched release has a documented disclosure timeline.

Incorrect Answers

A:

The contractor's compromised session cannot read repositories and legitimate access is reissued only after approved recovery. It would not independently demonstrate that the control works: A maintainer learns privately about an exploitable library flaw but proposes opening a public issue before a fixed version is ready. Maintainers and the reporter can collaborate privately and a patched release has a documented disclosure timeline. Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure.

B:

Retain required reviews and use signature verification as a complementary control when supported and justified. It does not implement the governing rule for this approval: A maintainer learns privately about an exploitable library flaw but proposes opening a public issue before a fixed version is ready. Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure. Maintainers and the reporter can collaborate privately and a patched release has a documented disclosure timeline.

E:

API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance. It is not the rule that supports the proposed change and acceptance test: A maintainer learns privately about an exploitable library flaw but proposes opening a public issue before a fixed version is ready. Coordinated vulnerability disclosure needs restricted collaboration and a tracked remediation process. Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure.

Question 271

GitHub Enterprise administration scenario — Apply dependency review to risky pull requests. In an enterprise development environment: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. 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. Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories.
  2. Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone.
  3. Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase.
  4. External enterprise audit log streaming can provide independently retained event copies beyond the product's limited interactive history.

Explanation

Correct Answer

A:

Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories. Compare before-and-after dependency manifests, newly introduced packages and configured review policy. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.

Incorrect Answers

B:

Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone. It does not govern the condition described: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories.

C:

Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase. It does not govern the condition described: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories.

D:

External enterprise audit log streaming can provide independently retained event copies beyond the product's limited interactive history. It does not govern the condition described: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories.

Question 272

GitHub Enterprise administration scenario — Apply dependency review to risky pull requests. In an enterprise development environment: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs.
  2. Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations.
  3. Review available enterprise audit streaming options, required API events, source IP visibility and SIEM retention.
  4. Compare before-and-after dependency manifests, newly introduced packages and configured review policy.

Explanation

Correct Answer

D:

Compare before-and-after dependency manifests, newly introduced packages and configured review policy. Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.

Incorrect Answers

A:

Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs. That check would not establish the decisive facts for this condition: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. Compare before-and-after dependency manifests, newly introduced packages and configured review policy.

B:

Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations. That check would not establish the decisive facts for this condition: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. Compare before-and-after dependency manifests, newly introduced packages and configured review policy.

C:

Review available enterprise audit streaming options, required API events, source IP visibility and SIEM retention. That check would not establish the decisive facts for this condition: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. Compare before-and-after dependency manifests, newly introduced packages and configured review policy.

Question 273

GitHub Enterprise administration scenario — Apply dependency review to risky pull requests. In an enterprise development environment: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. 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. Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token.
  2. Require validated triage categories with documented revocation and exception decisions for exposed tokens.
  3. Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate.
  4. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.

Explanation

Correct Answer

D:

Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement. Compare before-and-after dependency manifests, newly introduced packages and configured review policy. A pull request adding a known-risk dependency is flagged before merge while safe updates pass.

Incorrect Answers

A:

Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token. That change would leave the reported problem unresolved: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.

B:

Require validated triage categories with documented revocation and exception decisions for exposed tokens. That change would leave the reported problem unresolved: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.

C:

Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate. That change would leave the reported problem unresolved: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.

Question 274

GitHub Enterprise administration scenario — Apply dependency review to risky pull requests. In an enterprise development environment: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. 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. Compare before-and-after dependency manifests, newly introduced packages and configured review policy.
  2. A pull request adding a known-risk dependency is flagged before merge while safe updates pass.
  3. A simulated sensitive API action produces attributable retained evidence in the security monitoring destination.
  4. Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy.
  5. Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events.

Explanation

Correct Answers

A:

Compare before-and-after dependency manifests, newly introduced packages and configured review policy. A pull request adding a known-risk dependency is flagged before merge while safe updates pass. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.

B:

A pull request adding a known-risk dependency is flagged before merge while safe updates pass. Compare before-and-after dependency manifests, newly introduced packages and configured review policy. Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories.

Incorrect Answers

C:

A simulated sensitive API action produces attributable retained evidence in the security monitoring destination. It would not verify whether the proposed change works: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. A pull request adding a known-risk dependency is flagged before merge while safe updates pass. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.

D:

Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy. It would not provide the evidence needed for the paired diagnosis and follow-up: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. Compare before-and-after dependency manifests, newly introduced packages and configured review policy. A pull request adding a known-risk dependency is flagged before merge while safe updates pass.

E:

Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events. It would not provide the evidence needed for the paired diagnosis and follow-up: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. Compare before-and-after dependency manifests, newly introduced packages and configured review policy. A pull request adding a known-risk dependency is flagged before merge while safe updates pass.

Question 275

GitHub Enterprise administration scenario — Apply dependency review to risky pull requests. In an enterprise development environment: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. 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. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.
  2. Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
  3. A pull request adding a known-risk dependency is flagged before merge while safe updates pass.
  4. Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement.
  5. The user can complete required labeling without giving an untrusted extension access to confidential source.
  6. Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories.

Explanation

Correct Answers

A:

Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement. Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories. A pull request adding a known-risk dependency is flagged before merge while safe updates pass.

C:

A pull request adding a known-risk dependency is flagged before merge while safe updates pass. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement. Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories.

F:

Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement. A pull request adding a known-risk dependency is flagged before merge while safe updates pass.

Incorrect Answers

B:

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 pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.

D:

Define and dry-run an appropriate custom secret pattern under security owner review before broad enforcement. It does not implement the governing rule for this approval: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement. A pull request adding a known-risk dependency is flagged before merge while safe updates pass.

E:

The user can complete required labeling without giving an untrusted extension access to confidential source. It would not independently demonstrate that the control works: A pull request introduces several third-party packages, including a vulnerable transitive dependency, but only unit tests are required before merge. A pull request adding a known-risk dependency is flagged before merge while safe updates pass. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.

Question 276

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. 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. Organization-level security configuration can provide consistent supported coverage when applied and monitored across repositories.
  2. Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats.
  3. Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability.
  4. Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses.

Explanation

Correct Answer

A:

Organization-level security configuration can provide consistent supported coverage when applied and monitored across repositories. Compare current repository security setting inventories, configured baseline policies and exception classes. Create and apply an approved security baseline to eligible repositories with exception ownership and periodic coverage reports.

Incorrect Answers

B:

Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats. It does not govern the condition described: 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.

C:

Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability. It does not govern the condition described: 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.

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: 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.

Question 277

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. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Review required events, streaming destination, service ownership, delivery health and external retention policy.
  2. Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities.
  3. Compare current repository security setting inventories, configured baseline policies and exception classes.
  4. Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options.

Explanation

Correct Answer

C:

Compare current repository security setting inventories, configured baseline policies and exception classes. 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.

Incorrect Answers

A:

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 security team enables secret scanning and code scanning one repository at a time, but newly created organization repositories repeatedly lack these controls. Compare current repository security setting inventories, configured baseline policies and exception classes.

B:

Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities. That check would not establish the decisive facts for this condition: A security team enables secret scanning and code scanning one repository at a time, but newly created organization repositories repeatedly lack these controls. Compare current repository security setting inventories, configured baseline policies and exception classes.

D:

Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options. That check would not establish the decisive facts for this condition: A security team enables secret scanning and code scanning one repository at a time, but newly created organization repositories repeatedly lack these controls. Compare current repository security setting inventories, configured baseline policies and exception classes.

Question 278

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. 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. Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance.
  2. Create and apply an approved security baseline to eligible repositories with exception ownership and periodic coverage reports.
  3. Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership.
  4. Enable appropriate external collection before incidents and document search sources by event type.

Explanation

Correct Answer

B:

Create and apply an approved security baseline to eligible repositories with exception ownership and periodic coverage reports. Compare current repository security setting inventories, configured baseline policies and exception classes. Sample existing and new repositories have the required supported scanning controls or documented exceptions.

Incorrect Answers

A:

Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance. That change would leave the reported problem unresolved: 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.

C:

Enable supported dependency intelligence and alerting, then assign appropriate alert triage ownership. That change would leave the reported problem unresolved: 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.

D:

Enable appropriate external collection before incidents and document search sources by event type. That change would leave the reported problem unresolved: 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.

Question 279

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. 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 test installation token signed through the new approved key works and the compromised key is unusable.
  2. Review the app manifest permissions, selected repositories and the organization policy controlling installations.
  3. Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy.
  4. Compare current repository security setting inventories, configured baseline policies and exception classes.
  5. Sample existing and new repositories have the required supported scanning controls or documented exceptions.

Explanation

Correct Answers

D:

Compare current repository security setting inventories, configured baseline policies and exception classes. 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.

E:

Sample existing and new repositories have the required supported scanning controls or documented exceptions. Compare current repository security setting inventories, configured baseline policies and exception classes. Organization-level security configuration can provide consistent supported coverage when applied and monitored across repositories.

Incorrect Answers

A:

A test installation token signed through the new approved key works and the compromised key is unusable. It would not verify whether the proposed change 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.

B:

Review the app manifest permissions, selected repositories and the organization policy controlling installations. It would not provide the evidence needed for the paired diagnosis and follow-up: A security team enables secret scanning and code scanning one repository at a time, but newly created organization repositories repeatedly lack these controls. Compare current repository security setting inventories, configured baseline policies and exception classes. Sample existing and new repositories have the required supported scanning controls or documented exceptions.

C:

Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy. It would not provide the evidence needed for the paired diagnosis and follow-up: A security team enables secret scanning and code scanning one repository at a time, but newly created organization repositories repeatedly lack these controls. Compare current repository security setting inventories, configured baseline policies and exception classes. Sample existing and new repositories have the required supported scanning controls or documented exceptions.

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.

GitHub Administration (GH-100) Practice Tests