Microsoft GH-100 Practice Test 49
Question 480
GitHub Enterprise administration scenario — Constrain OIDC trust to reviewed workflow identity. In an enterprise development environment: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. 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.
- Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name.
- OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers.
- Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
- Runner group access matches the approved organization list and the change actor is recorded for investigation.
- Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role.
- Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.
Explanation
Correct Answers
A:Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions. Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role.
E:Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions. Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name.
F:Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions. Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name. Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role.
Incorrect Answers
B:OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers. It is not the rule that supports the proposed change and acceptance test: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.
C:Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities. It does not implement the governing rule for this approval: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions. Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role.
D:Runner group access matches the approved organization list and the change actor is recorded for investigation. It would not independently demonstrate that the control works: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.
Question 481
GitHub Enterprise administration scenario — Scope repository-level Actions secrets appropriately. In an enterprise development environment: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. 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.
- Secret availability must match job trust and deployment need rather than defaulting to repository-wide access.
- Organization secrets should be shared according to specific repository and environment authorization needs.
- Actions can retrieve secrets from supported vault-backed integrations using controlled workflow identity and network configuration.
- Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name.
Explanation
Correct Answer
A:Secret availability must match job trust and deployment need rather than defaulting to repository-wide access. Inspect all workflow triggers, secret references, required environments and existing repository security settings. Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.
Incorrect Answers
B:Organization secrets should be shared according to specific repository and environment authorization needs. It does not govern the condition described: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Secret availability must match job trust and deployment need rather than defaulting to repository-wide access.
C:Actions can retrieve secrets from supported vault-backed integrations using controlled workflow identity and network configuration. It does not govern the condition described: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Secret availability must match job trust and deployment need rather than defaulting to repository-wide access.
D: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 developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Secret availability must match job trust and deployment need rather than defaulting to repository-wide access.
Question 482
GitHub Enterprise administration scenario — Scope repository-level Actions secrets appropriately. In an enterprise development environment: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows.
- Inspect effective GITHUB_TOKEN settings, event types and the API actions made by the test job.
- Review artifact classes, existing retention settings, regulated records and actual download needs.
- Inspect all workflow triggers, secret references, required environments and existing repository security settings.
Explanation
Correct Answer
D:Inspect all workflow triggers, secret references, required environments and existing repository security settings. Secret availability must match job trust and deployment need rather than defaulting to repository-wide access. Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.
Incorrect Answers
A:Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows. That check would not establish the decisive facts for this condition: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Inspect all workflow triggers, secret references, required environments and existing repository security settings.
B:Inspect effective GITHUB_TOKEN settings, event types and the API actions made by the test job. That check would not establish the decisive facts for this condition: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Inspect all workflow triggers, secret references, required environments and existing repository security settings.
C:Review artifact classes, existing retention settings, regulated records and actual download needs. That check would not establish the decisive facts for this condition: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Inspect all workflow triggers, secret references, required environments and existing repository security settings.
Question 483
GitHub Enterprise administration scenario — Scope repository-level Actions secrets appropriately. In an enterprise development environment: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. 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.
- Limit secret availability to approved repositories and document the integration owner and rotation schedule.
- Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.
- Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed.
Explanation
Correct Answer
C:Move the credential to a protected environment or approved vault-backed access route with controlled job permissions. Inspect all workflow triggers, secret references, required environments and existing repository security settings. Routine test jobs cannot receive production credentials and a reviewed deployment job still obtains its approved secret.
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 developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.
B:Limit secret availability to approved repositories and document the integration owner and rotation schedule. That change would leave the reported problem unresolved: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.
D:Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed. That change would leave the reported problem unresolved: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.
Question 484
GitHub Enterprise administration scenario — Scope repository-level Actions secrets appropriately. In an enterprise development environment: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. 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.
- Inspect all workflow triggers, secret references, required environments and existing repository security settings.
- Hung jobs terminate within the approved window and normal tests still finish with complete results.
- Examine the caller's secret inheritance, callee permissions, environment protection and required credentials.
- Routine test jobs cannot receive production credentials and a reviewed deployment job still obtains its approved secret.
Explanation
Correct Answers
B:Inspect all workflow triggers, secret references, required environments and existing repository security settings. Routine test jobs cannot receive production credentials and a reviewed deployment job still obtains its approved secret. Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.
E:Routine test jobs cannot receive production credentials and a reviewed deployment job still obtains its approved secret. Inspect all workflow triggers, secret references, required environments and existing repository security settings. Secret availability must match job trust and deployment need rather than defaulting to repository-wide access.
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 developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Inspect all workflow triggers, secret references, required environments and existing repository security settings. Routine test jobs cannot receive production credentials and a reviewed deployment job still obtains its approved secret.
C:Hung jobs terminate within the approved window and normal tests still finish with complete results. It would not verify whether the proposed change works: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Routine test jobs cannot receive production credentials and a reviewed deployment job still obtains its approved secret. Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.
D:Examine the caller's secret inheritance, callee permissions, environment protection and required credentials. It would not provide the evidence needed for the paired diagnosis and follow-up: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Inspect all workflow triggers, secret references, required environments and existing repository security settings. Routine test jobs cannot receive production credentials and a reviewed deployment job still obtains its approved secret.
Question 485
GitHub Enterprise administration scenario — Scope repository-level Actions secrets appropriately. In an enterprise development environment: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. 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.
- Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
- Secret availability must match job trust and deployment need rather than defaulting to repository-wide access.
- Routine test jobs cannot receive production credentials and a reviewed deployment job still obtains its approved secret.
- Third-party actions execute code in workflow security context and require trust, permission and change reviews.
- Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.
- New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow.
Explanation
Correct Answers
B:Secret availability must match job trust and deployment need rather than defaulting to repository-wide access. Move the credential to a protected environment or approved vault-backed access route with controlled job permissions. Routine test jobs cannot receive production credentials and a reviewed deployment job still obtains its approved secret.
C:Routine test jobs cannot receive production credentials and a reviewed deployment job still obtains its approved secret. Move the credential to a protected environment or approved vault-backed access route with controlled job permissions. Secret availability must match job trust and deployment need rather than defaulting to repository-wide access.
E:Move the credential to a protected environment or approved vault-backed access route with controlled job permissions. Secret availability must match job trust and deployment need rather than defaulting to repository-wide access. Routine test jobs cannot receive production credentials and a reviewed deployment job still obtains its approved secret.
Incorrect Answers
A: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 developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Move the credential to a protected environment or approved vault-backed access route with controlled job permissions. Routine test jobs cannot receive production credentials and a reviewed deployment job still obtains its approved secret.
D:Third-party actions execute code in workflow security context and require trust, permission and change reviews. It is not the rule that supports the proposed change and acceptance test: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Secret availability must match job trust and deployment need rather than defaulting to repository-wide access. Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.
F: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 independently demonstrate that the control works: A developer stores an environment-wide production database credential as a repository secret accessible to every workflow, including ordinary pull request checks. Routine test jobs cannot receive production credentials and a reviewed deployment job still obtains its approved secret. Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.
Question 486
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. 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.
- OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers.
- Organization secrets should be shared according to specific repository and environment authorization needs.
- Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.
- Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface.
Explanation
Correct Answer
B:Organization secrets should be shared according to specific repository and environment authorization needs. Check the secret's selected-repository visibility settings and every workflow currently referencing it. Limit secret availability to approved repositories and document the integration owner and rotation schedule.
Incorrect Answers
A:OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers. It does not govern the condition described: 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.
C:Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets. It does not govern the condition described: 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.
D:Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface. It does not govern the condition described: A 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.
Question 487
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. 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 artifact classes, existing retention settings, regulated records and actual download needs.
- Check the secret's selected-repository visibility settings and every workflow currently referencing it.
- Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference.
Explanation
Correct Answer
C:Check the secret's selected-repository visibility settings and every workflow currently referencing 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.
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 shared cloud testing secret was configured for all repositories in a GitHub organization although only two internal projects use it. Check the secret's selected-repository visibility settings and every workflow currently referencing it.
B:Review artifact classes, existing retention settings, regulated records and actual download needs. That check would not establish the decisive facts for this condition: A shared cloud testing secret was configured for all repositories in a GitHub organization although only two internal projects use it. Check the secret's selected-repository visibility settings and every workflow currently referencing it.
D:Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference. That check would not establish the decisive facts for this condition: A shared cloud testing secret was configured for all repositories in a GitHub organization although only two internal projects use it. Check the secret's selected-repository visibility settings and every workflow currently referencing it.
Question 488
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. 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.
- Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
- Limit secret availability to approved repositories and document the integration owner and rotation schedule.
- Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts.
- Configure a least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs.
Explanation
Correct Answer
B:Limit secret availability to approved repositories and document the integration owner and rotation schedule. Check the secret's selected-repository visibility settings and every workflow currently referencing it. Unapproved repositories cannot access the secret while intended jobs in the selected projects continue working.
Incorrect Answers
A: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 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.
C:Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts. That change would leave the reported problem unresolved: 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.
D:Configure a least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs. That change would leave the reported problem unresolved: 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.
Question 489
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. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.
- Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions.
- Inspect the reusable repository's visibility, access settings and the caller's organization policy.
- An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access.
- Unapproved repositories cannot access the secret while intended jobs in the selected projects continue working.
- Check the secret's selected-repository visibility settings and every workflow currently referencing it.
Explanation
Correct Answers
D:Unapproved repositories cannot access the secret while intended jobs in the selected projects continue working. Check the secret's selected-repository visibility settings and every workflow currently referencing it. Organization secrets should be shared according to specific repository and environment authorization needs.
E:Check the secret's selected-repository visibility settings and every workflow currently referencing 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.
Incorrect Answers
A: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: A shared cloud testing secret was configured for all repositories in a GitHub organization although only two internal projects use it. Check the secret's selected-repository visibility settings and every workflow currently referencing it. Unapproved repositories cannot access the secret while intended jobs in the selected projects continue working.
B:Inspect the reusable repository's visibility, access settings and the caller's organization policy. It would not provide the evidence needed for the paired diagnosis and follow-up: A shared cloud testing secret was configured for all repositories in a GitHub organization although only two internal projects use it. Check the secret's selected-repository visibility settings and every workflow currently referencing it. Unapproved repositories cannot access the secret while intended jobs in the selected projects continue working.
C:An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access. It would not verify whether the proposed change 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.
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.