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 39

Question 380

GitHub Enterprise administration scenario — Deny an OAuth integration that requests excessive account scope. In an enterprise development environment: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. 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 user can complete required labeling without giving an untrusted extension access to confidential source.
  2. Fix dependency graph inputs or supported submission process and retest the nested component.
  3. Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.
  4. Enterprise security governance needs risk-tiered alert owners and observable remediation accountability.
  5. Sample existing and new repositories have the required supported scanning controls or documented exceptions.
  6. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation.

Explanation

Correct Answers

A:

The user can complete required labeling without giving an untrusted extension access to confidential source. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation. Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.

C:

Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation. The user can complete required labeling without giving an untrusted extension access to confidential source.

F:

Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation. Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy. The user can complete required labeling without giving an untrusted extension access to confidential source.

Incorrect Answers

B:

Fix dependency graph inputs or supported submission process and retest the nested component. It does not implement the governing rule for this approval: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation. The user can complete required labeling without giving an untrusted extension access to confidential source.

D:

Enterprise security governance needs risk-tiered alert owners and observable remediation accountability. It is not the rule that supports the proposed change and acceptance test: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation.

E:

Sample existing and new repositories have the required supported scanning controls or documented exceptions. It would not independently demonstrate that the control works: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. The user can complete required labeling without giving an untrusted extension access to confidential source. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation.

Question 381

GitHub Enterprise administration scenario — Respond to compromised outside collaborator access. In an enterprise development environment: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. 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. Security logging coverage varies by audit method and event type, so detailed API request telemetry should be enabled deliberately where supported.
  2. Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite.
  3. Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access.
  4. SAML-protected resources can require token authorization independent of interactive account sign-in.

Explanation

Correct Answer

C:

Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access. Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners.

Incorrect Answers

A:

Security logging coverage varies by audit method and event type, so detailed API request telemetry should be enabled deliberately where supported. It does not govern the condition described: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access.

B:

Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite. It does not govern the condition described: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access.

D:

SAML-protected resources can require token authorization independent of interactive account sign-in. It does not govern the condition described: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access.

Question 382

GitHub Enterprise administration scenario — Respond to compromised outside collaborator access. In an enterprise development environment: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy.
  2. Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets.
  3. Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance.
  4. Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options.

Explanation

Correct Answer

A:

Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy. Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners.

Incorrect Answers

B:

Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets. That check would not establish the decisive facts for this condition: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy.

C:

Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance. That check would not establish the decisive facts for this condition: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy.

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: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy.

Question 383

GitHub Enterprise administration scenario — Respond to compromised outside collaborator access. In an enterprise development environment: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. 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 supported security update pull requests with owned reviewers and controlled merge rules.
  2. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners.
  3. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.
  4. Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.

Explanation

Correct Answer

B:

Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners. Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy. The contractor's compromised session cannot read repositories and legitimate access is reissued only after approved recovery.

Incorrect Answers

A:

Enable supported security update pull requests with owned reviewers and controlled merge rules. That change would leave the reported problem unresolved: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners.

C:

Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement. That change would leave the reported problem unresolved: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners.

D:

Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results. That change would leave the reported problem unresolved: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners.

Question 384

GitHub Enterprise administration scenario — Respond to compromised outside collaborator access. In an enterprise development environment: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. 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. Assess the key identity, installed app permissions, issued token activity and supported key rotation window.
  2. Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy.
  3. The current repository has the correct visibility and incident records identify each necessary external remediation.
  4. Check audit-log access methods, required event classes, Git event retention and previous stream coverage.
  5. The contractor's compromised session cannot read repositories and legitimate access is reissued only after approved recovery.

Explanation

Correct Answers

B:

Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy. The contractor's compromised session cannot read repositories and legitimate access is reissued only after approved recovery. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners.

E:

The contractor's compromised session cannot read repositories and legitimate access is reissued only after approved recovery. Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy. Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access.

Incorrect Answers

A:

Assess the key identity, installed app permissions, issued token activity and supported key rotation window. It would not provide the evidence needed for the paired diagnosis and follow-up: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy. The contractor's compromised session cannot read repositories and legitimate access is reissued only after approved recovery.

