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 45

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.

Question 441

GitHub Enterprise administration scenario — Use reusable workflows for central policy. In an enterprise development environment: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across 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. Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions.
  2. Runner capacity and queue telemetry should determine scaling actions instead of broad permission exceptions.
  3. Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface.
  4. Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks.

Explanation

Correct Answer

A:

Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions. Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions. Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests.

Incorrect Answers

B:

Runner capacity and queue telemetry should determine scaling actions instead of broad permission exceptions. It does not govern the condition described: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions.

C:

Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface. It does not govern the condition described: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions.

D:

Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks. It does not govern the condition described: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions.

Question 442

GitHub Enterprise administration scenario — Use reusable workflows for central policy. In an enterprise development environment: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions.
  2. Review runner persistence, network reachability, PR trust conditions and available credentials or caches.
  3. Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing.
  4. Review historical execution durations, external call retry behavior and the workflow's current timeout settings.

Explanation

Correct Answer

A:

Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions. Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions. Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests.

Incorrect Answers

B:

Review runner persistence, network reachability, PR trust conditions and available credentials or caches. That check would not establish the decisive facts for this condition: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions.

C:

Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing. That check would not establish the decisive facts for this condition: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions.

D:

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 hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions.

Question 443

GitHub Enterprise administration scenario — Use reusable workflows for central policy. In an enterprise development environment: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across 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. Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests.
  2. Set read-only token defaults or explicit least-privilege job permissions and grant writes only to reviewed publishing jobs.
  3. Pass only the needed named secret or use protected environment identity with an approved shared workflow contract.
  4. Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.

Explanation

Correct Answer

A:

Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests. Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions. Sample callers invoke the same reviewed workflow revision and conform to the required deployment controls.

Incorrect Answers

B:

Set read-only token defaults or explicit least-privilege job permissions and grant writes only to reviewed publishing jobs. That change would leave the reported problem unresolved: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests.

C:

Pass only the needed named secret or use protected environment identity with an approved shared workflow contract. That change would leave the reported problem unresolved: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests.

D:

Move the credential to a protected environment or approved vault-backed access route with controlled job permissions. That change would leave the reported problem unresolved: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests.

Question 444

GitHub Enterprise administration scenario — Use reusable workflows for central policy. In an enterprise development environment: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across 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. Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions.
  2. Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements.
  3. A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released.
  4. Inspect queued job history, runner resource saturation, labels, groups and concurrent build demand.
  5. Sample callers invoke the same reviewed workflow revision and conform to the required deployment controls.

Explanation

Correct Answers

A:

Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions. Sample callers invoke the same reviewed workflow revision and conform to the required deployment controls. Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests.

E:

Sample callers invoke the same reviewed workflow revision and conform to the required deployment controls. Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions. Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions.

Incorrect Answers

B:

Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements. It would not provide the evidence needed for the paired diagnosis and follow-up: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions. Sample callers invoke the same reviewed workflow revision and conform to the required deployment controls.

C:

A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released. It would not verify whether the proposed change works: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Sample callers invoke the same reviewed workflow revision and conform to the required deployment controls. Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests.

D:

Inspect queued job history, runner resource saturation, labels, groups and concurrent build demand. It would not provide the evidence needed for the paired diagnosis and follow-up: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions. Sample callers invoke the same reviewed workflow revision and conform to the required deployment controls.

Question 445

GitHub Enterprise administration scenario — Use reusable workflows for central policy. In an enterprise development environment: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across 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. The standardized release workflow preserves separate review-gated jobs and callers use the intended shared implementation.
  2. Sample callers invoke the same reviewed workflow revision and conform to the required deployment controls.
  3. Correct the supported selector or provision an appropriately labeled authorized runner with approval.
  4. Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions.
  5. Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests.
  6. OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers.

Explanation

Correct Answers

B:

Sample callers invoke the same reviewed workflow revision and conform to the required deployment controls. Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests. Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions.

D:

Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions. Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests. Sample callers invoke the same reviewed workflow revision and conform to the required deployment controls.

E:

Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests. Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions. Sample callers invoke the same reviewed workflow revision and conform to the required deployment controls.

Incorrect Answers

A:

The standardized release workflow preserves separate review-gated jobs and callers use the intended shared implementation. It would not independently demonstrate that the control works: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Sample callers invoke the same reviewed workflow revision and conform to the required deployment controls. Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests.

C:

Correct the supported selector or provision an appropriately labeled authorized runner with approval. It does not implement the governing rule for this approval: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests. Sample callers invoke the same reviewed workflow revision and conform to the required deployment controls.

F:

OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers. It is not the rule that supports the proposed change and acceptance test: A hundred repositories copy the same deployment YAML but security teams cannot patch authentication steps consistently across copies. Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions. Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests.

Question 446

GitHub Enterprise administration scenario — Offer workflow templates without assuming enforced reuse. In an enterprise development environment: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. 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. Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement.
  2. Runner capacity and queue telemetry should determine scaling actions instead of broad permission exceptions.
  3. Runner label and group selection must match actual eligible connected runner inventory for a job to schedule.
  4. Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks.

Explanation

Correct Answer

A:

Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement. Inspect which repositories actually use the template and how enterprise Actions rules control alternatives. Provide the supported workflow template together with enforceable Actions policies and measured adoption checks.

Incorrect Answers

B:

