Microsoft GH-100 Practice Test 35
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.
Question 341
GitHub Enterprise administration scenario — Reduce classic personal access token exposure. In an enterprise development environment: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. 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.
- API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance.
- Classic personal tokens may convey broader account-authorized scope than the specific automation requires.
- Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access.
- Automated security update pull requests support remediation but must still pass review, compatibility and CI checks.
Explanation
Correct Answer
B:Classic personal tokens may convey broader account-authorized scope than the specific automation requires. Inspect token type, granted scopes, usage age, the user's effective rights and supported alternative app credentials. Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token.
Incorrect Answers
A:API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance. It does not govern the condition described: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. Classic personal tokens may convey broader account-authorized scope than the specific automation requires.
C:Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access. It does not govern the condition described: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. Classic personal tokens may convey broader account-authorized scope than the specific automation requires.
D:Automated security update pull requests support remediation but must still pass review, compatibility and CI checks. It does not govern the condition described: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. Classic personal tokens may convey broader account-authorized scope than the specific automation requires.
Question 342
GitHub Enterprise administration scenario — Reduce classic personal access token exposure. In an enterprise development environment: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect the active branch rulesets, required tools, alert thresholds and the checkout of the merge commit.
- Assess the key identity, installed app permissions, issued token activity and supported key rotation window.
- Inspect token type, granted scopes, usage age, the user's effective rights and supported alternative app credentials.
- Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage.
Explanation
Correct Answer
C:Inspect token type, granted scopes, usage age, the user's effective rights and supported alternative app credentials. Classic personal tokens may convey broader account-authorized scope than the specific automation requires. Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token.
Incorrect Answers
A:Inspect the active branch rulesets, required tools, alert thresholds and the checkout of the merge commit. That check would not establish the decisive facts for this condition: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. Inspect token type, granted scopes, usage age, the user's effective rights and supported alternative app credentials.
B:Assess the key identity, installed app permissions, issued token activity and supported key rotation window. That check would not establish the decisive facts for this condition: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. Inspect token type, granted scopes, usage age, the user's effective rights and supported alternative app credentials.
D:Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage. That check would not establish the decisive facts for this condition: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. Inspect token type, granted scopes, usage age, the user's effective rights and supported alternative app credentials.
Question 343
GitHub Enterprise administration scenario — Reduce classic personal access token exposure. In an enterprise development environment: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. 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.
- Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures.
- Enable appropriate external collection before incidents and document search sources by event type.
- Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries.
- Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token.
Explanation
Correct Answer
D:Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token. Inspect token type, granted scopes, usage age, the user's effective rights and supported alternative app credentials. The inventory job succeeds with limited rights and the old credential is rejected after revocation.
Incorrect Answers
A:Add appropriate protected tag and branch rules with controlled release authority and break-glass procedures. That change would leave the reported problem unresolved: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token.
B:Enable appropriate external collection before incidents and document search sources by event type. That change would leave the reported problem unresolved: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token.
C:Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries. That change would leave the reported problem unresolved: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token.
Question 344
GitHub Enterprise administration scenario — Reduce classic personal access token exposure. In an enterprise development environment: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. 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.
- Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.
- Inspect token type, granted scopes, usage age, the user's effective rights and supported alternative app credentials.
- The inventory job succeeds with limited rights and the old credential is rejected after revocation.
- Review the app manifest permissions, selected repositories and the organization policy controlling installations.
- Check the repository's private advisory facilities, downstream impact and the reporter's preferred disclosure channel.
Explanation
Correct Answers
B:Inspect token type, granted scopes, usage age, the user's effective rights and supported alternative app credentials. The inventory job succeeds with limited rights and the old credential is rejected after revocation. Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token.
C:The inventory job succeeds with limited rights and the old credential is rejected after revocation. Inspect token type, granted scopes, usage age, the user's effective rights and supported alternative app credentials. Classic personal tokens may convey broader account-authorized scope than the specific automation requires.
Incorrect Answers
A:Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits. It would not verify whether the proposed change works: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. The inventory job succeeds with limited rights and the old credential is rejected after revocation. Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token.
D:Review the app manifest permissions, selected repositories and the organization policy controlling installations. It would not provide the evidence needed for the paired diagnosis and follow-up: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. Inspect token type, granted scopes, usage age, the user's effective rights and supported alternative app credentials. The inventory job succeeds with limited rights and the old credential is rejected after revocation.
E:Check the repository's private advisory facilities, downstream impact and the reporter's preferred disclosure channel. It would not provide the evidence needed for the paired diagnosis and follow-up: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. Inspect token type, granted scopes, usage age, the user's effective rights and supported alternative app credentials. The inventory job succeeds with limited rights and the old credential is rejected after revocation.
Question 345
GitHub Enterprise administration scenario — Reduce classic personal access token exposure. In an enterprise development environment: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. 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.
- Move the classified content into a private repository with explicit reviewed team access and retention safeguards.
- Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token.
- Classic personal tokens may convey broader account-authorized scope than the specific automation requires.
- Fine-grained personal access and approval policies can limit an integration to the minimum required resources.
- A fork PR can run safe checks but cannot access production deployment credentials.
- The inventory job succeeds with limited rights and the old credential is rejected after revocation.
Explanation
Correct Answers
B:Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token. Classic personal tokens may convey broader account-authorized scope than the specific automation requires. The inventory job succeeds with limited rights and the old credential is rejected after revocation.
C:Classic personal tokens may convey broader account-authorized scope than the specific automation requires. Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token. The inventory job succeeds with limited rights and the old credential is rejected after revocation.
F:The inventory job succeeds with limited rights and the old credential is rejected after revocation. Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token. Classic personal tokens may convey broader account-authorized scope than the specific automation requires.
Incorrect Answers
A:Move the classified content into a private repository with explicit reviewed team access and retention safeguards. It does not implement the governing rule for this approval: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token. The inventory job succeeds with limited rights and the old credential is rejected after revocation.
D:Fine-grained personal access and approval policies can limit an integration to the minimum required resources. It is not the rule that supports the proposed change and acceptance test: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. Classic personal tokens may convey broader account-authorized scope than the specific automation requires. Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token.
E:A fork PR can run safe checks but cannot access production deployment credentials. It would not independently demonstrate that the control works: A long-running automation uses a classic personal access token with broad repository and administrative scope for a read-only inventory job. The inventory job succeeds with limited rights and the old credential is rejected after revocation. Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token.
Question 346
GitHub Enterprise administration scenario — Honor SAML restrictions for token-based access. In an enterprise development environment: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. 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.
- App-based installation identity separates automated service authorization from individual employee lifecycle while supporting scoped permissions.
- Public exposure and historical clones require incident scoping beyond a later repository visibility change.
- SAML-protected resources can require token authorization independent of interactive account sign-in.
- GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary.
Explanation
Correct Answer
C:SAML-protected resources can require token authorization independent of interactive account sign-in. Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs. Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight.
Incorrect Answers
A:App-based installation identity separates automated service authorization from individual employee lifecycle while supporting scoped permissions. It does not govern the condition described: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. SAML-protected resources can require token authorization independent of interactive account sign-in.
B:Public exposure and historical clones require incident scoping beyond a later repository visibility change. It does not govern the condition described: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. SAML-protected resources can require token authorization independent of interactive account sign-in.
D:GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary. It does not govern the condition described: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. SAML-protected resources can require token authorization independent of interactive account sign-in.
Question 347
GitHub Enterprise administration scenario — Honor SAML restrictions for token-based access. In an enterprise development environment: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs.
- Inspect the active branch rulesets, required tools, alert thresholds and the checkout of the merge commit.
- Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy.
- Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps.
Explanation
Correct Answer
A:Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs. SAML-protected resources can require token authorization independent of interactive account sign-in. Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight.
Incorrect Answers
B:Inspect the active branch rulesets, required tools, alert thresholds and the checkout of the merge commit. That check would not establish the decisive facts for this condition: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs.
C:Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy. That check would not establish the decisive facts for this condition: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs.
D:Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps. That check would not establish the decisive facts for this condition: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs.
Question 348
GitHub Enterprise administration scenario — Honor SAML restrictions for token-based access. In an enterprise development environment: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. 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.
- Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight.
- Produce a repeatable cross-organization effective-control report and assign remediation to owners of exceptions.
- Restrict public repository creation through supported governing policy and provide a controlled publication review.
- Enable supported security update pull requests with owned reviewers and controlled merge rules.
Explanation
Correct Answer
A:Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight. Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs. Only the intended integration gains API access to its approved repositories and failure logs show no remaining SSO block.
Incorrect Answers
B:Produce a repeatable cross-organization effective-control report and assign remediation to owners of exceptions. That change would leave the reported problem unresolved: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight.
C:Restrict public repository creation through supported governing policy and provide a controlled publication review. That change would leave the reported problem unresolved: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight.
D:Enable supported security update pull requests with owned reviewers and controlled merge rules. That change would leave the reported problem unresolved: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight.
Question 349
GitHub Enterprise administration scenario — Honor SAML restrictions for token-based access. In an enterprise development environment: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. 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 user can complete required labeling without giving an untrusted extension access to confidential source.
- Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs.
- Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies.
- Only the intended integration gains API access to its approved repositories and failure logs show no remaining SSO block.
- Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage.
Explanation
Correct Answers
B:Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs. Only the intended integration gains API access to its approved repositories and failure logs show no remaining SSO block. Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight.
D:Only the intended integration gains API access to its approved repositories and failure logs show no remaining SSO block. Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs. SAML-protected resources can require token authorization independent of interactive account sign-in.
Incorrect Answers
A:The user can complete required labeling without giving an untrusted extension access to confidential source. It would not verify whether the proposed change works: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. Only the intended integration gains API access to its approved repositories and failure logs show no remaining SSO block. Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight.
C:Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies. It would not provide the evidence needed for the paired diagnosis and follow-up: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs. Only the intended integration gains API access to its approved repositories and failure logs show no remaining SSO block.
E: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: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs. Only the intended integration gains API access to its approved repositories and failure logs show no remaining SSO block.
Question 350
GitHub Enterprise administration scenario — Honor SAML restrictions for token-based access. In an enterprise development environment: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. 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.
- Only the intended integration gains API access to its approved repositories and failure logs show no remaining SSO block.
- SAML-protected resources can require token authorization independent of interactive account sign-in.
- Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.
- Git and other audit event types have different availability windows, so required forensic data must be retained proactively.
- Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight.
- CodeQL successfully analyzes the intended modules and results appear under the correct repository security context.
Explanation
Correct Answers
A:Only the intended integration gains API access to its approved repositories and failure logs show no remaining SSO block. Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight. SAML-protected resources can require token authorization independent of interactive account sign-in.
B:SAML-protected resources can require token authorization independent of interactive account sign-in. Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight. Only the intended integration gains API access to its approved repositories and failure logs show no remaining SSO block.
E:Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight. SAML-protected resources can require token authorization independent of interactive account sign-in. Only the intended integration gains API access to its approved repositories and failure logs show no remaining SSO block.
Incorrect Answers
C:Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process. It does not implement the governing rule for this approval: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight. Only the intended integration gains API access to its approved repositories and failure logs show no remaining SSO block.
D:Git and other audit event types have different availability windows, so required forensic data must be retained proactively. It is not the rule that supports the proposed change and acceptance test: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. SAML-protected resources can require token authorization independent of interactive account sign-in. Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight.
F:CodeQL successfully analyzes the intended modules and results appear under the correct repository security context. It would not independently demonstrate that the control works: An integration repeatedly receives a repository authorization failure although its user's personal account is enrolled and SSO works in a web browser. Only the intended integration gains API access to its approved repositories and failure logs show no remaining SSO block. Authorize a supported narrow credential for the correct SAML-protected organization with owner oversight.