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 44

Question 430

GitHub Enterprise administration scenario — Strengthen audit visibility into sensitive API activity. In an enterprise development environment: Investigators see a suspected privileged token being used but the organization's existing exported audit logs omit the API request details needed for attribution. 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. Security logging coverage varies by audit method and event type, so detailed API request telemetry should be enabled deliberately where supported.
  2. A simulated sensitive API action produces attributable retained evidence in the security monitoring destination.
  3. Enable supported API request audit streaming and correlated source IP evidence with privacy approvals and health checks.
  4. A pull request adding a known-risk dependency is flagged before merge while safe updates pass.
  5. Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure.
  6. Limit the installation to the required repository with only the necessary issues or pull request permissions.

Explanation

Correct Answers

A:

Security logging coverage varies by audit method and event type, so detailed API request telemetry should be enabled deliberately where supported. Enable supported API request audit streaming and correlated source IP evidence with privacy approvals and health checks. A simulated sensitive API action produces attributable retained evidence in the security monitoring destination.

B:

A simulated sensitive API action produces attributable retained evidence in the security monitoring destination. Enable supported API request audit streaming and correlated source IP evidence with privacy approvals and health checks. Security logging coverage varies by audit method and event type, so detailed API request telemetry should be enabled deliberately where supported.

C:

Enable supported API request audit streaming and correlated source IP evidence with privacy approvals and health checks. Security logging coverage varies by audit method and event type, so detailed API request telemetry should be enabled deliberately where supported. A simulated sensitive API action produces attributable retained evidence in the security monitoring destination.

Incorrect Answers

D:

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: Investigators see a suspected privileged token being used but the organization's existing exported audit logs omit the API request details needed for attribution. A simulated sensitive API action produces attributable retained evidence in the security monitoring destination. Enable supported API request audit streaming and correlated source IP evidence with privacy approvals and health checks.

E:

Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure. It is not the rule that supports the proposed change and acceptance test: Investigators see a suspected privileged token being used but the organization's existing exported audit logs omit the API request details needed for attribution. Security logging coverage varies by audit method and event type, so detailed API request telemetry should be enabled deliberately where supported. Enable supported API request audit streaming and correlated source IP evidence with privacy approvals and health checks.

F:

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: Investigators see a suspected privileged token being used but the organization's existing exported audit logs omit the API request details needed for attribution. Enable supported API request audit streaming and correlated source IP evidence with privacy approvals and health checks. A simulated sensitive API action produces attributable retained evidence in the security monitoring destination.

Question 431

GitHub Enterprise administration scenario — Restrict third-party Actions at enterprise scope. In an enterprise development environment: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. 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. Runner label and group selection must match actual eligible connected runner inventory for a job to schedule.
  2. Enterprise Actions policies should explicitly limit usable actions and reusable workflows according to approved trust boundaries.
  3. Workflow concurrency controls can serialize mutually exclusive deployments when aligned with protected environments.
  4. Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.

Explanation

Correct Answer

B:

Enterprise Actions policies should explicitly limit usable actions and reusable workflows according to approved trust boundaries. Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows. Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.

Incorrect Answers

A:

Runner label and group selection must match actual eligible connected runner inventory for a job to schedule. It does not govern the condition described: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. Enterprise Actions policies should explicitly limit usable actions and reusable workflows according to approved trust boundaries.

C:

Workflow concurrency controls can serialize mutually exclusive deployments when aligned with protected environments. It does not govern the condition described: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. Enterprise Actions policies should explicitly limit usable actions and reusable workflows according to approved trust boundaries.

D:

Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets. It does not govern the condition described: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. Enterprise Actions policies should explicitly limit usable actions and reusable workflows according to approved trust boundaries.

Question 432

GitHub Enterprise administration scenario — Restrict third-party Actions at enterprise scope. In an enterprise development environment: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Inspect all workflow triggers, secret references, required environments and existing repository security settings.
  2. Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference.
  3. Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows.
  4. Inspect the reusable repository's visibility, access settings and the caller's organization policy.

Explanation

Correct Answer

C:

Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows. Enterprise Actions policies should explicitly limit usable actions and reusable workflows according to approved trust boundaries. Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.

Incorrect Answers

A:

Inspect all workflow triggers, secret references, required environments and existing repository security settings. That check would not establish the decisive facts for this condition: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows.

B:

Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference. That check would not establish the decisive facts for this condition: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows.

D:

Inspect the reusable repository's visibility, access settings and the caller's organization policy. That check would not establish the decisive facts for this condition: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows.

Question 433

GitHub Enterprise administration scenario — Restrict third-party Actions at enterprise scope. In an enterprise development environment: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. 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. Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.
  2. Replace or approve the action through the supply-chain allow process and pin a reviewed revision.
  3. Create the supported larger runner configuration and restrict it to approved repositories or runner groups.
  4. Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics.

