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 32

Question 310

GitHub Enterprise administration scenario — Prevent unsafe security controls on public fork contributions. In an enterprise development environment: A public repository CI job has privileged package-publishing credentials and is configured to run contributor-controlled code from fork pull requests. 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. Separate untrusted PR validation from privileged publishing and restrict secrets to reviewed trusted workflow contexts.
  2. A fork PR can run safe checks but cannot access production deployment credentials.
  3. The audit sample demonstrates required controls for every selected organization or records justified deviations.
  4. Untrusted fork code must not receive secrets or broad workflow privileges simply to perform tests.
  5. Limit the installation to the required repository with only the necessary issues or pull request permissions.
  6. Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling.

Explanation

Correct Answers

A:

Separate untrusted PR validation from privileged publishing and restrict secrets to reviewed trusted workflow contexts. Untrusted fork code must not receive secrets or broad workflow privileges simply to perform tests. A fork PR can run safe checks but cannot access production deployment credentials.

B:

A fork PR can run safe checks but cannot access production deployment credentials. Separate untrusted PR validation from privileged publishing and restrict secrets to reviewed trusted workflow contexts. Untrusted fork code must not receive secrets or broad workflow privileges simply to perform tests.

D:

Untrusted fork code must not receive secrets or broad workflow privileges simply to perform tests. Separate untrusted PR validation from privileged publishing and restrict secrets to reviewed trusted workflow contexts. A fork PR can run safe checks but cannot access production deployment credentials.

Incorrect Answers

C:

The audit sample demonstrates required controls for every selected organization or records justified deviations. It would not independently demonstrate that the control works: A public repository CI job has privileged package-publishing credentials and is configured to run contributor-controlled code from fork pull requests. A fork PR can run safe checks but cannot access production deployment credentials. Separate untrusted PR validation from privileged publishing and restrict secrets to reviewed trusted workflow contexts.

E:

Limit the installation to the required repository with only the necessary issues or pull request permissions. It does not implement the governing rule for this approval: A public repository CI job has privileged package-publishing credentials and is configured to run contributor-controlled code from fork pull requests. Separate untrusted PR validation from privileged publishing and restrict secrets to reviewed trusted workflow contexts. A fork PR can run safe checks but cannot access production deployment credentials.

F:

Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling. It is not the rule that supports the proposed change and acceptance test: A public repository CI job has privileged package-publishing credentials and is configured to run contributor-controlled code from fork pull requests. Untrusted fork code must not receive secrets or broad workflow privileges simply to perform tests. Separate untrusted PR validation from privileged publishing and restrict secrets to reviewed trusted workflow contexts.

Question 311

GitHub Enterprise administration scenario — Enable private vulnerability reporting responsibly. In an enterprise development environment: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. The administrator must identify the controlling access, governance or platform principle rather than an unrelated configuration fix. Which principle BEST addresses this condition? Choose ONE best answer.

  1. Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure.
  2. Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance.
  3. Repository visibility settings define different reader populations and must be evaluated against data classification.
  4. Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling.

Explanation

Correct Answer

A:

Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure. Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy. Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions.

Incorrect Answers

B:

Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance. It does not govern the condition described: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure.

C:

Repository visibility settings define different reader populations and must be evaluated against data classification. It does not govern the condition described: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure.

D:

Enterprise-wide security controls should be defined at an enforceable scope with accountable exception handling. It does not govern the condition described: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure.

Question 312

GitHub Enterprise administration scenario — Enable private vulnerability reporting responsibly. In an enterprise development environment: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Determine affected file content, publication duration, forks, caches and any included credentials or personal data.
  2. Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy.
  3. Check audit-log access methods, required event classes, Git event retention and previous stream coverage.
  4. Review required events, streaming destination, service ownership, delivery health and external retention policy.

Explanation

Correct Answer

B:

Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy. Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure. Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions.

Incorrect Answers

A:

Determine affected file content, publication duration, forks, caches and any included credentials or personal data. That check would not establish the decisive facts for this condition: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy.

C:

Check audit-log access methods, required event classes, Git event retention and previous stream coverage. That check would not establish the decisive facts for this condition: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy.

D:

Review required events, streaming destination, service ownership, delivery health and external retention policy. That check would not establish the decisive facts for this condition: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy.

Question 313

