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 23

Question 220

GitHub Enterprise administration scenario — Define scheduled maintenance roles for self-hosted systems. In an enterprise development environment: A GitHub Enterprise Server appliance upgrade is scheduled, but networking, storage and application owners each assume a different party will test recovery. 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. Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats.
  2. Assign accountable operators and rehearse key recovery checks with a documented maintenance change.
  3. The upgraded service handles representative Git, authentication and automation tasks and restore steps are available.
  4. Self-hosted service maintenance requires named responsibilities across infrastructure, software and dependent integrations.
  5. Representative repositories enforce the required approvals while low-risk teams retain permitted flexibility.
  6. Enterprise Cloud data-residency options have eligibility and account-model prerequisites that must be examined before procurement.

Explanation

Correct Answers

B:

Assign accountable operators and rehearse key recovery checks with a documented maintenance change. Self-hosted service maintenance requires named responsibilities across infrastructure, software and dependent integrations. The upgraded service handles representative Git, authentication and automation tasks and restore steps are available.

C:

The upgraded service handles representative Git, authentication and automation tasks and restore steps are available. Assign accountable operators and rehearse key recovery checks with a documented maintenance change. Self-hosted service maintenance requires named responsibilities across infrastructure, software and dependent integrations.

D:

Self-hosted service maintenance requires named responsibilities across infrastructure, software and dependent integrations. Assign accountable operators and rehearse key recovery checks with a documented maintenance change. The upgraded service handles representative Git, authentication and automation tasks and restore steps are available.

Incorrect Answers

A:

Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats. It does not implement the governing rule for this approval: A GitHub Enterprise Server appliance upgrade is scheduled, but networking, storage and application owners each assume a different party will test recovery. Assign accountable operators and rehearse key recovery checks with a documented maintenance change. The upgraded service handles representative Git, authentication and automation tasks and restore steps are available.

E:

Representative repositories enforce the required approvals while low-risk teams retain permitted flexibility. It would not independently demonstrate that the control works: A GitHub Enterprise Server appliance upgrade is scheduled, but networking, storage and application owners each assume a different party will test recovery. The upgraded service handles representative Git, authentication and automation tasks and restore steps are available. Assign accountable operators and rehearse key recovery checks with a documented maintenance change.

F:

Enterprise Cloud data-residency options have eligibility and account-model prerequisites that must be examined before procurement. It is not the rule that supports the proposed change and acceptance test: A GitHub Enterprise Server appliance upgrade is scheduled, but networking, storage and application owners each assume a different party will test recovery. Self-hosted service maintenance requires named responsibilities across infrastructure, software and dependent integrations. Assign accountable operators and rehearse key recovery checks with a documented maintenance change.

Question 221

GitHub Enterprise administration scenario — Create scalable enterprise user-support triage. In an enterprise development environment: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. 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. Routine organization and repository access configuration is generally within administrator responsibility before vendor escalation.
  2. Support governance should delegate routine permission management and publish escalation boundaries while protecting privileged administrator actions.
  3. GitHub feature availability can depend on deployment type, enterprise version and enabled plan.
  4. License optimization requires comparing actual billable account assignments with effective employee and collaborator entitlements.

Explanation

Correct Answer

B:

Support governance should delegate routine permission management and publish escalation boundaries while protecting privileged administrator actions. Classify recent tickets by issue, appropriate organization role, support entitlement and time to resolution. Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria.

Incorrect Answers

A:

Routine organization and repository access configuration is generally within administrator responsibility before vendor escalation. It does not govern the condition described: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Support governance should delegate routine permission management and publish escalation boundaries while protecting privileged administrator actions.

C:

GitHub feature availability can depend on deployment type, enterprise version and enabled plan. It does not govern the condition described: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Support governance should delegate routine permission management and publish escalation boundaries while protecting privileged administrator actions.

D:

License optimization requires comparing actual billable account assignments with effective employee and collaborator entitlements. It does not govern the condition described: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Support governance should delegate routine permission management and publish escalation boundaries while protecting privileged administrator actions.

Question 222

GitHub Enterprise administration scenario — Create scalable enterprise user-support triage. In an enterprise development environment: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Compare approved legal regions, supported enterprise types and the team's external collaboration requirements.
  2. Compare release records, protected branch rules, tag ownership and deployment build provenance.
  3. Review affected repositories, current Actions policy, change window and the proposed exemption scope.
  4. Classify recent tickets by issue, appropriate organization role, support entitlement and time to resolution.

Explanation

Correct Answer

D:

Classify recent tickets by issue, appropriate organization role, support entitlement and time to resolution. Support governance should delegate routine permission management and publish escalation boundaries while protecting privileged administrator actions. Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria.