Runner capacity and queue telemetry should determine scaling actions instead of broad permission exceptions. It does not govern the condition described: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement.

C:

Runner label and group selection must match actual eligible connected runner inventory for a job to schedule. It does not govern the condition described: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement.

D:

Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks. It does not govern the condition described: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement.

Question 447

GitHub Enterprise administration scenario — Offer workflow templates without assuming enforced reuse. In an enterprise development environment: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Inspect which repositories actually use the template and how enterprise Actions rules control alternatives.
  2. Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference.
  3. Inspect all workflow triggers, secret references, required environments and existing repository security settings.
  4. Review runner size and OS, assigned IP or private networking requirements and which repositories may use it.

Explanation

Correct Answer

A:

Inspect which repositories actually use the template and how enterprise Actions rules control alternatives. Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement. Provide the supported workflow template together with enforceable Actions policies and measured adoption checks.

Incorrect Answers

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: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. Inspect which repositories actually use the template and how enterprise Actions rules control alternatives.

C:

Inspect all workflow triggers, secret references, required environments and existing repository security settings. That check would not establish the decisive facts for this condition: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. Inspect which repositories actually use the template and how enterprise Actions rules control alternatives.

D:

Review runner size and OS, assigned IP or private networking requirements and which repositories may use it. That check would not establish the decisive facts for this condition: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. Inspect which repositories actually use the template and how enterprise Actions rules control alternatives.

Question 448

GitHub Enterprise administration scenario — Offer workflow templates without assuming enforced reuse. In an enterprise development environment: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. 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 least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs.
  2. Provide the supported workflow template together with enforceable Actions policies and measured adoption checks.
  3. Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key.
  4. Pass only the needed named secret or use protected environment identity with an approved shared workflow contract.

Explanation

Correct Answer

B:

Provide the supported workflow template together with enforceable Actions policies and measured adoption checks. Inspect which repositories actually use the template and how enterprise Actions rules control alternatives. New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow.

Incorrect Answers

A:

Configure a least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs. That change would leave the reported problem unresolved: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. Provide the supported workflow template together with enforceable Actions policies and measured adoption checks.

C:

Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key. That change would leave the reported problem unresolved: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. Provide the supported workflow template together with enforceable Actions policies and measured adoption checks.

D:

Pass only the needed named secret or use protected environment identity with an approved shared workflow contract. That change would leave the reported problem unresolved: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. Provide the supported workflow template together with enforceable Actions policies and measured adoption checks.

Question 449

GitHub Enterprise administration scenario — Offer workflow templates without assuming enforced reuse. In an enterprise development environment: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. 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 which repositories actually use the template and how enterprise Actions rules control alternatives.
  2. Review runner persistence, network reachability, PR trust conditions and available credentials or caches.
  3. Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage.
  4. New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow.
  5. A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released.

Explanation

Correct Answers

A:

Inspect which repositories actually use the template and how enterprise Actions rules control alternatives. New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow. Provide the supported workflow template together with enforceable Actions policies and measured adoption checks.

D:

New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow. Inspect which repositories actually use the template and how enterprise Actions rules control alternatives. Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement.

Incorrect Answers

B:

Review runner persistence, network reachability, PR trust conditions and available credentials or caches. It would not provide the evidence needed for the paired diagnosis and follow-up: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. Inspect which repositories actually use the template and how enterprise Actions rules control alternatives. New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow.

C:

Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage. It would not provide the evidence needed for the paired diagnosis and follow-up: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. Inspect which repositories actually use the template and how enterprise Actions rules control alternatives. New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow.

E:

A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released. It would not verify whether the proposed change works: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow. Provide the supported workflow template together with enforceable Actions policies and measured adoption checks.

Question 450

GitHub Enterprise administration scenario — Offer workflow templates without assuming enforced reuse. In an enterprise development environment: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. 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. Provide the supported workflow template together with enforceable Actions policies and measured adoption checks.
  2. Larger runners have configurable resource and networking capabilities that require matching security and access policies.
  3. Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement.
  4. New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow.
  5. Pass only the needed named secret or use protected environment identity with an approved shared workflow contract.
  6. An authorized caller executes the reviewed shared workflow while unrelated repositories remain excluded.

Explanation

Correct Answers

A:

Provide the supported workflow template together with enforceable Actions policies and measured adoption checks. Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement. New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow.

C:

Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement. Provide the supported workflow template together with enforceable Actions policies and measured adoption checks. New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow.

D:

New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow. Provide the supported workflow template together with enforceable Actions policies and measured adoption checks. Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement.

Incorrect Answers

B:

Larger runners have configurable resource and networking capabilities that require matching security and access policies. It is not the rule that supports the proposed change and acceptance test: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement. Provide the supported workflow template together with enforceable Actions policies and measured adoption checks.

E:

Pass only the needed named secret or use protected environment identity with an approved shared workflow contract. It does not implement the governing rule for this approval: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. Provide the supported workflow template together with enforceable Actions policies and measured adoption checks. New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow.

F:

An authorized caller executes the reviewed shared workflow while unrelated repositories remain excluded. It would not independently demonstrate that the control works: An administrator publishes a template workflow and tells auditors every repository must be using it, although teams can create other workflows. New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow. Provide the supported workflow template together with enforceable Actions policies and measured adoption checks.

GitHub Administration (GH-100) Practice Tests