C:

The current repository has the correct visibility and incident records identify each necessary external remediation. It would not verify whether the proposed change works: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. The contractor's compromised session cannot read repositories and legitimate access is reissued only after approved recovery. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners.

D:

Check audit-log access methods, required event classes, Git event retention and previous stream coverage. It would not provide the evidence needed for the paired diagnosis and follow-up: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy. The contractor's compromised session cannot read repositories and legitimate access is reissued only after approved recovery.

Question 385

GitHub Enterprise administration scenario — Respond to compromised outside collaborator access. In an enterprise development environment: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. 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. Produce a repeatable cross-organization effective-control report and assign remediation to owners of exceptions.
  2. The user can complete required labeling without giving an untrusted extension access to confidential source.
  3. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners.
  4. Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access.
  5. The contractor's compromised session cannot read repositories and legitimate access is reissued only after approved recovery.
  6. GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary.

Explanation

Correct Answers

C:

Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners. Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access. The contractor's compromised session cannot read repositories and legitimate access is reissued only after approved recovery.

D:

Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners. The contractor's compromised session cannot read repositories and legitimate access is reissued only after approved recovery.

E:

The contractor's compromised session cannot read repositories and legitimate access is reissued only after approved recovery. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners. Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access.

Incorrect Answers

A:

Produce a repeatable cross-organization effective-control report and assign remediation to owners of exceptions. It does not implement the governing rule for this approval: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners. The contractor's compromised session cannot read repositories and legitimate access is reissued only after approved recovery.

B:

The user can complete required labeling without giving an untrusted extension access to confidential source. It would not independently demonstrate that the control works: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. The contractor's compromised session cannot read repositories and legitimate access is reissued only after approved recovery. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners.

F:

GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary. It is not the rule that supports the proposed change and acceptance test: An external contractor account logs in from unfamiliar locations and downloads several repositories beyond its current contract. Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access. Suspend or revoke the affected access, preserve logs and coordinate credential recovery with the responsible vendor and owners.

Question 386

GitHub Enterprise administration scenario — Minimize accidental repository data disclosure. In an enterprise development environment: A development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. 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. Fine-grained personal access and approval policies can limit an integration to the minimum required resources.
  2. Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access.
  3. Deleting committed text does not revoke an already exposed credential or erase all earlier history and copies.
  4. Public exposure and historical clones require incident scoping beyond a later repository visibility change.

Explanation

Correct Answer

D:

Public exposure and historical clones require incident scoping beyond a later repository visibility change. Determine affected file content, publication duration, forks, caches and any included credentials or personal data. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.

Incorrect Answers

A:

Fine-grained personal access and approval policies can limit an integration to the minimum required resources. It does not govern the condition described: A development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. Public exposure and historical clones require incident scoping beyond a later repository visibility change.

B:

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 development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. Public exposure and historical clones require incident scoping beyond a later repository visibility change.

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 development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. Public exposure and historical clones require incident scoping beyond a later repository visibility change.

Question 387

GitHub Enterprise administration scenario — Minimize accidental repository data disclosure. In an enterprise development environment: A development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Compare before-and-after dependency manifests, newly introduced packages and configured review policy.
  2. Determine affected file content, publication duration, forks, caches and any included credentials or personal data.
  3. Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events.
  4. Review the requested repository selection, granular permissions, account owner and organization token policy.

Explanation

Correct Answer

B:

Determine affected file content, publication duration, forks, caches and any included credentials or personal data. Public exposure and historical clones require incident scoping beyond a later repository visibility change. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.

Incorrect Answers

A:

Compare before-and-after dependency manifests, newly introduced packages and configured review policy. That check would not establish the decisive facts for this condition: A development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. Determine affected file content, publication duration, forks, caches and any included credentials or personal data.

C:

Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events. That check would not establish the decisive facts for this condition: A development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. Determine affected file content, publication duration, forks, caches and any included credentials or personal data.

D:

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 development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. Determine affected file content, publication duration, forks, caches and any included credentials or personal data.