GitHub Enterprise administration scenario — Enable private vulnerability reporting responsibly. In an enterprise development environment: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. 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. Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions.
  4. Move the classified content into a private repository with explicit reviewed team access and retention safeguards.

Explanation

Correct Answer

C:

Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions. Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy. A researcher can notify maintainers privately and a test issue routes to designated responders.

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: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions.

B:

Require validated triage categories with documented revocation and exception decisions for exposed tokens. That change would leave the reported problem unresolved: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions.

D:

Move the classified content into a private repository with explicit reviewed team access and retention safeguards. That change would leave the reported problem unresolved: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions.

Question 314

GitHub Enterprise administration scenario — Enable private vulnerability reporting responsibly. In an enterprise development environment: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. 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 researcher can notify maintainers privately and a test issue routes to designated responders.
  2. Compare current token ownership, required API endpoints, repository selection and supported GitHub App permission model.
  3. The missing dependency is inventoried and a known vulnerable sample generates appropriate reviewable findings.
  4. Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy.
  5. Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets.

Explanation

Correct Answers

A:

A researcher can notify maintainers privately and a test issue routes to designated responders. Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy. Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure.

D:

Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy. A researcher can notify maintainers privately and a test issue routes to designated responders. Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions.

Incorrect Answers

B:

Compare current token ownership, required API endpoints, repository selection and supported GitHub App permission model. It would not provide the evidence needed for the paired diagnosis and follow-up: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy. A researcher can notify maintainers privately and a test issue routes to designated responders.

C:

The missing dependency is inventoried and a known vulnerable sample generates appropriate reviewable findings. It would not verify whether the proposed change works: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. A researcher can notify maintainers privately and a test issue routes to designated responders. Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions.

E:

Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets. It would not provide the evidence needed for the paired diagnosis and follow-up: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy. A researcher can notify maintainers privately and a test issue routes to designated responders.

Question 315

GitHub Enterprise administration scenario — Enable private vulnerability reporting responsibly. In an enterprise development environment: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. 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 a supported private vulnerability reporting pathway and publish clear responsible reporting instructions.
  2. A researcher can notify maintainers privately and a test issue routes to designated responders.
  3. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.
  4. Create or choose an authorized GitHub App with least-privilege permissions and documented credential rotation.
  5. Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure.
  6. Security logging coverage varies by audit method and event type, so detailed API request telemetry should be enabled deliberately where supported.

Explanation

Correct Answers

A:

Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions. Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure. A researcher can notify maintainers privately and a test issue routes to designated responders.

B:

A researcher can notify maintainers privately and a test issue routes to designated responders. Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions. Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure.

E:

Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure. Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions. A researcher can notify maintainers privately and a test issue routes to designated responders.

Incorrect Answers

C:

Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits. It would not independently demonstrate that the control works: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. A researcher can notify maintainers privately and a test issue routes to designated responders. Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions.

D:

Create or choose an authorized GitHub App with least-privilege permissions and documented credential rotation. It does not implement the governing rule for this approval: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions. A researcher can notify maintainers privately and a test issue routes to designated responders.

F:

Security logging coverage varies by audit method and event type, so detailed API request telemetry should be enabled deliberately where supported. It is not the rule that supports the proposed change and acceptance test: An open-source project's contributors publish sensitive proof-of-concept exploit details in a public issue because the repository has no private reporting instructions. Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure. Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions.

Question 316

GitHub Enterprise administration scenario — Stream GitHub enterprise audit events for compliance. In an enterprise development environment: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. 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. Enterprise security governance needs risk-tiered alert owners and observable remediation accountability.
  2. API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance.
  3. External enterprise audit log streaming can provide independently retained event copies beyond the product's limited interactive history.
  4. Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase.

Explanation

Correct Answer

C:

External enterprise audit log streaming can provide independently retained event copies beyond the product's limited interactive history. Review required events, streaming destination, service ownership, delivery health and external retention policy. Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries.

Incorrect Answers

A:

Enterprise security governance needs risk-tiered alert owners and observable remediation accountability. It does not govern the condition described: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. External enterprise audit log streaming can provide independently retained event copies beyond the product's limited interactive history.

B:

API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance. It does not govern the condition described: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. External enterprise audit log streaming can provide independently retained event copies beyond the product's limited interactive history.

D:

