Microsoft GH-100 Practice Test 54
Question 530
GitHub Enterprise administration scenario — Diagnose unschedulable runner labels. In an enterprise development environment: A workflow job waits indefinitely for a self-hosted runner labeled windows-gpu although every available runner lacks that exact label. 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.
- Correct the supported selector or provision an appropriately labeled authorized runner with approval.
- Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.
- The queued job is assigned to a qualified runner and finishes its representative build.
- Runner label and group selection must match actual eligible connected runner inventory for a job to schedule.
- Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership.
- Unit tests continue to pass without repository write permission and only the release job can publish intended changes.
Explanation
Correct Answers
A:Correct the supported selector or provision an appropriately labeled authorized runner with approval. Runner label and group selection must match actual eligible connected runner inventory for a job to schedule. The queued job is assigned to a qualified runner and finishes its representative build.
C:The queued job is assigned to a qualified runner and finishes its representative build. Correct the supported selector or provision an appropriately labeled authorized runner with approval. Runner label and group selection must match actual eligible connected runner inventory for a job to schedule.
D:Runner label and group selection must match actual eligible connected runner inventory for a job to schedule. Correct the supported selector or provision an appropriately labeled authorized runner with approval. The queued job is assigned to a qualified runner and finishes its representative build.
Incorrect Answers
B:Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines. It does not implement the governing rule for this approval: A workflow job waits indefinitely for a self-hosted runner labeled windows-gpu although every available runner lacks that exact label. Correct the supported selector or provision an appropriately labeled authorized runner with approval. The queued job is assigned to a qualified runner and finishes its representative build.
E:Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership. It is not the rule that supports the proposed change and acceptance test: A workflow job waits indefinitely for a self-hosted runner labeled windows-gpu although every available runner lacks that exact label. Runner label and group selection must match actual eligible connected runner inventory for a job to schedule. Correct the supported selector or provision an appropriately labeled authorized runner with approval.
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 workflow job waits indefinitely for a self-hosted runner labeled windows-gpu although every available runner lacks that exact label. The queued job is assigned to a qualified runner and finishes its representative build. Correct the supported selector or provision an appropriately labeled authorized runner with approval.
Question 531
GitHub Enterprise administration scenario — Resolve offline runner provisioning failures. In an enterprise development environment: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. 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.
- Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name.
- Runner group policies should constrain repository and organization access to trusted workload boundaries.
- Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose.
- An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution.
Explanation
Correct Answer
D:An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution. Inspect runner service health, registered status, outbound connectivity, group membership and host logs. Restore the supported runner service or replace the failed agent through an approved capacity and image process.
Incorrect Answers
A:Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name. It does not govern the condition described: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution.
B:Runner group policies should constrain repository and organization access to trusted workload boundaries. It does not govern the condition described: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution.
C:Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose. It does not govern the condition described: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution.
Question 532
GitHub Enterprise administration scenario — Resolve offline runner provisioning failures. In an enterprise development environment: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets.
- Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements.
- Inspect runner service health, registered status, outbound connectivity, group membership and host logs.
- Inspect the reusable repository's visibility, access settings and the caller's organization policy.
Explanation
Correct Answer
C:Inspect runner service health, registered status, outbound connectivity, group membership and host logs. An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution. Restore the supported runner service or replace the failed agent through an approved capacity and image process.
Incorrect Answers
A:Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets. That check would not establish the decisive facts for this condition: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. Inspect runner service health, registered status, outbound connectivity, group membership and host logs.
B:Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements. That check would not establish the decisive facts for this condition: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. Inspect runner service health, registered status, outbound connectivity, group membership and host logs.
D:Inspect the reusable repository's visibility, access settings and the caller's organization policy. That check would not establish the decisive facts for this condition: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. Inspect runner service health, registered status, outbound connectivity, group membership and host logs.
Question 533
GitHub Enterprise administration scenario — Resolve offline runner provisioning failures. In an enterprise development environment: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. 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.
- Restore the supported runner service or replace the failed agent through an approved capacity and image process.
- Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
- Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields.
Explanation
Correct Answer
B:Restore the supported runner service or replace the failed agent through an approved capacity and image process. Inspect runner service health, registered status, outbound connectivity, group membership and host logs. An authorized workflow dispatches to the restored runner group and execution results are visible.
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 pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. Restore the supported runner service or replace the failed agent through an approved capacity and image process.
C: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 pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. Restore the supported runner service or replace the failed agent through an approved capacity and image process.
D:Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields. That change would leave the reported problem unresolved: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. Restore the supported runner service or replace the failed agent through an approved capacity and image process.
Question 534
GitHub Enterprise administration scenario — Resolve offline runner provisioning failures. In an enterprise development environment: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. 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.
- Check the secret's selected-repository visibility settings and every workflow currently referencing it.
- The release pipeline runs with a vetted action while attempted substitution from an untrusted publisher is rejected.
- Inspect trigger type, fork trust boundary, token permissions and secret availability for the affected job.
- An authorized workflow dispatches to the restored runner group and execution results are visible.
- Inspect runner service health, registered status, outbound connectivity, group membership and host logs.
Explanation
Correct Answers
D:An authorized workflow dispatches to the restored runner group and execution results are visible. Inspect runner service health, registered status, outbound connectivity, group membership and host logs. An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution.
E:Inspect runner service health, registered status, outbound connectivity, group membership and host logs. An authorized workflow dispatches to the restored runner group and execution results are visible. Restore the supported runner service or replace the failed agent through an approved capacity and image process.
Incorrect Answers
A:Check the secret's selected-repository visibility settings and every workflow currently referencing it. It would not provide the evidence needed for the paired diagnosis and follow-up: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. Inspect runner service health, registered status, outbound connectivity, group membership and host logs. An authorized workflow dispatches to the restored runner group and execution results are visible.
B:The release pipeline runs with a vetted action while attempted substitution from an untrusted publisher is rejected. It would not verify whether the proposed change works: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. An authorized workflow dispatches to the restored runner group and execution results are visible. Restore the supported runner service or replace the failed agent through an approved capacity and image process.
C:Inspect trigger type, fork trust boundary, token permissions and secret availability for the affected job. It would not provide the evidence needed for the paired diagnosis and follow-up: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. Inspect runner service health, registered status, outbound connectivity, group membership and host logs. An authorized workflow dispatches to the restored runner group and execution results are visible.
Question 535
GitHub Enterprise administration scenario — Resolve offline runner provisioning failures. In an enterprise development environment: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. 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.
- Runner group policies should constrain repository and organization access to trusted workload boundaries.
- Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.
- An authorized workflow dispatches to the restored runner group and execution results are visible.
- Restore the supported runner service or replace the failed agent through an approved capacity and image process.
- An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution.
- Routine test jobs cannot receive production credentials and a reviewed deployment job still obtains its approved secret.
Explanation
Correct Answers
C:An authorized workflow dispatches to the restored runner group and execution results are visible. Restore the supported runner service or replace the failed agent through an approved capacity and image process. An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution.
D:Restore the supported runner service or replace the failed agent through an approved capacity and image process. An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution. An authorized workflow dispatches to the restored runner group and execution results are visible.
E:An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution. Restore the supported runner service or replace the failed agent through an approved capacity and image process. An authorized workflow dispatches to the restored runner group and execution results are visible.
Incorrect Answers
A:Runner group policies should constrain repository and organization access to trusted workload boundaries. It is not the rule that supports the proposed change and acceptance test: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution. Restore the supported runner service or replace the failed agent through an approved capacity and image process.
B:Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines. It does not implement the governing rule for this approval: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. Restore the supported runner service or replace the failed agent through an approved capacity and image process. An authorized workflow dispatches to the restored runner group and execution results are visible.
F:Routine test jobs cannot receive production credentials and a reviewed deployment job still obtains its approved secret. It would not independently demonstrate that the control works: A pipeline job remains queued while the designated runner group shows its only agent as offline after a platform patch. An authorized workflow dispatches to the restored runner group and execution results are visible. Restore the supported runner service or replace the failed agent through an approved capacity and image process.
Question 536
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. 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 concurrency controls can serialize mutually exclusive deployments when aligned with protected environments.
- Build caches are an input trust boundary and should not carry attacker-influenced execution material into privileged releases.
- Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.
- Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions.
Explanation
Correct Answer
A:Workflow concurrency controls can serialize mutually exclusive deployments when aligned with protected environments. Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior. Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics.
Incorrect Answers
B: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: 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.
C:Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets. It does not govern the condition described: 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.
D:Reusable workflows can centralize shared deployment logic while individual callers retain approved inputs and explicit permissions. It does not govern the condition described: 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.
Question 537
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. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior.
- Inspect trigger type, fork trust boundary, token permissions and secret availability for the affected job.
- Inspect required job boundaries, environment approvals, runner types and existing code reuse patterns.
- Review runner persistence, network reachability, PR trust conditions and available credentials or caches.
Explanation
Correct Answer
A:Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior. 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.
Incorrect Answers
B: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: Two production-deployment workflows start from consecutive commits and both run simultaneously, threatening to overwrite each other's release state. Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior.
C:Inspect required job boundaries, environment approvals, runner types and existing code reuse patterns. That check would not establish the decisive facts for this condition: Two production-deployment workflows start from consecutive commits and both run simultaneously, threatening to overwrite each other's release state. Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior.
D:Review runner persistence, network reachability, PR trust conditions and available credentials or caches. That check would not establish the decisive facts for this condition: Two production-deployment workflows start from consecutive commits and both run simultaneously, threatening to overwrite each other's release state. Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior.
Question 538
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. 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.
- Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs.
- Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics.
- Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
Explanation
Correct Answer
C:Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics. Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior. Sequential releases occur in the intended order and overlapping production mutation is prevented.
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: 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.
B:Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs. That change would leave the reported problem unresolved: 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.
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: 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.
Question 539
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. 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.
- Sequential releases occur in the intended order and overlapping production mutation is prevented.
- The release pipeline runs with a vetted action while attempted substitution from an untrusted publisher is rejected.
- Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates.
- Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets.
- Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior.
Explanation
Correct Answers
A:Sequential releases occur in the intended order and overlapping production mutation is prevented. Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior. Workflow concurrency controls can serialize mutually exclusive deployments when aligned with protected environments.
E:Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior. 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.
Incorrect Answers
B:The release pipeline runs with a vetted action while attempted substitution from an untrusted publisher is rejected. It would not verify whether the proposed change 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.
C:Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates. It would not provide the evidence needed for the paired diagnosis and follow-up: Two production-deployment workflows start from consecutive commits and both run simultaneously, threatening to overwrite each other's release state. Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior. Sequential releases occur in the intended order and overlapping production mutation is prevented.
D:Compare hosted runner usage, workflow matrix dimensions, cache efficiency and configured enterprise budgets. It would not provide the evidence needed for the paired diagnosis and follow-up: Two production-deployment workflows start from consecutive commits and both run simultaneously, threatening to overwrite each other's release state. Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior. Sequential releases occur in the intended order and overlapping production mutation is prevented.
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.