Question 388

GitHub Enterprise administration scenario — Minimize accidental repository data disclosure. In an enterprise development environment: A development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. 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. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.
  3. Enable supported push protection and establish a documented response for verified false positives and genuine exposures.
  4. Enable appropriate external collection before incidents and document search sources by event type.

Explanation

Correct Answer

B:

Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process. Determine affected file content, publication duration, forks, caches and any included credentials or personal data. The current repository has the correct visibility and incident records identify each necessary external remediation.

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 development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.

C:

Enable supported push protection and establish a documented response for verified false positives and genuine exposures. That change would leave the reported problem unresolved: A development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.

D:

Enable appropriate external collection before incidents and document search sources by event type. That change would leave the reported problem unresolved: A development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.

Question 389

GitHub Enterprise administration scenario — Minimize accidental repository data disclosure. In an enterprise development environment: A development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. 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 current signatures, ruleset review requirements and known risks in the change authorization workflow.
  2. A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge.
  3. Determine affected file content, publication duration, forks, caches and any included credentials or personal data.
  4. Review the app manifest permissions, selected repositories and the organization policy controlling installations.
  5. The current repository has the correct visibility and incident records identify each necessary external remediation.

Explanation

Correct Answers

C:

Determine affected file content, publication duration, forks, caches and any included credentials or personal data. The current repository has the correct visibility and incident records identify each necessary external remediation. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.

E:

The current repository has the correct visibility and incident records identify each necessary external remediation. Determine affected file content, publication duration, forks, caches and any included credentials or personal data. Public exposure and historical clones require incident scoping beyond a later repository visibility change.

Incorrect Answers

A:

Inspect current signatures, ruleset review requirements and known risks in the change authorization workflow. It would not provide the evidence needed for the paired diagnosis and follow-up: A development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. Determine affected file content, publication duration, forks, caches and any included credentials or personal data. The current repository has the correct visibility and incident records identify each necessary external remediation.

B:

A representative vulnerable dependency produces an update PR whose tests and review can be completed before merge. It would not verify whether the proposed change works: A development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. The current repository has the correct visibility and incident records identify each necessary external remediation. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.

D:

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 development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. Determine affected file content, publication duration, forks, caches and any included credentials or personal data. The current repository has the correct visibility and incident records identify each necessary external remediation.

Question 390

GitHub Enterprise administration scenario — Minimize accidental repository data disclosure. In an enterprise development environment: A development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. 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. Enable supported security update pull requests with owned reviewers and controlled merge rules.
  2. Public exposure and historical clones require incident scoping beyond a later repository visibility change.
  3. Maintainers and the reporter can collaborate privately and a patched release has a documented disclosure timeline.
  4. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.
  5. Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance.
  6. The current repository has the correct visibility and incident records identify each necessary external remediation.

Explanation

Correct Answers

B:

Public exposure and historical clones require incident scoping beyond a later repository visibility change. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process. The current repository has the correct visibility and incident records identify each necessary external remediation.

D:

Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process. Public exposure and historical clones require incident scoping beyond a later repository visibility change. The current repository has the correct visibility and incident records identify each necessary external remediation.

F:

The current repository has the correct visibility and incident records identify each necessary external remediation. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process. Public exposure and historical clones require incident scoping beyond a later repository visibility change.

Incorrect Answers

A:

Enable supported security update pull requests with owned reviewers and controlled merge rules. It does not implement the governing rule for this approval: A development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process. The current repository has the correct visibility and incident records identify each necessary external remediation.

C:

Maintainers and the reporter can collaborate privately and a patched release has a documented disclosure timeline. It would not independently demonstrate that the control works: A development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. The current repository has the correct visibility and incident records identify each necessary external remediation. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.

E:

Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance. It is not the rule that supports the proposed change and acceptance test: A development team commits internal customer configuration files to an otherwise public GitHub repository and assumes changing visibility to private eliminates all copies. Public exposure and historical clones require incident scoping beyond a later repository visibility change. Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.

GitHub Administration (GH-100) Practice Tests