Microsoft GH-100 Practice Test 50
Question 490
GitHub Enterprise administration scenario — Restrict organization secret sharing to selected repositories. In an enterprise development environment: A shared cloud testing secret was configured for all repositories in a GitHub organization although only two internal projects use it. 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.
- Unapproved repositories cannot access the secret while intended jobs in the selected projects continue working.
- Labels are applied correctly while untrusted PR scripts cannot run with the privileged workflow's token.
- Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface.
- Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
- Organization secrets should be shared according to specific repository and environment authorization needs.
- Limit secret availability to approved repositories and document the integration owner and rotation schedule.
Explanation
Correct Answers
A:Unapproved repositories cannot access the secret while intended jobs in the selected projects continue working. Limit secret availability to approved repositories and document the integration owner and rotation schedule. Organization secrets should be shared according to specific repository and environment authorization needs.
E:Organization secrets should be shared according to specific repository and environment authorization needs. Limit secret availability to approved repositories and document the integration owner and rotation schedule. Unapproved repositories cannot access the secret while intended jobs in the selected projects continue working.
F:Limit secret availability to approved repositories and document the integration owner and rotation schedule. Organization secrets should be shared according to specific repository and environment authorization needs. Unapproved repositories cannot access the secret while intended jobs in the selected projects continue working.
Incorrect Answers
B:Labels are applied correctly while untrusted PR scripts cannot run with the privileged workflow's token. It would not independently demonstrate that the control works: A shared cloud testing secret was configured for all repositories in a GitHub organization although only two internal projects use it. Unapproved repositories cannot access the secret while intended jobs in the selected projects continue working. Limit secret availability to approved repositories and document the integration owner and rotation schedule.
C:Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface. It is not the rule that supports the proposed change and acceptance test: A shared cloud testing secret was configured for all repositories in a GitHub organization although only two internal projects use it. Organization secrets should be shared according to specific repository and environment authorization needs. Limit secret availability to approved repositories and document the integration owner and rotation schedule.
D: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 shared cloud testing secret was configured for all repositories in a GitHub organization although only two internal projects use it. Limit secret availability to approved repositories and document the integration owner and rotation schedule. Unapproved repositories cannot access the secret while intended jobs in the selected projects continue working.
Question 491
GitHub Enterprise administration scenario — Require environment protection for release secrets. In an enterprise development environment: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. 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.
- Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership.
- Workflow execution plans should balance required test coverage and resource cost within approved budgets.
- Secret availability must match job trust and deployment need rather than defaulting to repository-wide access.
Explanation
Correct Answer
A:Protected deployment environments help enforce authorized release gates and restrict production secret access. Review environment branch restrictions, required reviewers, workflow triggers and production secret placement. Configure supported environment protection rules and route release jobs through the protected environment.
Incorrect Answers
B:Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership. It does not govern the condition described: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. Protected deployment environments help enforce authorized release gates and restrict production secret access.
C:Workflow execution plans should balance required test coverage and resource cost within approved budgets. It does not govern the condition described: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. Protected deployment environments help enforce authorized release gates and restrict production secret access.
D:Secret availability must match job trust and deployment need rather than defaulting to repository-wide access. It does not govern the condition described: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. Protected deployment environments help enforce authorized release gates and restrict production secret access.
Question 492
GitHub Enterprise administration scenario — Require environment protection for release secrets. In an enterprise development environment: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing.
- Review environment branch restrictions, required reviewers, workflow triggers and production secret placement.
- Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows.
- Correlate audit log policy-change events, runner group access history and approved maintenance tickets.
Explanation
Correct Answer
B:Review environment branch restrictions, required reviewers, workflow triggers and production secret placement. Protected deployment environments help enforce authorized release gates and restrict production secret access. Configure supported environment protection rules and route release jobs through the protected environment.
Incorrect Answers
A:Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing. That check would not establish the decisive facts for this condition: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. Review environment branch restrictions, required reviewers, workflow triggers and production secret placement.
C:Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows. That check would not establish the decisive facts for this condition: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. Review environment branch restrictions, required reviewers, workflow triggers and production secret placement.
D:Correlate audit log policy-change events, runner group access history and approved maintenance tickets. That check would not establish the decisive facts for this condition: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. Review environment branch restrictions, required reviewers, workflow triggers and production secret placement.
Question 493
GitHub Enterprise administration scenario — Require environment protection for release secrets. In an enterprise development environment: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. 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.
- Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries.
- Configure supported environment protection rules and route release jobs through the protected environment.
- Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key.
- Provide the supported workflow template together with enforceable Actions policies and measured adoption checks.
Explanation
Correct Answer
B:Configure supported environment protection rules and route release jobs through the protected environment. Review environment branch restrictions, required reviewers, workflow triggers and production secret placement. A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released.
Incorrect Answers
A:Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries. That change would leave the reported problem unresolved: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. Configure supported environment protection rules and route release jobs through the protected environment.
C:Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key. That change would leave the reported problem unresolved: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. Configure supported environment protection rules and route release jobs through the protected environment.
D:Provide the supported workflow template together with enforceable Actions policies and measured adoption checks. That change would leave the reported problem unresolved: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. Configure supported environment protection rules and route release jobs through the protected environment.
Question 494
GitHub Enterprise administration scenario — Require environment protection for release secrets. In an enterprise development environment: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. 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 cloud trust settings, workflow identity claims, repository environments and current deployment secret use.
- Production deployments continue using federation and the retired key fails in a credential validation test.
- Compare build resource needs, private endpoint access, supported runner networking and required trust posture.
- A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released.
- Review environment branch restrictions, required reviewers, workflow triggers and production secret placement.
Explanation
Correct Answers
D:A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released. Review environment branch restrictions, required reviewers, workflow triggers and production secret placement. Protected deployment environments help enforce authorized release gates and restrict production secret access.
E:Review environment branch restrictions, required reviewers, workflow triggers and production secret placement. A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released. Configure supported environment protection rules and route release jobs through the protected environment.
Incorrect Answers
A:Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use. It would not provide the evidence needed for the paired diagnosis and follow-up: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. Review environment branch restrictions, required reviewers, workflow triggers and production secret placement. A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released.
B:Production deployments continue using federation and the retired key fails in a credential validation test. It would not verify whether the proposed change works: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released. Configure supported environment protection rules and route release jobs through the protected environment.
C:Compare build resource needs, private endpoint access, supported runner networking and required trust posture. It would not provide the evidence needed for the paired diagnosis and follow-up: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. Review environment branch restrictions, required reviewers, workflow triggers and production secret placement. A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released.
Question 495
GitHub Enterprise administration scenario — Require environment protection for release secrets. In an enterprise development environment: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. 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.
- Configure supported environment protection rules and route release jobs through the protected environment.
- A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released.
- Runner capacity and queue telemetry should determine scaling actions instead of broad permission exceptions.
- Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries.
- Protected deployment environments help enforce authorized release gates and restrict production secret access.
Explanation
Correct Answers
B:Configure supported environment protection rules and route release jobs through the protected environment. Protected deployment environments help enforce authorized release gates and restrict production secret access. A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released.
C:A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released. Configure supported environment protection rules and route release jobs through the protected environment. Protected deployment environments help enforce authorized release gates and restrict production secret access.
F:Protected deployment environments help enforce authorized release gates and restrict production secret access. Configure supported environment protection rules and route release jobs through the protected environment. A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released.
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 release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released. Configure supported environment protection rules and route release jobs through the protected environment.
D:Runner capacity and queue telemetry should determine scaling actions instead of broad permission exceptions. It is not the rule that supports the proposed change and acceptance test: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. Protected deployment environments help enforce authorized release gates and restrict production secret access. Configure supported environment protection rules and route release jobs through the protected environment.
E:Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries. It does not implement the governing rule for this approval: A release workflow can deploy production code immediately after a developer pushes any branch because its environment does not require approvals. Configure supported environment protection rules and route release jobs through the protected environment. A deployment waits for the appropriate reviewer and rejects an unapproved branch before production credentials are released.
Question 496
GitHub Enterprise administration scenario — Use enterprise runner groups for project isolation. In an enterprise development environment: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. 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.
- Actions can retrieve secrets from supported vault-backed integrations using controlled workflow identity and network configuration.
- Job timeouts and cancellation handling protect finite runner capacity while preserving diagnosable failures.
- Runner group policies should constrain repository and organization access to trusted workload boundaries.
Explanation
Correct Answer
D:Runner group policies should constrain repository and organization access to trusted workload boundaries. Inspect runner group scope, repository allow policy, runner labels and the jobs scheduled on the same host. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
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 shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Runner group policies should constrain repository and organization access to trusted workload boundaries.
B:Actions can retrieve secrets from supported vault-backed integrations using controlled workflow identity and network configuration. It does not govern the condition described: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Runner group policies should constrain repository and organization access to trusted workload boundaries.
C:Job timeouts and cancellation handling protect finite runner capacity while preserving diagnosable failures. It does not govern the condition described: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Runner group policies should constrain repository and organization access to trusted workload boundaries.
Question 497
GitHub Enterprise administration scenario — Use enterprise runner groups for project isolation. In an enterprise development environment: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect runner group scope, repository allow policy, runner labels and the jobs scheduled on the same host.
- Review runner persistence, network reachability, PR trust conditions and available credentials or caches.
- Inspect trigger type, fork trust boundary, token permissions and secret availability for the affected job.
- Examine the caller's secret inheritance, callee permissions, environment protection and required credentials.
Explanation
Correct Answer
A:Inspect runner group scope, repository allow policy, runner labels and the jobs scheduled on the same host. Runner group policies should constrain repository and organization access to trusted workload boundaries. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
Incorrect Answers
B:Review runner persistence, network reachability, PR trust conditions and available credentials or caches. That check would not establish the decisive facts for this condition: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Inspect runner group scope, repository allow policy, runner labels and the jobs scheduled on the same host.
C: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: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Inspect runner group scope, repository allow policy, runner labels and the jobs scheduled on the same host.
D:Examine the caller's secret inheritance, callee permissions, environment protection and required credentials. That check would not establish the decisive facts for this condition: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Inspect runner group scope, repository allow policy, runner labels and the jobs scheduled on the same host.
Question 498
GitHub Enterprise administration scenario — Use enterprise runner groups for project isolation. In an enterprise development environment: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. 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.
- Create the supported larger runner configuration and restrict it to approved repositories or runner groups.
- Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests.
- Pin critical third-party actions to vetted immutable commits and use an accountable update review process.
- Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
Explanation
Correct Answer
D:Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories. Inspect runner group scope, repository allow policy, runner labels and the jobs scheduled on the same host. The payment release can use its runner pool while an unrelated repository cannot schedule jobs there.
Incorrect Answers
A:Create the supported larger runner configuration and restrict it to approved repositories or runner groups. That change would leave the reported problem unresolved: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
B:Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests. That change would leave the reported problem unresolved: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
C:Pin critical third-party actions to vetted immutable commits and use an accountable update review process. That change would leave the reported problem unresolved: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
Question 499
GitHub Enterprise administration scenario — Use enterprise runner groups for project isolation. In an enterprise development environment: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. 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 runner group scope, repository allow policy, runner labels and the jobs scheduled on the same host.
- A fork pull request receives only safe read access and cannot access deployment credentials in a controlled test.
- Review historical execution durations, external call retry behavior and the workflow's current timeout settings.
- The payment release can use its runner pool while an unrelated repository cannot schedule jobs there.
- Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets.
Explanation
Correct Answers
A:Inspect runner group scope, repository allow policy, runner labels and the jobs scheduled on the same host. The payment release can use its runner pool while an unrelated repository cannot schedule jobs there. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
D:The payment release can use its runner pool while an unrelated repository cannot schedule jobs there. Inspect runner group scope, repository allow policy, runner labels and the jobs scheduled on the same host. Runner group policies should constrain repository and organization access to trusted workload boundaries.
Incorrect Answers
B:A fork pull request receives only safe read access and cannot access deployment credentials in a controlled test. It would not verify whether the proposed change works: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. The payment release can use its runner pool while an unrelated repository cannot schedule jobs there. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
C:Review historical execution durations, external call retry behavior and the workflow's current timeout settings. It would not provide the evidence needed for the paired diagnosis and follow-up: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Inspect runner group scope, repository allow policy, runner labels and the jobs scheduled on the same host. The payment release can use its runner pool while an unrelated repository cannot schedule jobs there.
E:Trace the workflow's event context, checked-out ref, executed commands, token permission and available secrets. It would not provide the evidence needed for the paired diagnosis and follow-up: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Inspect runner group scope, repository allow policy, runner labels and the jobs scheduled on the same host. The payment release can use its runner pool while an unrelated repository cannot schedule jobs there.
Question 500
GitHub Enterprise administration scenario — Use enterprise runner groups for project isolation. In an enterprise development environment: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. 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.
- Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.
- A malicious test title is processed as inert data and cannot trigger an unintended shell command.
- Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics.
- Runner group policies should constrain repository and organization access to trusted workload boundaries.
- Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
- The payment release can use its runner pool while an unrelated repository cannot schedule jobs there.
Explanation
Correct Answers
D:Runner group policies should constrain repository and organization access to trusted workload boundaries. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories. The payment release can use its runner pool while an unrelated repository cannot schedule jobs there.
E:Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories. Runner group policies should constrain repository and organization access to trusted workload boundaries. The payment release can use its runner pool while an unrelated repository cannot schedule jobs there.
F:The payment release can use its runner pool while an unrelated repository cannot schedule jobs there. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories. Runner group policies should constrain repository and organization access to trusted workload boundaries.
Incorrect Answers
A:Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets. It is not the rule that supports the proposed change and acceptance test: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Runner group policies should constrain repository and organization access to trusted workload boundaries. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
B:A malicious test title is processed as inert data and cannot trigger an unintended shell command. It would not independently demonstrate that the control works: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. The payment release can use its runner pool while an unrelated repository cannot schedule jobs there. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
C:Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics. It does not implement the governing rule for this approval: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories. The payment release can use its runner pool while an unrelated repository cannot schedule jobs there.