Microsoft GH-100 Practice Test 56
Question 550
GitHub Enterprise administration scenario — Manage workflow artifact retention deliberately. In an enterprise development environment: An engineering organization stores huge intermediate build artifacts indefinitely in Actions even though only release artifacts require long retention. 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.
- Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose.
- Artifact retention should reflect debugging, compliance and cost needs, not assume all intermediate files require permanent storage.
- Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed.
- Disposable artifacts expire on policy while required release evidence remains retrievable.
- Monthly minutes fall to planned limits while critical build and security checks continue to run.
- Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics.
Explanation
Correct Answers
B:Artifact retention should reflect debugging, compliance and cost needs, not assume all intermediate files require permanent storage. Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed. Disposable artifacts expire on policy while required release evidence remains retrievable.
C:Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed. Artifact retention should reflect debugging, compliance and cost needs, not assume all intermediate files require permanent storage. Disposable artifacts expire on policy while required release evidence remains retrievable.
D:Disposable artifacts expire on policy while required release evidence remains retrievable. Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed. Artifact retention should reflect debugging, compliance and cost needs, not assume all intermediate files require permanent storage.
Incorrect Answers
A:Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose. It is not the rule that supports the proposed change and acceptance test: An engineering organization stores huge intermediate build artifacts indefinitely in Actions even though only release artifacts require long retention. Artifact retention should reflect debugging, compliance and cost needs, not assume all intermediate files require permanent storage. Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed.
E:Monthly minutes fall to planned limits while critical build and security checks continue to run. It would not independently demonstrate that the control works: An engineering organization stores huge intermediate build artifacts indefinitely in Actions even though only release artifacts require long retention. Disposable artifacts expire on policy while required release evidence remains retrievable. Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed.
F:Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics. It does not implement the governing rule for this approval: An engineering organization stores huge intermediate build artifacts indefinitely in Actions even though only release artifacts require long retention. Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed. Disposable artifacts expire on policy while required release evidence remains retrievable.
Question 551
GitHub Enterprise administration scenario — Avoid cache poisoning between untrusted and privileged jobs. In an enterprise development environment: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. 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.
- Changes to runner group access are privileged governance events requiring attribution and periodic review.
- Runner label and group selection must match actual eligible connected runner inventory for a job to schedule.
- Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions.
- Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases.
Explanation
Correct Answer
D:Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases. Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing. Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys.
Incorrect Answers
A:Changes to runner group access are privileged governance events requiring attribution and periodic review. It does not govern the condition described: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases.
B: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 high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases.
C:Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions. It does not govern the condition described: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases.
Question 552
GitHub Enterprise administration scenario — Avoid cache poisoning between untrusted and privileged jobs. In an enterprise development environment: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies.
- Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions.
- Check the secret's selected-repository visibility settings and every workflow currently referencing it.
- Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing.
Explanation
Correct Answer
D:Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing. Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases. Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys.
Incorrect Answers
A:Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies. That check would not establish the decisive facts for this condition: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing.
B:Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions. That check would not establish the decisive facts for this condition: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing.
C:Check the secret's selected-repository visibility settings and every workflow currently referencing it. That check would not establish the decisive facts for this condition: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing.
Question 553
GitHub Enterprise administration scenario — Avoid cache poisoning between untrusted and privileged jobs. In an enterprise development environment: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. 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.
- Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.
- Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys.
- Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields.
- Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
Explanation
Correct Answer
B:Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys. Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing. A fork pull request cannot influence the release job's executable dependencies through a shared cache.
Incorrect Answers
A:Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes. That change would leave the reported problem unresolved: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys.
C:Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields. That change would leave the reported problem unresolved: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys.
D:Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities. That change would leave the reported problem unresolved: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys.
Question 554
GitHub Enterprise administration scenario — Avoid cache poisoning between untrusted and privileged jobs. In an enterprise development environment: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. 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.
- The representative build reaches its allowed dependencies and remains isolated from untrusted repositories.
- Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage.
- A fork pull request cannot influence the release job's executable dependencies through a shared cache.
- Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing.
- Inspect the reusable repository's visibility, access settings and the caller's organization policy.
Explanation
Correct Answers
C:A fork pull request cannot influence the release job's executable dependencies through a shared cache. Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing. Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases.
D:Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing. A fork pull request cannot influence the release job's executable dependencies through a shared cache. Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys.
Incorrect Answers
A:The representative build reaches its allowed dependencies and remains isolated from untrusted repositories. It would not verify whether the proposed change works: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. A fork pull request cannot influence the release job's executable dependencies through a shared cache. Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys.
B: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: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing. A fork pull request cannot influence the release job's executable dependencies through a shared cache.
E:Inspect the reusable repository's visibility, access settings and the caller's organization policy. It would not provide the evidence needed for the paired diagnosis and follow-up: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing. A fork pull request cannot influence the release job's executable dependencies through a shared cache.
Question 555
GitHub Enterprise administration scenario — Avoid cache poisoning between untrusted and privileged jobs. In an enterprise development environment: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. 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.
- A newly scheduled job starts from a clean runner state without previous job artifacts or secrets.
- Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
- A fork pull request cannot influence the release job's executable dependencies through a shared cache.
- Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases.
- Secret availability must match job trust and deployment need rather than defaulting to repository-wide access.
- Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys.
Explanation
Correct Answers
C:A fork pull request cannot influence the release job's executable dependencies through a shared cache. Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys. Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases.
D:Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases. Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys. A fork pull request cannot influence the release job's executable dependencies through a shared cache.
F:Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys. Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases. A fork pull request cannot influence the release job's executable dependencies through a shared cache.
Incorrect Answers
A:A newly scheduled job starts from a clean runner state without previous job artifacts or secrets. It would not independently demonstrate that the control works: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. A fork pull request cannot influence the release job's executable dependencies through a shared cache. Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys.
B:Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories. It does not implement the governing rule for this approval: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys. A fork pull request cannot influence the release job's executable dependencies through a shared cache.
E:Secret availability must match job trust and deployment need rather than defaulting to repository-wide access. It is not the rule that supports the proposed change and acceptance test: A high-privilege release workflow restores a shared cache that is also writable by less-trusted pull request jobs. Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases. Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys.
Question 556
GitHub Enterprise administration scenario — Monitor GitHub Actions spending limits. In an enterprise development environment: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. 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.
- Workflow execution plans should balance required test coverage and resource cost within approved budgets.
- Workflow and job-level token permissions should be restricted to minimum required operations.
- Runner group policies should constrain repository and organization access to trusted workload boundaries.
- Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases.
Explanation
Correct Answer
A:Workflow execution plans should balance required test coverage and resource cost within approved budgets. Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets. Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks.
Incorrect Answers
B:Workflow and job-level token permissions should be restricted to minimum required operations. It does not govern the condition described: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Workflow execution plans should balance required test coverage and resource cost within approved budgets.
C:Runner group policies should constrain repository and organization access to trusted workload boundaries. It does not govern the condition described: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Workflow execution plans should balance required test coverage and resource cost within approved budgets.
D:Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases. It does not govern the condition described: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Workflow execution plans should balance required test coverage and resource cost within approved budgets.
Question 557
GitHub Enterprise administration scenario — Monitor GitHub Actions spending limits. In an enterprise development environment: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Review environment branch restrictions, required reviewers, workflow triggers and production secret placement.
- Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets.
- Compare build resource needs, private endpoint access, supported runner networking and required trust posture.
- Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference.
Explanation
Correct Answer
B:Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets. Workflow execution plans should balance required test coverage and resource cost within approved budgets. Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks.
Incorrect Answers
A:Review environment branch restrictions, required reviewers, workflow triggers and production secret placement. That check would not establish the decisive facts for this condition: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets.
C:Compare build resource needs, private endpoint access, supported runner networking and required trust posture. That check would not establish the decisive facts for this condition: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets.
D: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 new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets.
Question 558
GitHub Enterprise administration scenario — Monitor GitHub Actions spending limits. In an enterprise development environment: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. 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.
- Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks.
- Provide the supported workflow template together with enforceable Actions policies and measured adoption checks.
- Restore the supported runner service or replace the failed agent through an approved capacity and image process.
- Configure supported environment protection rules and route release jobs through the protected environment.
Explanation
Correct Answer
A:Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks. Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets. Monthly minutes fall to planned limits while critical build and security checks continue to run.
Incorrect Answers
B:Provide the supported workflow template together with enforceable Actions policies and measured adoption checks. That change would leave the reported problem unresolved: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks.
C:Restore the supported runner service or replace the failed agent through an approved capacity and image process. That change would leave the reported problem unresolved: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks.
D:Configure supported environment protection rules and route release jobs through the protected environment. That change would leave the reported problem unresolved: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks.
Question 559
GitHub Enterprise administration scenario — Monitor GitHub Actions spending limits. In an enterprise development environment: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. 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.
- Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets.
- Inspect queued job history, runner resource saturation, labels, groups and concurrent build demand.
- Monthly minutes fall to planned limits while critical build and security checks continue to run.
- Correlate audit log policy-change events, runner group access history and approved maintenance tickets.
- The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it.
Explanation
Correct Answers
A:Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets. Monthly minutes fall to planned limits while critical build and security checks continue to run. Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks.
C:Monthly minutes fall to planned limits while critical build and security checks continue to run. Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets. Workflow execution plans should balance required test coverage and resource cost within approved budgets.
Incorrect Answers
B: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 new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets. Monthly minutes fall to planned limits while critical build and security checks continue to run.
D: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 new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets. Monthly minutes fall to planned limits while critical build and security checks continue to run.
E:The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it. It would not verify whether the proposed change works: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Monthly minutes fall to planned limits while critical build and security checks continue to run. Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks.
Question 560
GitHub Enterprise administration scenario — Monitor GitHub Actions spending limits. In an enterprise development environment: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. 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.
- The release pipeline runs with a vetted action while attempted substitution from an untrusted publisher is rejected.
- Workflow execution plans should balance required test coverage and resource cost within approved budgets.
- Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks.
- Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests.
- Monthly minutes fall to planned limits while critical build and security checks continue to run.
- An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution.
Explanation
Correct Answers
B:Workflow execution plans should balance required test coverage and resource cost within approved budgets. Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks. Monthly minutes fall to planned limits while critical build and security checks continue to run.
C:Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks. Workflow execution plans should balance required test coverage and resource cost within approved budgets. Monthly minutes fall to planned limits while critical build and security checks continue to run.
E:Monthly minutes fall to planned limits while critical build and security checks continue to run. Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks. Workflow execution plans should balance required test coverage and resource cost within approved budgets.
Incorrect Answers
A:The release pipeline runs with a vetted action while attempted substitution from an untrusted publisher is rejected. It would not independently demonstrate that the control works: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Monthly minutes fall to planned limits while critical build and security checks continue to run. Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks.
D:Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests. It does not implement the governing rule for this approval: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks. Monthly minutes fall to planned limits while critical build and security checks continue to run.
F:An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution. It is not the rule that supports the proposed change and acceptance test: A new test matrix multiplies hosted runner minutes across dozens of repositories and finance sees a surprise increase in metered CI charges. Workflow execution plans should balance required test coverage and resource cost within approved budgets. Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks.