Microsoft GH-100 Practice Test 30
Question 290
GitHub Enterprise administration scenario — Protect main branches and release tags with rulesets. In an enterprise development environment: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. 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.
- Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.
- Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls.
- Evaluate the product's supported integration model and approve only the least-privilege application type and rights.
- The bot comments in its assigned repository and access checks fail for unrelated private repositories.
- Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.
- Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.
Explanation
Correct Answers
A:Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures. Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls.
B:Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.
F:Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures. Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.
Incorrect Answers
C:Evaluate the product's supported integration model and approve only the least-privilege application type and rights. It does not implement the governing rule for this approval: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.
D:The bot comments in its assigned repository and access checks fail for unrelated private repositories. It would not independently demonstrate that the control works: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.
E:Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy. It is not the rule that supports the proposed change and acceptance test: A service team has required reviews on its main branch but unprotected release tags can still be replaced after deployment. Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls. Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.
Question 291
GitHub Enterprise administration scenario — Review a ruleset bypass that hides peer review. In an enterprise development environment: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. 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.
- Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
- Fine-grained personal access and approval policies can limit an integration to the minimum required resources.
- Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability.
- Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.
Explanation
Correct Answer
C:Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability. Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception. Limit bypass authority and require an approved accountable emergency pathway with post-event review.
Incorrect Answers
A:Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope. It does not govern the condition described: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability.
B:Fine-grained personal access and approval policies can limit an integration to the minimum required resources. It does not govern the condition described: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability.
D:Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy. It does not govern the condition described: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability.
Question 292
GitHub Enterprise administration scenario — Review a ruleset bypass that hides peer review. In an enterprise development environment: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs.
- Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies.
- Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception.
- Review supported languages, build commands, checkout depth, workflow logs and the failed extraction stage.
Explanation
Correct Answer
C:Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception. Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability. Limit bypass authority and require an approved accountable emergency pathway with post-event review.
Incorrect Answers
A:Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs. That check would not establish the decisive facts for this condition: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception.
B:Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies. That check would not establish the decisive facts for this condition: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception.
D:Review supported languages, build commands, checkout depth, workflow logs and the failed extraction stage. That check would not establish the decisive facts for this condition: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception.
Question 293
GitHub Enterprise administration scenario — Review a ruleset bypass that hides peer review. In an enterprise development environment: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. 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.
- Enable supported security update pull requests with owned reviewers and controlled merge rules.
- Limit bypass authority and require an approved accountable emergency pathway with post-event review.
- Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight.
- Define and track risk-based remediation targets with approved escalation for overdue high-risk findings.
Explanation
Correct Answer
B:Limit bypass authority and require an approved accountable emergency pathway with post-event review. Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception. Normal changes receive required review and exceptional bypasses have recorded owners and reasons.
Incorrect Answers
A:Enable supported security update pull requests with owned reviewers and controlled merge rules. That change would leave the reported problem unresolved: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Limit bypass authority and require an approved accountable emergency pathway with post-event review.
C:Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight. That change would leave the reported problem unresolved: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Limit bypass authority and require an approved accountable emergency pathway with post-event review.
D:Define and track risk-based remediation targets with approved escalation for overdue high-risk findings. That change would leave the reported problem unresolved: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Limit bypass authority and require an approved accountable emergency pathway with post-event review.
Question 294
GitHub Enterprise administration scenario — Review a ruleset bypass that hides peer review. In an enterprise development environment: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. 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.
- Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries.
- Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs.
- Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.
- Normal changes receive required review and exceptional bypasses have recorded owners and reasons.
- Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception.
Explanation
Correct Answers
D:Normal changes receive required review and exceptional bypasses have recorded owners and reasons. Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception. Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability.
E:Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception. Normal changes receive required review and exceptional bypasses have recorded owners and reasons. Limit bypass authority and require an approved accountable emergency pathway with post-event review.
Incorrect Answers
A:Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries. It would not provide the evidence needed for the paired diagnosis and follow-up: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception. Normal changes receive required review and exceptional bypasses have recorded owners and reasons.
B:Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs. It would not provide the evidence needed for the paired diagnosis and follow-up: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception. Normal changes receive required review and exceptional bypasses have recorded owners and reasons.
C:Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits. It would not verify whether the proposed change works: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Normal changes receive required review and exceptional bypasses have recorded owners and reasons. Limit bypass authority and require an approved accountable emergency pathway with post-event review.
Question 295
GitHub Enterprise administration scenario — Review a ruleset bypass that hides peer review. In an enterprise development environment: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. 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.
- Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability.
- Both organizations follow the same mandatory repository security rule without accidental creation of public assets.
- Untrusted fork code must not receive secrets or broad workflow privileges simply to perform tests.
- Limit bypass authority and require an approved accountable emergency pathway with post-event review.
- Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation.
- Normal changes receive required review and exceptional bypasses have recorded owners and reasons.
Explanation
Correct Answers
A:Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability. Limit bypass authority and require an approved accountable emergency pathway with post-event review. Normal changes receive required review and exceptional bypasses have recorded owners and reasons.
D:Limit bypass authority and require an approved accountable emergency pathway with post-event review. Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability. Normal changes receive required review and exceptional bypasses have recorded owners and reasons.
F:Normal changes receive required review and exceptional bypasses have recorded owners and reasons. Limit bypass authority and require an approved accountable emergency pathway with post-event review. Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability.
Incorrect Answers
B:Both organizations follow the same mandatory repository security rule without accidental creation of public assets. It would not independently demonstrate that the control works: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Normal changes receive required review and exceptional bypasses have recorded owners and reasons. Limit bypass authority and require an approved accountable emergency pathway with post-event review.
C:Untrusted fork code must not receive secrets or broad workflow privileges simply to perform tests. It is not the rule that supports the proposed change and acceptance test: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability. Limit bypass authority and require an approved accountable emergency pathway with post-event review.
E:Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation. It does not implement the governing rule for this approval: A user designated as a bypass actor can merge directly to the production branch without the approvals ordinarily required from peer maintainers. Limit bypass authority and require an approved accountable emergency pathway with post-event review. Normal changes receive required review and exceptional bypasses have recorded owners and reasons.
Question 296
GitHub Enterprise administration scenario — Require code owners for sensitive paths. In an enterprise development environment: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. 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.
- Deleting committed text does not revoke an already exposed credential or erase all earlier history and copies.
- Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls.
- SAML-protected resources can require token authorization independent of interactive account sign-in.
- Path-specific review can direct sensitive changes to authorized subject-matter owners before merge.
Explanation
Correct Answer
D:Path-specific review can direct sensitive changes to authorized subject-matter owners before merge. Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets. Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance.
Incorrect Answers
A:Deleting committed text does not revoke an already exposed credential or erase all earlier history and copies. It does not govern the condition described: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. Path-specific review can direct sensitive changes to authorized subject-matter owners before merge.
B:Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls. It does not govern the condition described: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. Path-specific review can direct sensitive changes to authorized subject-matter owners before merge.
C:SAML-protected resources can require token authorization independent of interactive account sign-in. It does not govern the condition described: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. Path-specific review can direct sensitive changes to authorized subject-matter owners before merge.
Question 297
GitHub Enterprise administration scenario — Require code owners for sensitive paths. In an enterprise development environment: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect workflow event triggers, token permissions, secret exposure paths and the executed checkout reference.
- Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets.
- Compare current token ownership, required API endpoints, repository selection and supported GitHub App permission model.
- Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options.
Explanation
Correct Answer
B:Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets. Path-specific review can direct sensitive changes to authorized subject-matter owners before merge. Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance.
Incorrect Answers
A:Inspect workflow event triggers, token permissions, secret exposure paths and the executed checkout reference. That check would not establish the decisive facts for this condition: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets.
C:Compare current token ownership, required API endpoints, repository selection and supported GitHub App permission model. That check would not establish the decisive facts for this condition: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets.
D:Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options. That check would not establish the decisive facts for this condition: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets.
Question 298
GitHub Enterprise administration scenario — Require code owners for sensitive paths. In an enterprise development environment: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. 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.
- Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance.
- Create and apply an approved security baseline to eligible repositories with exception ownership and periodic coverage reports.
- Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
- Apply a centrally approved policy baseline and allow only formally approved supported exceptions.
Explanation
Correct Answer
A:Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance. Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets. A change touching deployment configuration requires an appropriate owner's approval before merge.
Incorrect Answers
B:Create and apply an approved security baseline to eligible repositories with exception ownership and periodic coverage reports. That change would leave the reported problem unresolved: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance.
C:Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results. That change would leave the reported problem unresolved: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance.
D:Apply a centrally approved policy baseline and allow only formally approved supported exceptions. That change would leave the reported problem unresolved: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance.
Question 299
GitHub Enterprise administration scenario — Require code owners for sensitive paths. In an enterprise development environment: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.
- Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage.
- Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets.
- Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy.
- The inventory job succeeds with limited rights and the old credential is rejected after revocation.
- A change touching deployment configuration requires an appropriate owner's approval before merge.
Explanation
Correct Answers
B:Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets. A change touching deployment configuration requires an appropriate owner's approval before merge. Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance.
E:A change touching deployment configuration requires an appropriate owner's approval before merge. Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets. Path-specific review can direct sensitive changes to authorized subject-matter owners before merge.
Incorrect Answers
A:Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage. It would not provide the evidence needed for the paired diagnosis and follow-up: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets. A change touching deployment configuration requires an appropriate owner's approval before merge.
C:Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy. It would not provide the evidence needed for the paired diagnosis and follow-up: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets. A change touching deployment configuration requires an appropriate owner's approval before merge.
D:The inventory job succeeds with limited rights and the old credential is rejected after revocation. It would not verify whether the proposed change works: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. A change touching deployment configuration requires an appropriate owner's approval before merge. Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance.
Question 300
GitHub Enterprise administration scenario — Require code owners for sensitive paths. In an enterprise development environment: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. 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.
- Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance.
- Limit the installation to the required repository with only the necessary issues or pull request permissions.
- Path-specific review can direct sensitive changes to authorized subject-matter owners before merge.
- Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
- The tool performs its required repository operation without reading unrelated repositories or changing organization settings.
- A change touching deployment configuration requires an appropriate owner's approval before merge.
Explanation
Correct Answers
A:Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance. Path-specific review can direct sensitive changes to authorized subject-matter owners before merge. A change touching deployment configuration requires an appropriate owner's approval before merge.
C:Path-specific review can direct sensitive changes to authorized subject-matter owners before merge. Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance. A change touching deployment configuration requires an appropriate owner's approval before merge.
F:A change touching deployment configuration requires an appropriate owner's approval before merge. Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance. Path-specific review can direct sensitive changes to authorized subject-matter owners before merge.
Incorrect Answers
B:Limit the installation to the required repository with only the necessary issues or pull request permissions. It does not implement the governing rule for this approval: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance. A change touching deployment configuration requires an appropriate owner's approval before merge.
D:Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope. It is not the rule that supports the proposed change and acceptance test: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. Path-specific review can direct sensitive changes to authorized subject-matter owners before merge. Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance.
E:The tool performs its required repository operation without reading unrelated repositories or changing organization settings. It would not independently demonstrate that the control works: A payment service's deployment configuration is changed in a pull request without review from the infrastructure owners who understand production secrets. A change touching deployment configuration requires an appropriate owner's approval before merge. Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance.