Microsoft GH-100 Practice Test 34
Question 330
GitHub Enterprise administration scenario — Aggregate security governance evidence across organizations. In an enterprise development environment: Compliance auditors request proof that dozens of GitHub organizations follow the same secret-protection and branch-review rules, but screenshots from one pilot team are offered as evidence. 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.
- The audit sample demonstrates required controls for every selected organization or records justified deviations.
- Known-format test tokens trigger alerts without overwhelming benign repository files.
- Public exposure and historical clones require incident scoping beyond a later repository visibility change.
- Compliance evidence should establish effective control coverage across the actual governed scope, not only the intended policy.
- Enable appropriate external collection before incidents and document search sources by event type.
- Produce a repeatable cross-organization effective-control report and assign remediation to owners of exceptions.
Explanation
Correct Answers
A:The audit sample demonstrates required controls for every selected organization or records justified deviations. Produce a repeatable cross-organization effective-control report and assign remediation to owners of exceptions. Compliance evidence should establish effective control coverage across the actual governed scope, not only the intended policy.
D:Compliance evidence should establish effective control coverage across the actual governed scope, not only the intended policy. Produce a repeatable cross-organization effective-control report and assign remediation to owners of exceptions. The audit sample demonstrates required controls for every selected organization or records justified deviations.
F:Produce a repeatable cross-organization effective-control report and assign remediation to owners of exceptions. Compliance evidence should establish effective control coverage across the actual governed scope, not only the intended policy. The audit sample demonstrates required controls for every selected organization or records justified deviations.
Incorrect Answers
B:Known-format test tokens trigger alerts without overwhelming benign repository files. It would not independently demonstrate that the control works: Compliance auditors request proof that dozens of GitHub organizations follow the same secret-protection and branch-review rules, but screenshots from one pilot team are offered as evidence. The audit sample demonstrates required controls for every selected organization or records justified deviations. Produce a repeatable cross-organization effective-control report and assign remediation to owners of exceptions.
C:Public exposure and historical clones require incident scoping beyond a later repository visibility change. It is not the rule that supports the proposed change and acceptance test: Compliance auditors request proof that dozens of GitHub organizations follow the same secret-protection and branch-review rules, but screenshots from one pilot team are offered as evidence. Compliance evidence should establish effective control coverage across the actual governed scope, not only the intended policy. Produce a repeatable cross-organization effective-control report and assign remediation to owners of exceptions.
E:Enable appropriate external collection before incidents and document search sources by event type. It does not implement the governing rule for this approval: Compliance auditors request proof that dozens of GitHub organizations follow the same secret-protection and branch-review rules, but screenshots from one pilot team are offered as evidence. Produce a repeatable cross-organization effective-control report and assign remediation to owners of exceptions. The audit sample demonstrates required controls for every selected organization or records justified deviations.
Question 331
GitHub Enterprise administration scenario — Define accountable evidence for compliance reviews. In an enterprise development environment: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies 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.
- Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone.
- SAML-protected resources can require token authorization independent of interactive account sign-in.
- Dependency graph completeness depends on supported manifests and any required submission or extraction configuration.
- Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance.
Explanation
Correct Answer
A:Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone. Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events. Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
Incorrect Answers
B:SAML-protected resources can require token authorization independent of interactive account sign-in. It does not govern the condition described: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone.
C:Dependency graph completeness depends on supported manifests and any required submission or extraction configuration. It does not govern the condition described: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone.
D:Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance. It does not govern the condition described: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone.
Question 332
GitHub Enterprise administration scenario — Define accountable evidence for compliance reviews. In an enterprise development environment: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries.
- Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy.
- Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status.
- Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events.
Explanation
Correct Answer
D:Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events. Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone. Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
Incorrect Answers
A:Audit organizational settings, effective enterprise policies, and repository visibility exceptions across subsidiaries. That check would not establish the decisive facts for this condition: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events.
B:Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy. That check would not establish the decisive facts for this condition: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events.
C:Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status. That check would not establish the decisive facts for this condition: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events.
Question 333
GitHub Enterprise administration scenario — Define accountable evidence for compliance reviews. In an enterprise development environment: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies 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.
- Restrict public repository creation through supported governing policy and provide a controlled publication review.
- Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance.
- Limit bypass authority and require an approved accountable emergency pathway with post-event review.
- Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
Explanation
Correct Answer
D:Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results. Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events. An auditor can trace a sampled claim to current repository settings and time-stamped governance evidence.
Incorrect Answers
A:Restrict public repository creation through supported governing policy and provide a controlled publication review. That change would leave the reported problem unresolved: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
B:Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance. That change would leave the reported problem unresolved: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
C:Limit bypass authority and require an approved accountable emergency pathway with post-event review. That change would leave the reported problem unresolved: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
Question 334
GitHub Enterprise administration scenario — Define accountable evidence for compliance reviews. In an enterprise development environment: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies 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.
- Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy.
- Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets.
- A simulated sensitive API action produces attributable retained evidence in the security monitoring destination.
- An auditor can trace a sampled claim to current repository settings and time-stamped governance evidence.
- Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events.
Explanation
Correct Answers
D:An auditor can trace a sampled claim to current repository settings and time-stamped governance evidence. Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events. Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone.
E:Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events. An auditor can trace a sampled claim to current repository settings and time-stamped governance evidence. Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
Incorrect Answers
A: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 compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events. An auditor can trace a sampled claim to current repository settings and time-stamped governance evidence.
B:Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets. It would not provide the evidence needed for the paired diagnosis and follow-up: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. Reconcile critical repository inventory, effective rulesets, scanning results and relevant policy-change events. An auditor can trace a sampled claim to current repository settings and time-stamped governance evidence.
C:A simulated sensitive API action produces attributable retained evidence in the security monitoring destination. It would not verify whether the proposed change works: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. An auditor can trace a sampled claim to current repository settings and time-stamped governance evidence. Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
Question 335
GitHub Enterprise administration scenario — Define accountable evidence for compliance reviews. In an enterprise development environment: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies 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.
- Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
- An auditor can trace a sampled claim to current repository settings and time-stamped governance evidence.
- Sample existing and new repositories have the required supported scanning controls or documented exceptions.
- Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance.
- Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone.
- Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
Explanation
Correct Answers
B:An auditor can trace a sampled claim to current repository settings and time-stamped governance evidence. Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results. Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone.
E:Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone. Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results. An auditor can trace a sampled claim to current repository settings and time-stamped governance evidence.
F:Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results. Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone. An auditor can trace a sampled claim to current repository settings and time-stamped governance evidence.
Incorrect Answers
A: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 compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone. Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
C:Sample existing and new repositories have the required supported scanning controls or documented exceptions. It would not independently demonstrate that the control works: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. An auditor can trace a sampled claim to current repository settings and time-stamped governance evidence. Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
D:Define maintained code-owner mappings for sensitive paths and require relevant reviews through branch governance. It does not implement the governing rule for this approval: A compliance team accepts a spreadsheet stating that every critical repository uses branch protection, although no machine-verifiable configuration evidence accompanies it. Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results. An auditor can trace a sampled claim to current repository settings and time-stamped governance evidence.
Question 336
GitHub Enterprise administration scenario — Approve a fine-grained personal access token request. In an enterprise development environment: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. 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.
- Commit identity assurance and independent code-review controls address different aspects of source integrity.
- Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.
- Fine-grained personal access and approval policies can limit an integration to the minimum required resources.
- Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access.
Explanation
Correct Answer
C:Fine-grained personal access and approval policies can limit an integration to the minimum required resources. Review the requested repository selection, granular permissions, account owner and organization token policy. Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request.
Incorrect Answers
A:Commit identity assurance and independent code-review controls address different aspects of source integrity. It does not govern the condition described: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. Fine-grained personal access and approval policies can limit an integration to the minimum required resources.
B:Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy. It does not govern the condition described: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. Fine-grained personal access and approval policies can limit an integration to the minimum required resources.
D:Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access. It does not govern the condition described: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. Fine-grained personal access and approval policies can limit an integration to the minimum required resources.
Question 337
GitHub Enterprise administration scenario — Approve a fine-grained personal access token request. In an enterprise development environment: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs.
- Review the documents' classification, enterprise audience permitted by internal visibility and alternative private access roles.
- Inspect the application's authorization flow, granted scopes or granular installation permissions, and its repository targets.
- Review the requested repository selection, granular permissions, account owner and organization token policy.
Explanation
Correct Answer
D:Review the requested repository selection, granular permissions, account owner and organization token policy. Fine-grained personal access and approval policies can limit an integration to the minimum required resources. Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request.
Incorrect Answers
A:Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs. That check would not establish the decisive facts for this condition: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. Review the requested repository selection, granular permissions, account owner and organization token policy.
B:Review the documents' classification, enterprise audience permitted by internal visibility and alternative private access roles. That check would not establish the decisive facts for this condition: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. Review the requested repository selection, granular permissions, account owner and organization token policy.
C:Inspect the application's authorization flow, granted scopes or granular installation permissions, and its repository targets. That check would not establish the decisive facts for this condition: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. Review the requested repository selection, granular permissions, account owner and organization token policy.
Question 338
GitHub Enterprise administration scenario — Approve a fine-grained personal access token request. In an enterprise development environment: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. 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.
- Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request.
- Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
- Require validated triage categories with documented revocation and exception decisions for exposed tokens.
- Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions.
Explanation
Correct Answer
A:Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request. Review the requested repository selection, granular permissions, account owner and organization token policy. The tool performs its required repository operation without reading unrelated repositories or changing organization settings.
Incorrect Answers
B:Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results. That change would leave the reported problem unresolved: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request.
C:Require validated triage categories with documented revocation and exception decisions for exposed tokens. That change would leave the reported problem unresolved: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request.
D:Enable a supported private vulnerability reporting pathway and publish clear responsible reporting instructions. That change would leave the reported problem unresolved: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request.
Question 339
GitHub Enterprise administration scenario — Approve a fine-grained personal access token request. In an enterprise development environment: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. 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.
- The job eventually completes within allowed API budgets without aggressive retry storms.
- Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception.
- Review the requested repository selection, granular permissions, account owner and organization token policy.
- The tool performs its required repository operation without reading unrelated repositories or changing organization settings.
- Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities.
Explanation
Correct Answers
C:Review the requested repository selection, granular permissions, account owner and organization token policy. The tool performs its required repository operation without reading unrelated repositories or changing organization settings. Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request.
D:The tool performs its required repository operation without reading unrelated repositories or changing organization settings. Review the requested repository selection, granular permissions, account owner and organization token policy. Fine-grained personal access and approval policies can limit an integration to the minimum required resources.
Incorrect Answers
A:The job eventually completes within allowed API budgets without aggressive retry storms. It would not verify whether the proposed change works: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. The tool performs its required repository operation without reading unrelated repositories or changing organization settings. Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request.
B:Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception. It would not provide the evidence needed for the paired diagnosis and follow-up: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. Review the requested repository selection, granular permissions, account owner and organization token policy. The tool performs its required repository operation without reading unrelated repositories or changing organization settings.
E:Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities. It would not provide the evidence needed for the paired diagnosis and follow-up: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. Review the requested repository selection, granular permissions, account owner and organization token policy. The tool performs its required repository operation without reading unrelated repositories or changing organization settings.
Question 340
GitHub Enterprise administration scenario — Approve a fine-grained personal access token request. In an enterprise development environment: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. 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.
- Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories.
- Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request.
- Limit bypass authority and require an approved accountable emergency pathway with post-event review.
- The tool performs its required repository operation without reading unrelated repositories or changing organization settings.
- Fine-grained personal access and approval policies can limit an integration to the minimum required resources.
- Every sampled alert has a defensible resolved status and still-active compromised credentials are revoked.
Explanation
Correct Answers
B:Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request. Fine-grained personal access and approval policies can limit an integration to the minimum required resources. The tool performs its required repository operation without reading unrelated repositories or changing organization settings.
D:The tool performs its required repository operation without reading unrelated repositories or changing organization settings. Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request. Fine-grained personal access and approval policies can limit an integration to the minimum required resources.
E:Fine-grained personal access and approval policies can limit an integration to the minimum required resources. Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request. The tool performs its required repository operation without reading unrelated repositories or changing organization settings.
Incorrect Answers
A:Dependency review during pull requests helps identify newly introduced package risk distinct from existing vulnerability inventories. It is not the rule that supports the proposed change and acceptance test: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. Fine-grained personal access and approval policies can limit an integration to the minimum required resources. Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request.
C:Limit bypass authority and require an approved accountable emergency pathway with post-event review. It does not implement the governing rule for this approval: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request. The tool performs its required repository operation without reading unrelated repositories or changing organization settings.
F:Every sampled alert has a defensible resolved status and still-active compromised credentials are revoked. It would not independently demonstrate that the control works: An external deployment tool requests an organization-wide classic token even though it needs write access to one selected repository. The tool performs its required repository operation without reading unrelated repositories or changing organization settings. Approve a supported narrowly scoped credential after functional testing or reject the unjustified broad request.