Code scanning requires a supported analysis configuration and evidence that its workflow covers the intended codebase. It does not govern the condition described: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. External enterprise audit log streaming can provide independently retained event copies beyond the product's limited interactive history.

Question 317

GitHub Enterprise administration scenario — Stream GitHub enterprise audit events for compliance. In an enterprise development environment: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. 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. Review required events, streaming destination, service ownership, delivery health and external retention policy.
  3. Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps.
  4. Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy.

Explanation

Correct Answer

B:

Review required events, streaming destination, service ownership, delivery health and external retention policy. External enterprise audit log streaming can provide independently retained event copies beyond the product's limited interactive history. Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries.

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: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. Review required events, streaming destination, service ownership, delivery health and external retention policy.

C:

Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps. That check would not establish the decisive facts for this condition: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. Review required events, streaming destination, service ownership, delivery health and external retention policy.

D:

Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy. That check would not establish the decisive facts for this condition: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. Review required events, streaming destination, service ownership, delivery health and external retention policy.

Question 318

GitHub Enterprise administration scenario — Stream GitHub enterprise audit events for compliance. In an enterprise development environment: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. 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. Produce a repeatable cross-organization effective-control report and assign remediation to owners of exceptions.
  2. Limit bypass authority and require an approved accountable emergency pathway with post-event review.
  3. Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries.
  4. Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.

Explanation

Correct Answer

C:

Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries. Review required events, streaming destination, service ownership, delivery health and external retention policy. A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy.

Incorrect Answers

A:

Produce a repeatable cross-organization effective-control report and assign remediation to owners of exceptions. That change would leave the reported problem unresolved: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries.

B:

Limit bypass authority and require an approved accountable emergency pathway with post-event review. That change would leave the reported problem unresolved: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries.

D:

Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement. That change would leave the reported problem unresolved: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries.

Question 319

GitHub Enterprise administration scenario — Stream GitHub enterprise audit events for compliance. In an enterprise development environment: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. 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. Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception.
  2. Review required events, streaming destination, service ownership, delivery health and external retention policy.
  3. The audit sample demonstrates required controls for every selected organization or records justified deviations.
  4. A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy.
  5. Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits.

Explanation

Correct Answers

B:

Review required events, streaming destination, service ownership, delivery health and external retention policy. A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy. Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries.

D:

A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy. Review required events, streaming destination, service ownership, delivery health and external retention policy. External enterprise audit log streaming can provide independently retained event copies beyond the product's limited interactive history.

Incorrect Answers

A:

Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception. It would not provide the evidence needed for the paired diagnosis and follow-up: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. Review required events, streaming destination, service ownership, delivery health and external retention policy. A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy.

C:

The audit sample demonstrates required controls for every selected organization or records justified deviations. It would not verify whether the proposed change works: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy. Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries.

E:

Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits. It would not provide the evidence needed for the paired diagnosis and follow-up: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. Review required events, streaming destination, service ownership, delivery health and external retention policy. A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy.

Question 320

GitHub Enterprise administration scenario — Stream GitHub enterprise audit events for compliance. In an enterprise development environment: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. 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. External enterprise audit log streaming can provide independently retained event copies beyond the product's limited interactive history.
  2. Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone.
  3. Revoke and replace the token promptly, contain abuse, and plan any history remediation with authorized owners.
  4. A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy.
  5. The tool performs its required repository operation without reading unrelated repositories or changing organization settings.
  6. Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries.

Explanation

Correct Answers

A:

External enterprise audit log streaming can provide independently retained event copies beyond the product's limited interactive history. Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries. A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy.

D:

A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy. Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries. External enterprise audit log streaming can provide independently retained event copies beyond the product's limited interactive history.

F:

Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries. External enterprise audit log streaming can provide independently retained event copies beyond the product's limited interactive history. A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy.

Incorrect Answers

B:

Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone. It is not the rule that supports the proposed change and acceptance test: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. External enterprise audit log streaming can provide independently retained event copies beyond the product's limited interactive history. Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries.

C:

Revoke and replace the token promptly, contain abuse, and plan any history remediation with authorized owners. It does not implement the governing rule for this approval: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries. A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy.

E:

The tool performs its required repository operation without reading unrelated repositories or changing organization settings. It would not independently demonstrate that the control works: An enterprise security operations team needs year-long investigation records, but its administrators only search GitHub's web audit interface occasionally. A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy. Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries.

GitHub Administration (GH-100) Practice Tests