Microsoft GH-100 Practice Test 55
Question 540
GitHub Enterprise administration scenario — Control duplicate deployments with concurrency. In an enterprise development environment: Two production-deployment workflows start from consecutive commits and both run simultaneously, threatening to overwrite each other's release state. 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.
- Sequential releases occur in the intended order and overlapping production mutation is prevented.
- Workflow concurrency controls can serialize mutually exclusive deployments when aligned with protected environments.
- Provide the supported workflow template together with enforceable Actions policies and measured adoption checks.
- Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics.
- Changes to runner group access are privileged governance events requiring attribution and periodic review.
- Hung jobs terminate within the approved window and normal tests still finish with complete results.
Explanation
Correct Answers
A:Sequential releases occur in the intended order and overlapping production mutation is prevented. Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics. Workflow concurrency controls can serialize mutually exclusive deployments when aligned with protected environments.
B:Workflow concurrency controls can serialize mutually exclusive deployments when aligned with protected environments. Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics. Sequential releases occur in the intended order and overlapping production mutation is prevented.
D:Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics. Workflow concurrency controls can serialize mutually exclusive deployments when aligned with protected environments. Sequential releases occur in the intended order and overlapping production mutation is prevented.
Incorrect Answers
C:Provide the supported workflow template together with enforceable Actions policies and measured adoption checks. It does not implement the governing rule for this approval: Two production-deployment workflows start from consecutive commits and both run simultaneously, threatening to overwrite each other's release state. Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics. Sequential releases occur in the intended order and overlapping production mutation is prevented.
E:Changes to runner group access are privileged governance events requiring attribution and periodic review. It is not the rule that supports the proposed change and acceptance test: Two production-deployment workflows start from consecutive commits and both run simultaneously, threatening to overwrite each other's release state. Workflow concurrency controls can serialize mutually exclusive deployments when aligned with protected environments. Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics.
F:Hung jobs terminate within the approved window and normal tests still finish with complete results. It would not independently demonstrate that the control works: Two production-deployment workflows start from consecutive commits and both run simultaneously, threatening to overwrite each other's release state. Sequential releases occur in the intended order and overlapping production mutation is prevented. Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics.
Question 541
GitHub Enterprise administration scenario — Set realistic workflow job timeouts. In an enterprise development environment: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. 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.
- Protected deployment environments help enforce authorized release gates and restrict production secret access.
- Job timeouts and cancellation handling protect finite runner capacity while preserving diagnosable failures.
- Untrusted contributor code should not execute on privileged persistent infrastructure without strong isolation.
- Runner label and group selection must match actual eligible connected runner inventory for a job to schedule.
Explanation
Correct Answer
B:Job timeouts and cancellation handling protect finite runner capacity while preserving diagnosable failures. Review historical execution durations, external call retry behavior and the workflow's current timeout settings. Set a justified job timeout and meaningful cleanup or evidence capture for the integration step.
Incorrect Answers
A:Protected deployment environments help enforce authorized release gates and restrict production secret access. It does not govern the condition described: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Job timeouts and cancellation handling protect finite runner capacity while preserving diagnosable failures.
C:Untrusted contributor code should not execute on privileged persistent infrastructure without strong isolation. It does not govern the condition described: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Job timeouts and cancellation handling protect finite runner capacity while preserving diagnosable failures.
D: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 CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Job timeouts and cancellation handling protect finite runner capacity while preserving diagnosable failures.
Question 542
GitHub Enterprise administration scenario — Set realistic workflow job timeouts. In an enterprise development environment: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference.
- Inspect runner service health, registered status, outbound connectivity, group membership and host logs.
- Inspect which repositories actually use the template and how enterprise Actions rules control alternatives.
- Review historical execution durations, external call retry behavior and the workflow's current timeout settings.
Explanation
Correct Answer
D:Review historical execution durations, external call retry behavior and the workflow's current timeout settings. Job timeouts and cancellation handling protect finite runner capacity while preserving diagnosable failures. Set a justified job timeout and meaningful cleanup or evidence capture for the integration step.
Incorrect Answers
A: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 CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Review historical execution durations, external call retry behavior and the workflow's current timeout settings.
B:Inspect runner service health, registered status, outbound connectivity, group membership and host logs. That check would not establish the decisive facts for this condition: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Review historical execution durations, external call retry behavior and the workflow's current timeout settings.
C:Inspect which repositories actually use the template and how enterprise Actions rules control alternatives. That check would not establish the decisive facts for this condition: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Review historical execution durations, external call retry behavior and the workflow's current timeout settings.
Question 543
GitHub Enterprise administration scenario — Set realistic workflow job timeouts. In an enterprise development environment: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. 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.
- Replace or approve the action through the supply-chain allow process and pin a reviewed revision.
- Set a justified job timeout and meaningful cleanup or evidence capture for the integration step.
- Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields.
- Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys.
Explanation
Correct Answer
B:Set a justified job timeout and meaningful cleanup or evidence capture for the integration step. Review historical execution durations, external call retry behavior and the workflow's current timeout settings. Hung jobs terminate within the approved window and normal tests still finish with complete results.
Incorrect Answers
A: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 CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Set a justified job timeout and meaningful cleanup or evidence capture for the integration step.
C:Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields. That change would leave the reported problem unresolved: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Set a justified job timeout and meaningful cleanup or evidence capture for the integration step.
D:Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys. That change would leave the reported problem unresolved: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Set a justified job timeout and meaningful cleanup or evidence capture for the integration step.
Question 544
GitHub Enterprise administration scenario — Set realistic workflow job timeouts. In an enterprise development environment: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. 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.
- Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference.
- Review historical execution durations, external call retry behavior and the workflow's current timeout settings.
- New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow.
- Hung jobs terminate within the approved window and normal tests still finish with complete results.
- Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies.
Explanation
Correct Answers
B:Review historical execution durations, external call retry behavior and the workflow's current timeout settings. Hung jobs terminate within the approved window and normal tests still finish with complete results. Set a justified job timeout and meaningful cleanup or evidence capture for the integration step.
D:Hung jobs terminate within the approved window and normal tests still finish with complete results. Review historical execution durations, external call retry behavior and the workflow's current timeout settings. Job timeouts and cancellation handling protect finite runner capacity while preserving diagnosable failures.
Incorrect Answers
A:Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference. It would not provide the evidence needed for the paired diagnosis and follow-up: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Review historical execution durations, external call retry behavior and the workflow's current timeout settings. Hung jobs terminate within the approved window and normal tests still finish with complete results.
C:New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow. It would not verify whether the proposed change works: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Hung jobs terminate within the approved window and normal tests still finish with complete results. Set a justified job timeout and meaningful cleanup or evidence capture for the integration step.
E:Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies. It would not provide the evidence needed for the paired diagnosis and follow-up: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Review historical execution durations, external call retry behavior and the workflow's current timeout settings. Hung jobs terminate within the approved window and normal tests still finish with complete results.
Question 545
GitHub Enterprise administration scenario — Set realistic workflow job timeouts. In an enterprise development environment: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. 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.
- Set a justified job timeout and meaningful cleanup or evidence capture for the integration step.
- Job timeouts and cancellation handling protect finite runner capacity while preserving diagnosable failures.
- Hung jobs terminate within the approved window and normal tests still finish with complete results.
- Actions can retrieve secrets from supported vault-backed integrations using controlled workflow identity and network configuration.
- Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
- Unit tests continue to pass without repository write permission and only the release job can publish intended changes.
Explanation
Correct Answers
A:Set a justified job timeout and meaningful cleanup or evidence capture for the integration step. Job timeouts and cancellation handling protect finite runner capacity while preserving diagnosable failures. Hung jobs terminate within the approved window and normal tests still finish with complete results.
B:Job timeouts and cancellation handling protect finite runner capacity while preserving diagnosable failures. Set a justified job timeout and meaningful cleanup or evidence capture for the integration step. Hung jobs terminate within the approved window and normal tests still finish with complete results.
C:Hung jobs terminate within the approved window and normal tests still finish with complete results. Set a justified job timeout and meaningful cleanup or evidence capture for the integration step. Job timeouts and cancellation handling protect finite runner capacity while preserving diagnosable failures.
Incorrect Answers
D:Actions can retrieve secrets from supported vault-backed integrations using controlled workflow identity and network configuration. It is not the rule that supports the proposed change and acceptance test: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Job timeouts and cancellation handling protect finite runner capacity while preserving diagnosable failures. Set a justified job timeout and meaningful cleanup or evidence capture for the integration step.
E:Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan. It does not implement the governing rule for this approval: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Set a justified job timeout and meaningful cleanup or evidence capture for the integration step. Hung jobs terminate within the approved window and normal tests still finish with complete results.
F:Unit tests continue to pass without repository write permission and only the release job can publish intended changes. It would not independently demonstrate that the control works: A CI job running an external integration occasionally hangs indefinitely and consumes runner capacity far beyond its legitimate test time. Hung jobs terminate within the approved window and normal tests still finish with complete results. Set a justified job timeout and meaningful cleanup or evidence capture for the integration step.
Question 546
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. 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.
- Protected deployment environments help enforce authorized release gates and restrict production secret access.
- Artifact retention should reflect debugging, compliance and cost needs, not assume all intermediate files require permanent storage.
- Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement.
- Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.
Explanation
Correct Answer
B:Artifact retention should reflect debugging, compliance and cost needs, not assume all intermediate files require permanent storage. Review artifact classes, existing retention settings, regulated records and actual download needs. Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed.
Incorrect Answers
A:Protected deployment environments help enforce authorized release gates and restrict production secret access. It does not govern the condition described: 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.
C:Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement. It does not govern the condition described: 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.
D:Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets. It does not govern the condition described: 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.
Question 547
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. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect trigger type, fork trust boundary, token permissions and secret availability for the affected job.
- Review artifact classes, existing retention settings, regulated records and actual download needs.
- Review runner size and OS, assigned IP or private networking requirements and which repositories may use it.
- Compare build resource needs, private endpoint access, supported runner networking and required trust posture.
Explanation
Correct Answer
B:Review artifact classes, existing retention settings, regulated records and actual download needs. 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.
Incorrect Answers
A:Inspect trigger type, fork trust boundary, token permissions and secret availability for the affected job. That check would not establish the decisive facts for this condition: An engineering organization stores huge intermediate build artifacts indefinitely in Actions even though only release artifacts require long retention. Review artifact classes, existing retention settings, regulated records and actual download needs.
C: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 engineering organization stores huge intermediate build artifacts indefinitely in Actions even though only release artifacts require long retention. Review artifact classes, existing retention settings, regulated records and actual download needs.
D: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: An engineering organization stores huge intermediate build artifacts indefinitely in Actions even though only release artifacts require long retention. Review artifact classes, existing retention settings, regulated records and actual download needs.
Question 548
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. 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.
- Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed.
- Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs.
- Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.
Explanation
Correct Answer
B:Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed. Review artifact classes, existing retention settings, regulated records and actual download needs. Disposable artifacts expire on policy while required release evidence remains retrievable.
Incorrect Answers
A:Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks. That change would leave the reported problem unresolved: 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.
C:Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs. That change would leave the reported problem unresolved: 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.
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: 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.
Question 549
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. 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.
- Review artifact classes, existing retention settings, regulated records and actual download needs.
- Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions.
- Disposable artifacts expire on policy while required release evidence remains retrievable.
- A fork pull request cannot influence the release job's executable dependencies through a shared cache.
- Inspect which repositories actually use the template and how enterprise Actions rules control alternatives.
Explanation
Correct Answers
A:Review artifact classes, existing retention settings, regulated records and actual download needs. 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.
C:Disposable artifacts expire on policy while required release evidence remains retrievable. Review artifact classes, existing retention settings, regulated records and actual download needs. Artifact retention should reflect debugging, compliance and cost needs, not assume all intermediate files require permanent storage.
Incorrect Answers
B:Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions. It would not provide the evidence needed for the paired diagnosis and follow-up: An engineering organization stores huge intermediate build artifacts indefinitely in Actions even though only release artifacts require long retention. Review artifact classes, existing retention settings, regulated records and actual download needs. Disposable artifacts expire on policy while required release evidence remains retrievable.
D:A fork pull request cannot influence the release job's executable dependencies through a shared cache. It would not verify whether the proposed change 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.
E:Inspect which repositories actually use the template and how enterprise Actions rules control alternatives. It would not provide the evidence needed for the paired diagnosis and follow-up: An engineering organization stores huge intermediate build artifacts indefinitely in Actions even though only release artifacts require long retention. Review artifact classes, existing retention settings, regulated records and actual download needs. Disposable artifacts expire on policy while required release evidence remains retrievable.
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.