Explanation

Correct Answer

A:

Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines. Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows. An unapproved external action is blocked while designated trusted CI steps complete successfully.

Incorrect Answers

B:

Replace or approve the action through the supply-chain allow process and pin a reviewed revision. That change would leave the reported problem unresolved: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.

C:

Create the supported larger runner configuration and restrict it to approved repositories or runner groups. That change would leave the reported problem unresolved: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.

D:

Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics. That change would leave the reported problem unresolved: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.

Question 434

GitHub Enterprise administration scenario — Restrict third-party Actions at enterprise scope. In an enterprise development environment: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. 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. An authorized workflow dispatches to the restored runner group and execution results are visible.
  2. Review log excerpts, secret and variable handling, debug flags and downstream log exports.
  3. An unapproved external action is blocked while designated trusted CI steps complete successfully.
  4. Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows.
  5. Correlate audit log policy-change events, runner group access history and approved maintenance tickets.

Explanation

Correct Answers

C:

An unapproved external action is blocked while designated trusted CI steps complete successfully. Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows. Enterprise Actions policies should explicitly limit usable actions and reusable workflows according to approved trust boundaries.

D:

Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows. An unapproved external action is blocked while designated trusted CI steps complete successfully. Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.

Incorrect Answers

A:

An authorized workflow dispatches to the restored runner group and execution results are visible. It would not verify whether the proposed change works: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. An unapproved external action is blocked while designated trusted CI steps complete successfully. Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.

B:

Review log excerpts, secret and variable handling, debug flags and downstream log exports. It would not provide the evidence needed for the paired diagnosis and follow-up: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows. An unapproved external action is blocked while designated trusted CI steps complete successfully.

E:

Correlate audit log policy-change events, runner group access history and approved maintenance tickets. It would not provide the evidence needed for the paired diagnosis and follow-up: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows. An unapproved external action is blocked while designated trusted CI steps complete successfully.

Question 435

GitHub Enterprise administration scenario — Restrict third-party Actions at enterprise scope. In an enterprise development environment: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. 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. Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed.
  2. A malicious test title is processed as inert data and cannot trigger an unintended shell command.
  3. Enterprise Actions policies should explicitly limit usable actions and reusable workflows according to approved trust boundaries.
  4. An unapproved external action is blocked while designated trusted CI steps complete successfully.
  5. Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.
  6. Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets.

Explanation

Correct Answers

C:

Enterprise Actions policies should explicitly limit usable actions and reusable workflows according to approved trust boundaries. Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines. An unapproved external action is blocked while designated trusted CI steps complete successfully.

D:

An unapproved external action is blocked while designated trusted CI steps complete successfully. Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines. Enterprise Actions policies should explicitly limit usable actions and reusable workflows according to approved trust boundaries.

E:

Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines. Enterprise Actions policies should explicitly limit usable actions and reusable workflows according to approved trust boundaries. An unapproved external action is blocked while designated trusted CI steps complete successfully.

Incorrect Answers

A:

Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed. It does not implement the governing rule for this approval: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines. An unapproved external action is blocked while designated trusted CI steps complete successfully.

B:

A malicious test title is processed as inert data and cannot trigger an unintended shell command. It would not independently demonstrate that the control works: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. An unapproved external action is blocked while designated trusted CI steps complete successfully. Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.

F:

Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets. It is not the rule that supports the proposed change and acceptance test: A security team discovers that every repository can execute arbitrary unreviewed Marketplace Actions despite a centrally mandated software supply-chain allow policy. Enterprise Actions policies should explicitly limit usable actions and reusable workflows according to approved trust boundaries. Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.

Question 436

GitHub Enterprise administration scenario — Pin third-party action dependencies to immutable versions. In an enterprise development environment: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. 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. Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership.
  2. Immutable pinned action revisions reduce exposure to unexpected changes in remote dependency code between builds.
  3. Runner group policies should constrain repository and organization access to trusted workload boundaries.
  4. Third-party actions execute code in workflow security context and require trust, permission and change reviews.

Explanation

Correct Answer

B:

Immutable pinned action revisions reduce exposure to unexpected changes in remote dependency code between builds. Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies. Pin critical third-party actions to vetted immutable commits and use an accountable update review process.

Incorrect Answers

A:

Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership. It does not govern the condition described: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. Immutable pinned action revisions reduce exposure to unexpected changes in remote dependency code between builds.

C:

Runner group policies should constrain repository and organization access to trusted workload boundaries. It does not govern the condition described: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. Immutable pinned action revisions reduce exposure to unexpected changes in remote dependency code between builds.

D:

Third-party actions execute code in workflow security context and require trust, permission and change reviews. It does not govern the condition described: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. Immutable pinned action revisions reduce exposure to unexpected changes in remote dependency code between builds.

Question 437