Incorrect Answers

A:

Compare approved legal regions, supported enterprise types and the team's external collaboration requirements. That check would not establish the decisive facts for this condition: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Classify recent tickets by issue, appropriate organization role, support entitlement and time to resolution.

B:

Compare release records, protected branch rules, tag ownership and deployment build provenance. That check would not establish the decisive facts for this condition: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Classify recent tickets by issue, appropriate organization role, support entitlement and time to resolution.

C:

Review affected repositories, current Actions policy, change window and the proposed exemption scope. That check would not establish the decisive facts for this condition: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Classify recent tickets by issue, appropriate organization role, support entitlement and time to resolution.

Question 223

GitHub Enterprise administration scenario — Create scalable enterprise user-support triage. In an enterprise development environment: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. 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. Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats.
  2. Collect the supported diagnostics and open an authorized support case while retaining access-control and data-handling protections.
  3. Stage the policy change in a representative pilot and obtain cross-organization owner approval before rollout.
  4. Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria.

Explanation

Correct Answer

D:

Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria. Classify recent tickets by issue, appropriate organization role, support entitlement and time to resolution. Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval.

Incorrect Answers

A:

Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats. That change would leave the reported problem unresolved: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria.

B:

Collect the supported diagnostics and open an authorized support case while retaining access-control and data-handling protections. That change would leave the reported problem unresolved: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria.

C:

Stage the policy change in a representative pilot and obtain cross-organization owner approval before rollout. That change would leave the reported problem unresolved: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria.

Question 224

GitHub Enterprise administration scenario — Create scalable enterprise user-support triage. In an enterprise development environment: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. 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. Classify recent tickets by issue, appropriate organization role, support entitlement and time to resolution.
  2. Check the installed GHES release, product documentation, feature prerequisites and enterprise license capabilities.
  3. Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval.
  4. Every active organization appears in governance and licensing records with responsible owners.
  5. Compare release risk tiers, current branch rulesets, CODEOWNERS usage and stakeholder approval requirements.

Explanation

Correct Answers

A:

Classify recent tickets by issue, appropriate organization role, support entitlement and time to resolution. Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval. Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria.

C:

Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval. Classify recent tickets by issue, appropriate organization role, support entitlement and time to resolution. Support governance should delegate routine permission management and publish escalation boundaries while protecting privileged administrator actions.

Incorrect Answers

B:

Check the installed GHES release, product documentation, feature prerequisites and enterprise license capabilities. It would not provide the evidence needed for the paired diagnosis and follow-up: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Classify recent tickets by issue, appropriate organization role, support entitlement and time to resolution. Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval.

D:

Every active organization appears in governance and licensing records with responsible owners. It would not verify whether the proposed change works: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval. Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria.

E:

Compare release risk tiers, current branch rulesets, CODEOWNERS usage and stakeholder approval requirements. It would not provide the evidence needed for the paired diagnosis and follow-up: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Classify recent tickets by issue, appropriate organization role, support entitlement and time to resolution. Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval.

Question 225

GitHub Enterprise administration scenario — Create scalable enterprise user-support triage. In an enterprise development environment: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. 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. Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria.
  2. Choose a currently supported regional configuration only after a verified compatibility and migration assessment.
  3. Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval.
  4. Enterprise-level settings can affect many organizations and warrant staged change control and rollback plans.
  5. Spending alerts fire at planned thresholds and critical production work retains the agreed capacity.
  6. Support governance should delegate routine permission management and publish escalation boundaries while protecting privileged administrator actions.

Explanation

Correct Answers

A:

Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria. Support governance should delegate routine permission management and publish escalation boundaries while protecting privileged administrator actions. Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval.

C:

Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval. Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria. Support governance should delegate routine permission management and publish escalation boundaries while protecting privileged administrator actions.

F:

Support governance should delegate routine permission management and publish escalation boundaries while protecting privileged administrator actions. Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria. Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval.

Incorrect Answers

B:

Choose a currently supported regional configuration only after a verified compatibility and migration assessment. It does not implement the governing rule for this approval: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria. Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval.

D:

Enterprise-level settings can affect many organizations and warrant staged change control and rollback plans. It is not the rule that supports the proposed change and acceptance test: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Support governance should delegate routine permission management and publish escalation boundaries while protecting privileged administrator actions. Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria.

E:

Spending alerts fire at planned thresholds and critical production work retains the agreed capacity. It would not independently demonstrate that the control works: GitHub adoption grows across hundreds of teams, and every routine team invitation question reaches the limited enterprise-owner group. Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval. Publish a self-service runbook with clear organization-admin tasks and vendor-support escalation criteria.

Question 226

