Microsoft GH-100 Practice Test 41
Question 400
GitHub Enterprise administration scenario — Restore missing dependency graph coverage. In an enterprise development environment: A repository has language-specific manifests but security reports show no dependency inventory for a critical component in its nested workspace. 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.
- Dependency graph completeness depends on supported manifests and any required submission or extraction configuration.
- Add appropriate code scanning status requirements through the owning organization ruleset with a carefully approved bypass process.
- The missing dependency is inventoried and a known vulnerable sample generates appropriate reviewable findings.
- Repository visibility settings define different reader populations and must be evaluated against data classification.
- Fix dependency graph inputs or supported submission process and retest the nested component.
Explanation
Correct Answers
B:Dependency graph completeness depends on supported manifests and any required submission or extraction configuration. Fix dependency graph inputs or supported submission process and retest the nested component. The missing dependency is inventoried and a known vulnerable sample generates appropriate reviewable findings.
D:The missing dependency is inventoried and a known vulnerable sample generates appropriate reviewable findings. Fix dependency graph inputs or supported submission process and retest the nested component. Dependency graph completeness depends on supported manifests and any required submission or extraction configuration.
F:Fix dependency graph inputs or supported submission process and retest the nested component. Dependency graph completeness depends on supported manifests and any required submission or extraction configuration. The missing dependency is inventoried and a known vulnerable sample generates appropriate reviewable findings.
Incorrect Answers
A:The audit sample demonstrates required controls for every selected organization or records justified deviations. It would not independently demonstrate that the control works: A repository has language-specific manifests but security reports show no dependency inventory for a critical component in its nested workspace. The missing dependency is inventoried and a known vulnerable sample generates appropriate reviewable findings. Fix dependency graph inputs or supported submission process and retest the nested component.
C:Add appropriate code scanning status requirements through the owning organization ruleset with a carefully approved bypass process. It does not implement the governing rule for this approval: A repository has language-specific manifests but security reports show no dependency inventory for a critical component in its nested workspace. Fix dependency graph inputs or supported submission process and retest the nested component. The missing dependency is inventoried and a known vulnerable sample generates appropriate reviewable findings.
E:Repository visibility settings define different reader populations and must be evaluated against data classification. It is not the rule that supports the proposed change and acceptance test: A repository has language-specific manifests but security reports show no dependency inventory for a critical component in its nested workspace. Dependency graph completeness depends on supported manifests and any required submission or extraction configuration. Fix dependency graph inputs or supported submission process and retest the nested component.
Question 401
GitHub Enterprise administration scenario — Troubleshoot a CodeQL database build failure. In an enterprise development environment: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. 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.
- Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls.
- Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure.
- Fine-grained personal access and approval policies can limit an integration to the minimum required resources.
- Successful scheduling is not evidence that compiled-language analysis completed successfully.
Explanation
Correct Answer
D:Successful scheduling is not evidence that compiled-language analysis completed successfully. Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps. Correct the authorized build environment for the analysis job and rerun full relevant coverage.
Incorrect Answers
A:Rulesets targeting branches and tags should align with the organization's required supply-chain integrity controls. It does not govern the condition described: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. Successful scheduling is not evidence that compiled-language analysis completed successfully.
B:Secure reporting channels help researchers share vulnerabilities with maintainers without unnecessary pre-fix disclosure. It does not govern the condition described: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. Successful scheduling is not evidence that compiled-language analysis completed successfully.
C:Fine-grained personal access and approval policies can limit an integration to the minimum required resources. It does not govern the condition described: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. Successful scheduling is not evidence that compiled-language analysis completed successfully.
Question 402
GitHub Enterprise administration scenario — Troubleshoot a CodeQL database build failure. In an enterprise development environment: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect the application's authorization flow, granted scopes or granular installation permissions, and its repository targets.
- Check the repository's private advisory facilities, downstream impact and the reporter's preferred disclosure channel.
- Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps.
- Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations.
Explanation
Correct Answer
C:Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps. Successful scheduling is not evidence that compiled-language analysis completed successfully. Correct the authorized build environment for the analysis job and rerun full relevant coverage.
Incorrect Answers
A: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: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps.
B:Check the repository's private advisory facilities, downstream impact and the reporter's preferred disclosure channel. That check would not establish the decisive facts for this condition: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps.
D:Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations. That check would not establish the decisive facts for this condition: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps.
Question 403
GitHub Enterprise administration scenario — Troubleshoot a CodeQL database build failure. In an enterprise development environment: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. 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 push protection and establish a documented response for verified false positives and genuine exposures.
- Correct the authorized build environment for the analysis job and rerun full relevant coverage.
- Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token.
- Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.
Explanation
Correct Answer
B:Correct the authorized build environment for the analysis job and rerun full relevant coverage. Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps. The security analysis produces a valid database and findings for the intended compiled component.
Incorrect Answers
A:Enable supported push protection and establish a documented response for verified false positives and genuine exposures. That change would leave the reported problem unresolved: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. Correct the authorized build environment for the analysis job and rerun full relevant coverage.
C:Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token. That change would leave the reported problem unresolved: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. Correct the authorized build environment for the analysis job and rerun full relevant coverage.
D:Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement. That change would leave the reported problem unresolved: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. Correct the authorized build environment for the analysis job and rerun full relevant coverage.
Question 404
GitHub Enterprise administration scenario — Troubleshoot a CodeQL database build failure. In an enterprise development environment: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. 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 integration continues after the creator is offboarded and only its installed repositories are reachable.
- Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps.
- Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy.
- The security analysis produces a valid database and findings for the intended compiled component.
- Check the bypass actor list, effective enforcement mode, branch history and the business need for an exception.
Explanation
Correct Answers
B:Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps. The security analysis produces a valid database and findings for the intended compiled component. Correct the authorized build environment for the analysis job and rerun full relevant coverage.
D:The security analysis produces a valid database and findings for the intended compiled component. Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps. Successful scheduling is not evidence that compiled-language analysis completed successfully.
Incorrect Answers
A:The integration continues after the creator is offboarded and only its installed repositories are reachable. It would not verify whether the proposed change works: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. The security analysis produces a valid database and findings for the intended compiled component. Correct the authorized build environment for the analysis job and rerun full relevant coverage.
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: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps. The security analysis produces a valid database and findings for the intended compiled component.
E: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: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps. The security analysis produces a valid database and findings for the intended compiled component.
Question 405
GitHub Enterprise administration scenario — Troubleshoot a CodeQL database build failure. In an enterprise development environment: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. 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.
- Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token.
- Correct the authorized build environment for the analysis job and rerun full relevant coverage.
- The security analysis produces a valid database and findings for the intended compiled component.
- Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats.
- The integration accesses only approved resources and its permission grant can be independently reviewed and revoked.
- Successful scheduling is not evidence that compiled-language analysis completed successfully.
Explanation
Correct Answers
B:Correct the authorized build environment for the analysis job and rerun full relevant coverage. Successful scheduling is not evidence that compiled-language analysis completed successfully. The security analysis produces a valid database and findings for the intended compiled component.
C:The security analysis produces a valid database and findings for the intended compiled component. Correct the authorized build environment for the analysis job and rerun full relevant coverage. Successful scheduling is not evidence that compiled-language analysis completed successfully.
F:Successful scheduling is not evidence that compiled-language analysis completed successfully. Correct the authorized build environment for the analysis job and rerun full relevant coverage. The security analysis produces a valid database and findings for the intended compiled component.
Incorrect Answers
A:Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token. It does not implement the governing rule for this approval: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. Correct the authorized build environment for the analysis job and rerun full relevant coverage. The security analysis produces a valid database and findings for the intended compiled component.
D:Custom secret patterns can extend supported scanning coverage for well-defined proprietary credential formats. It is not the rule that supports the proposed change and acceptance test: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. Successful scheduling is not evidence that compiled-language analysis completed successfully. Correct the authorized build environment for the analysis job and rerun full relevant coverage.
E:The integration accesses only approved resources and its permission grant can be independently reviewed and revoked. It would not independently demonstrate that the control works: CodeQL workflow jobs run but produce no useful results because a C++ component's generated build files are absent on the hosted runner. The security analysis produces a valid database and findings for the intended compiled component. Correct the authorized build environment for the analysis job and rerun full relevant coverage.
Question 406
GitHub Enterprise administration scenario — Govern false-positive code scanning dismissals. In an enterprise development environment: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. 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.
- Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.
- Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite.
- Dependency graph completeness depends on supported manifests and any required submission or extraction configuration.
- Enterprise security governance needs risk-tiered alert owners and observable remediation accountability.
Explanation
Correct Answer
B:Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite. Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy. Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate.
Incorrect Answers
A:Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy. It does not govern the condition described: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite.
C:Dependency graph completeness depends on supported manifests and any required submission or extraction configuration. It does not govern the condition described: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite.
D:Enterprise security governance needs risk-tiered alert owners and observable remediation accountability. It does not govern the condition described: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite.
Question 407
GitHub Enterprise administration scenario — Govern false-positive code scanning dismissals. In an enterprise development environment: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy.
- Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations.
- Inspect current grants, audit events, accepted invitations and documented vendor authorization before changing global policy.
- Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs.
Explanation
Correct Answer
A:Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy. Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite. Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate.
Incorrect Answers
B:Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations. That check would not establish the decisive facts for this condition: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy.
C: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 team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy.
D: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 team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy.
Question 408
GitHub Enterprise administration scenario — Govern false-positive code scanning dismissals. In an enterprise development environment: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. 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.
- Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate.
- Enable supported push protection and establish a documented response for verified false positives and genuine exposures.
- Enable supported API request audit streaming and correlated source IP evidence with privacy approvals and health checks.
- Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token.
Explanation
Correct Answer
A:Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate. Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy. Sampled dismissed alerts include defensible evidence and actionable findings remain tracked to resolution.
Incorrect Answers
B:Enable supported push protection and establish a documented response for verified false positives and genuine exposures. That change would leave the reported problem unresolved: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate.
C:Enable supported API request audit streaming and correlated source IP evidence with privacy approvals and health checks. That change would leave the reported problem unresolved: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate.
D:Migrate to a limited-permission GitHub App or supported fine-grained token and revoke the obsolete broad token. That change would leave the reported problem unresolved: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate.
Question 409
GitHub Enterprise administration scenario — Govern false-positive code scanning dismissals. In an enterprise development environment: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. 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.
- CodeQL successfully analyzes the intended modules and results appear under the correct repository security context.
- Sampled dismissed alerts include defensible evidence and actionable findings remain tracked to resolution.
- Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps.
- Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy.
- Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status.
Explanation
Correct Answers
B:Sampled dismissed alerts include defensible evidence and actionable findings remain tracked to resolution. Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy. Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite.
D:Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy. Sampled dismissed alerts include defensible evidence and actionable findings remain tracked to resolution. Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate.
Incorrect Answers
A:CodeQL successfully analyzes the intended modules and results appear under the correct repository security context. It would not verify whether the proposed change works: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Sampled dismissed alerts include defensible evidence and actionable findings remain tracked to resolution. Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate.
C:Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps. It would not provide the evidence needed for the paired diagnosis and follow-up: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy. Sampled dismissed alerts include defensible evidence and actionable findings remain tracked to resolution.
E:Inspect repository security settings, detected languages, existing CodeQL workflows and recent analysis status. It would not provide the evidence needed for the paired diagnosis and follow-up: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy. Sampled dismissed alerts include defensible evidence and actionable findings remain tracked to resolution.
Question 410
GitHub Enterprise administration scenario — Govern false-positive code scanning dismissals. In an enterprise development environment: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. 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.
- Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate.
- A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy.
- Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite.
- Sampled dismissed alerts include defensible evidence and actionable findings remain tracked to resolution.
- Compliance evidence should establish effective control coverage across the actual governed scope, not only the intended policy.
- Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.
Explanation
Correct Answers
A:Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate. Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite. Sampled dismissed alerts include defensible evidence and actionable findings remain tracked to resolution.
C:Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite. Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate. Sampled dismissed alerts include defensible evidence and actionable findings remain tracked to resolution.
D:Sampled dismissed alerts include defensible evidence and actionable findings remain tracked to resolution. Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate. Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite.
Incorrect Answers
B:A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy. It would not independently demonstrate that the control works: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Sampled dismissed alerts include defensible evidence and actionable findings remain tracked to resolution. Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate.
E:Compliance evidence should establish effective control coverage across the actual governed scope, not only the intended policy. It is not the rule that supports the proposed change and acceptance test: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite. Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate.
F: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: A team dismisses high-severity CodeQL alerts with no justification because its release deadline is tomorrow. Require an accountable risk or false-positive decision with a documented explanation and future review where appropriate. Sampled dismissed alerts include defensible evidence and actionable findings remain tracked to resolution.