GitHub Enterprise administration scenario — Pin third-party action dependencies to immutable versions. In an enterprise development environment: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Examine the caller's secret inheritance, callee permissions, environment protection and required credentials.
  2. Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows.
  3. Review historical execution durations, external call retry behavior and the workflow's current timeout settings.
  4. Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies.

Explanation

Correct Answer

D:

Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies. Immutable pinned action revisions reduce exposure to unexpected changes in remote dependency code between builds. Pin critical third-party actions to vetted immutable commits and use an accountable update review process.

Incorrect Answers

A:

Examine the caller's secret inheritance, callee permissions, environment protection and required credentials. That check would not establish the decisive facts for this condition: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies.

B:

Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows. That check would not establish the decisive facts for this condition: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies.

C:

Review historical execution durations, external call retry behavior and the workflow's current timeout settings. That check would not establish the decisive facts for this condition: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies.

Question 438

GitHub Enterprise administration scenario — Pin third-party action dependencies to immutable versions. In an enterprise development environment: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. 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. Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields.
  2. Pin critical third-party actions to vetted immutable commits and use an accountable update review process.
  3. Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
  4. Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs.

Explanation

Correct Answer

B:

Pin critical third-party actions to vetted immutable commits and use an accountable update review process. Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies. The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it.

Incorrect Answers

A:

Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields. That change would leave the reported problem unresolved: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. Pin critical third-party actions to vetted immutable commits and use an accountable update review process.

C:

Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan. That change would leave the reported problem unresolved: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. Pin critical third-party actions to vetted immutable commits and use an accountable update review process.

D:

Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs. That change would leave the reported problem unresolved: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. Pin critical third-party actions to vetted immutable commits and use an accountable update review process.

Question 439

GitHub Enterprise administration scenario — Pin third-party action dependencies to immutable versions. In an enterprise development environment: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. 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. Correlate audit log policy-change events, runner group access history and approved maintenance tickets.
  2. The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it.
  3. Review historical execution durations, external call retry behavior and the workflow's current timeout settings.
  4. Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies.
  5. A fork pull request receives only safe read access and cannot access deployment credentials in a controlled test.

Explanation

Correct Answers

B:

The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it. Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies. Immutable pinned action revisions reduce exposure to unexpected changes in remote dependency code between builds.

D:

Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies. The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it. Pin critical third-party actions to vetted immutable commits and use an accountable update review process.

Incorrect Answers

A:

Correlate audit log policy-change events, runner group access history and approved maintenance tickets. It would not provide the evidence needed for the paired diagnosis and follow-up: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies. The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it.

C:

Review historical execution durations, external call retry behavior and the workflow's current timeout settings. It would not provide the evidence needed for the paired diagnosis and follow-up: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies. The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it.

E:

A fork pull request receives only safe read access and cannot access deployment credentials in a controlled test. It would not verify whether the proposed change works: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it. Pin critical third-party actions to vetted immutable commits and use an accountable update review process.

Question 440

GitHub Enterprise administration scenario — Pin third-party action dependencies to immutable versions. In an enterprise development environment: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. 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. Use reusable workflows for centralized multi-job policy and composite actions only for appropriate step-level reuse.
  2. An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access.
  3. Immutable pinned action revisions reduce exposure to unexpected changes in remote dependency code between builds.
  4. Pin critical third-party actions to vetted immutable commits and use an accountable update review process.
  5. Artifact retention should reflect debugging, compliance and cost needs, not assume all intermediate files require permanent storage.
  6. The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it.

Explanation

Correct Answers

C:

Immutable pinned action revisions reduce exposure to unexpected changes in remote dependency code between builds. Pin critical third-party actions to vetted immutable commits and use an accountable update review process. The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it.

D:

Pin critical third-party actions to vetted immutable commits and use an accountable update review process. Immutable pinned action revisions reduce exposure to unexpected changes in remote dependency code between builds. The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it.

F:

The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it. Pin critical third-party actions to vetted immutable commits and use an accountable update review process. Immutable pinned action revisions reduce exposure to unexpected changes in remote dependency code between builds.

Incorrect Answers

A:

Use reusable workflows for centralized multi-job policy and composite actions only for appropriate step-level reuse. It does not implement the governing rule for this approval: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. Pin critical third-party actions to vetted immutable commits and use an accountable update review process. The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it.

B:

An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access. It would not independently demonstrate that the control works: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it. Pin critical third-party actions to vetted immutable commits and use an accountable update review process.

E:

Artifact retention should reflect debugging, compliance and cost needs, not assume all intermediate files require permanent storage. It is not the rule that supports the proposed change and acceptance test: A production pipeline references a third-party action by a moving major-version tag and a maintainer worries that upstream changes could alter release behavior. Immutable pinned action revisions reduce exposure to unexpected changes in remote dependency code between builds. Pin critical third-party actions to vetted immutable commits and use an accountable update review process.

GitHub Administration (GH-100) Practice Tests