GitHub Enterprise administration scenario — Enable code scanning with an appropriate supported setup. In an enterprise development environment: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. 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. Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase.
  2. Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats.
  3. Deleting committed text does not revoke an already exposed credential or erase all earlier history and copies.
  4. SAML-protected resources can require token authorization independent of interactive account sign-in.

Explanation

Correct Answer

A:

Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase. Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status. Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners.

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 Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase.

C:

Deleting committed text does not revoke an already exposed credential or erase all earlier history and copies. It does not govern the condition described: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase.

D:

SAML-protected resources can require token authorization independent of interactive account sign-in. It does not govern the condition described: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase.

Question 227

GitHub Enterprise administration scenario — Enable code scanning with an appropriate supported setup. In an enterprise development environment: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Check the repository's private advisory facilities, downstream impact and the reporter's preferred disclosure channel.
  2. Collect alert severity, exploitability, asset criticality, creation time and current assigned owner.
  3. Review the requested repository selection, granular permissions, account owner and organization token policy.
  4. Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status.

Explanation

Correct Answer

D:

Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status. Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase. Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners.

Incorrect Answers

A:

Check the repository's private advisory facilities, downstream impact and the reporter's preferred disclosure channel. That check would not establish the decisive facts for this condition: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status.

B:

Collect alert severity, exploitability, asset criticality, creation time and current assigned owner. That check would not establish the decisive facts for this condition: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status.

C:

Review the requested repository selection, granular permissions, account owner and organization token policy. That check would not establish the decisive facts for this condition: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status.

Question 228

GitHub Enterprise administration scenario — Enable code scanning with an appropriate supported setup. In an enterprise development environment: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. 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. Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate.
  2. Enable supported API request audit streaming and correlated source IP evidence with privacy approvals and health checks.
  3. Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries.
  4. Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners.

Explanation

Correct Answer

D:

Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners. Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status. A new test change produces a completed analysis result and the security team can inspect any alerts.

Incorrect Answers

A:

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 Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners.

B:

Enable supported API request audit streaming and correlated source IP evidence with privacy approvals and health checks. That change would leave the reported problem unresolved: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners.

C:

Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries. That change would leave the reported problem unresolved: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners.

Question 229

GitHub Enterprise administration scenario — Enable code scanning with an appropriate supported setup. In an enterprise development environment: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. 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. Investigators can retrieve a test Git event from the archival system beyond the product's shorter native window.
  2. A new test change produces a completed analysis result and the security team can inspect any alerts.
  3. Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status.
  4. Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options.
  5. Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps.

Explanation

Correct Answers

B:

A new test change produces a completed analysis result and the security team can inspect any alerts. Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status. Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase.

C:

Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status. A new test change produces a completed analysis result and the security team can inspect any alerts. Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners.

Incorrect Answers

A:

Investigators can retrieve a test Git event from the archival system beyond the product's shorter native window. It would not verify whether the proposed change works: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. A new test change produces a completed analysis result and the security team can inspect any alerts. Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners.

D:

Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options. It would not provide the evidence needed for the paired diagnosis and follow-up: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status. A new test change produces a completed analysis result and the security team can inspect any alerts.

E:

Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps. It would not provide the evidence needed for the paired diagnosis and follow-up: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status. A new test change produces a completed analysis result and the security team can inspect any alerts.

Question 230

GitHub Enterprise administration scenario — Enable code scanning with an appropriate supported setup. In an enterprise development environment: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. 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 new test change produces a completed analysis result and the security team can inspect any alerts.
  2. Coordinated vulnerability disclosure needs restricted collaboration and a tracked remediation process.
  3. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.
  4. Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase.
  5. A pull request adding a known-risk dependency is flagged before merge while safe updates pass.
  6. Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners.

Explanation

Correct Answers

A:

A new test change produces a completed analysis result and the security team can inspect any alerts. Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners. Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase.

D:

Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase. Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners. A new test change produces a completed analysis result and the security team can inspect any alerts.

F:

Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners. Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase. A new test change produces a completed analysis result and the security team can inspect any alerts.

Incorrect Answers

B:

Coordinated vulnerability disclosure needs restricted collaboration and a tracked remediation process. It is not the rule that supports the proposed change and acceptance test: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase. Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners.

C:

Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures. It does not implement the governing rule for this approval: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners. A new test change produces a completed analysis result and the security team can inspect any alerts.

E:

A pull request adding a known-risk dependency is flagged before merge while safe updates pass. It would not independently demonstrate that the control works: A Python service has no static analysis results in GitHub although the development team assumes repository creation automatically starts CodeQL checks. A new test change produces a completed analysis result and the security team can inspect any alerts. Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners.

GitHub Administration (GH-100) Practice Tests