Microsoft GH-100 Practice Test 42
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.
Question 411
GitHub Enterprise administration scenario — Measure security alert remediation service levels. In an enterprise development environment: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. 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.
- Security logging coverage varies by audit method and event type, so detailed API request telemetry should be enabled deliberately where supported.
- Classic personal tokens may convey broader account-authorized scope than the specific automation requires.
- Enterprise security governance needs risk-tiered alert owners and observable remediation accountability.
- Untrusted fork code must not receive secrets or broad workflow privileges simply to perform tests.
Explanation
Correct Answer
C:Enterprise security governance needs risk-tiered alert owners and observable remediation accountability. Collect alert severity, exploitability, asset criticality, creation time and current assigned owner. Define and track risk-based remediation targets with approved escalation for overdue high-risk findings.
Incorrect Answers
A:Security logging coverage varies by audit method and event type, so detailed API request telemetry should be enabled deliberately where supported. It does not govern the condition described: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Enterprise security governance needs risk-tiered alert owners and observable remediation accountability.
B:Classic personal tokens may convey broader account-authorized scope than the specific automation requires. It does not govern the condition described: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Enterprise security governance needs risk-tiered alert owners and observable remediation accountability.
D:Untrusted fork code must not receive secrets or broad workflow privileges simply to perform tests. It does not govern the condition described: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Enterprise security governance needs risk-tiered alert owners and observable remediation accountability.
Question 412
GitHub Enterprise administration scenario — Measure security alert remediation service levels. In an enterprise development environment: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Review required events, streaming destination, service ownership, delivery health and external retention policy.
- Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets.
- Collect alert severity, exploitability, asset criticality, creation time and current assigned owner.
- Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps.
Explanation
Correct Answer
C:Collect alert severity, exploitability, asset criticality, creation time and current assigned owner. Enterprise security governance needs risk-tiered alert owners and observable remediation accountability. Define and track risk-based remediation targets with approved escalation for overdue high-risk findings.
Incorrect Answers
A:Review required events, streaming destination, service ownership, delivery health and external retention policy. That check would not establish the decisive facts for this condition: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Collect alert severity, exploitability, asset criticality, creation time and current assigned owner.
B:Compare the repository's CODEOWNERS coverage, protected paths and review requirements in active rulesets. That check would not establish the decisive facts for this condition: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Collect alert severity, exploitability, asset criticality, creation time and current assigned owner.
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: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Collect alert severity, exploitability, asset criticality, creation time and current assigned owner.
Question 413
GitHub Enterprise administration scenario — Measure security alert remediation service levels. In an enterprise development environment: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. The enterprise administrator needs a least-privilege corrective change with accountable approval and rollback. Which action BEST resolves the reported GitHub configuration or governance problem? Choose ONE best answer.
- Define and track risk-based remediation targets with approved escalation for overdue high-risk findings.
- Restrict public repository creation through supported governing policy and provide a controlled publication review.
- Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.
- Add appropriate code scanning status requirements through the owning organization ruleset with a carefully approved bypass process.
Explanation
Correct Answer
A:Define and track risk-based remediation targets with approved escalation for overdue high-risk findings. Collect alert severity, exploitability, asset criticality, creation time and current assigned owner. Critical alerts are assigned, evaluated and resolved or explicitly risk-accepted within defined review windows.
Incorrect Answers
B:Restrict public repository creation through supported governing policy and provide a controlled publication review. That change would leave the reported problem unresolved: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Define and track risk-based remediation targets with approved escalation for overdue high-risk findings.
C:Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement. That change would leave the reported problem unresolved: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Define and track risk-based remediation targets with approved escalation for overdue high-risk findings.
D:Add appropriate code scanning status requirements through the owning organization ruleset with a carefully approved bypass process. That change would leave the reported problem unresolved: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Define and track risk-based remediation targets with approved escalation for overdue high-risk findings.
Question 414
GitHub Enterprise administration scenario — Measure security alert remediation service levels. In an enterprise development environment: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. 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.
- Critical alerts are assigned, evaluated and resolved or explicitly risk-accepted within defined review windows.
- The user can complete required labeling without giving an untrusted extension access to confidential source.
- Assess the key identity, installed app permissions, issued token activity and supported key rotation window.
- Check the repository's private advisory facilities, downstream impact and the reporter's preferred disclosure channel.
- Collect alert severity, exploitability, asset criticality, creation time and current assigned owner.
Explanation
Correct Answers
A:Critical alerts are assigned, evaluated and resolved or explicitly risk-accepted within defined review windows. Collect alert severity, exploitability, asset criticality, creation time and current assigned owner. Enterprise security governance needs risk-tiered alert owners and observable remediation accountability.
E:Collect alert severity, exploitability, asset criticality, creation time and current assigned owner. Critical alerts are assigned, evaluated and resolved or explicitly risk-accepted within defined review windows. Define and track risk-based remediation targets with approved escalation for overdue high-risk findings.
Incorrect Answers
B:The user can complete required labeling without giving an untrusted extension access to confidential source. It would not verify whether the proposed change works: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Critical alerts are assigned, evaluated and resolved or explicitly risk-accepted within defined review windows. Define and track risk-based remediation targets with approved escalation for overdue high-risk findings.
C:Assess the key identity, installed app permissions, issued token activity and supported key rotation window. It would not provide the evidence needed for the paired diagnosis and follow-up: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Collect alert severity, exploitability, asset criticality, creation time and current assigned owner. Critical alerts are assigned, evaluated and resolved or explicitly risk-accepted within defined review windows.
D: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: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Collect alert severity, exploitability, asset criticality, creation time and current assigned owner. Critical alerts are assigned, evaluated and resolved or explicitly risk-accepted within defined review windows.
Question 415
GitHub Enterprise administration scenario — Measure security alert remediation service levels. In an enterprise development environment: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. 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.
- Critical alerts are assigned, evaluated and resolved or explicitly risk-accepted within defined review windows.
- Enterprise security governance needs risk-tiered alert owners and observable remediation accountability.
- Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
- Define and track risk-based remediation targets with approved escalation for overdue high-risk findings.
- A sampled organization policy event arrives with actor and time fields and remains queryable under the approved retention policy.
- Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.
Explanation
Correct Answers
A:Critical alerts are assigned, evaluated and resolved or explicitly risk-accepted within defined review windows. Define and track risk-based remediation targets with approved escalation for overdue high-risk findings. Enterprise security governance needs risk-tiered alert owners and observable remediation accountability.
B:Enterprise security governance needs risk-tiered alert owners and observable remediation accountability. Define and track risk-based remediation targets with approved escalation for overdue high-risk findings. Critical alerts are assigned, evaluated and resolved or explicitly risk-accepted within defined review windows.
D:Define and track risk-based remediation targets with approved escalation for overdue high-risk findings. Enterprise security governance needs risk-tiered alert owners and observable remediation accountability. Critical alerts are assigned, evaluated and resolved or explicitly risk-accepted within defined review windows.
Incorrect Answers
C: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: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Enterprise security governance needs risk-tiered alert owners and observable remediation accountability. Define and track risk-based remediation targets with approved escalation for overdue high-risk findings.
E: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: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Critical alerts are assigned, evaluated and resolved or explicitly risk-accepted within defined review windows. Define and track risk-based remediation targets with approved escalation for overdue high-risk findings.
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: The security dashboard contains aging Dependabot and secret scanning findings, but no team owns response deadlines. Define and track risk-based remediation targets with approved escalation for overdue high-risk findings. Critical alerts are assigned, evaluated and resolved or explicitly risk-accepted within defined review windows.
Question 416
GitHub Enterprise administration scenario — Block unintended public repository creation. In an enterprise development environment: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. 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.
- Complex CodeQL environments may need advanced workflow setup to analyze the actual compiled or interpreted application correctly.
- Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone.
- Untrusted fork code must not receive secrets or broad workflow privileges simply to perform tests.
- Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance.
Explanation
Correct Answer
D:Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance. Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options. Restrict public repository creation through supported governing policy and provide a controlled publication review.
Incorrect Answers
A:Complex CodeQL environments may need advanced workflow setup to analyze the actual compiled or interpreted application correctly. It does not govern the condition described: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance.
B:Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone. It does not govern the condition described: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance.
C:Untrusted fork code must not receive secrets or broad workflow privileges simply to perform tests. It does not govern the condition described: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance.
Question 417
GitHub Enterprise administration scenario — Block unintended public repository creation. In an enterprise development environment: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Compare current token ownership, required API endpoints, repository selection and supported GitHub App permission model.
- Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options.
- Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage.
- Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations.
Explanation
Correct Answer
B:Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options. Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance. Restrict public repository creation through supported governing policy and provide a controlled publication review.
Incorrect Answers
A:Compare current token ownership, required API endpoints, repository selection and supported GitHub App permission model. That check would not establish the decisive facts for this condition: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options.
C: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 corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options.
D:Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations. That check would not establish the decisive facts for this condition: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options.
Question 418
GitHub Enterprise administration scenario — Block unintended public repository creation. In an enterprise development environment: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. 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 a supported dependency review check to protected pull request workflows with risk-appropriate enforcement.
- Fix dependency graph inputs or supported submission process and retest the nested component.
- Restrict public repository creation through supported governing policy and provide a controlled publication review.
- Limit bypass authority and require an approved accountable emergency pathway with post-event review.
Explanation
Correct Answer
C:Restrict public repository creation through supported governing policy and provide a controlled publication review. Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options. An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route.
Incorrect Answers
A:Add a supported dependency review check to protected pull request workflows with risk-appropriate enforcement. That change would leave the reported problem unresolved: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. Restrict public repository creation through supported governing policy and provide a controlled publication review.
B:Fix dependency graph inputs or supported submission process and retest the nested component. That change would leave the reported problem unresolved: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. Restrict public repository creation through supported governing policy and provide a controlled publication review.
D:Limit bypass authority and require an approved accountable emergency pathway with post-event review. That change would leave the reported problem unresolved: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. Restrict public repository creation through supported governing policy and provide a controlled publication review.
Question 419
GitHub Enterprise administration scenario — Block unintended public repository creation. In an enterprise development environment: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. 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.
- Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance.
- Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options.
- An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route.
- A test installation token signed through the new approved key works and the compromised key is unusable.
- Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs.
Explanation
Correct Answers
B:Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options. An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route. Restrict public repository creation through supported governing policy and provide a controlled publication review.
C:An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route. Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options. Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance.
Incorrect Answers
A:Review secret scanning eligibility, push protection policy, historical alert patterns and bypass governance. It would not provide the evidence needed for the paired diagnosis and follow-up: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options. An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route.
D:A test installation token signed through the new approved key works and the compromised key is unusable. It would not verify whether the proposed change works: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route. Restrict public repository creation through supported governing policy and provide a controlled publication review.
E:Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs. It would not provide the evidence needed for the paired diagnosis and follow-up: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options. An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route.
Question 420
GitHub Enterprise administration scenario — Block unintended public repository creation. In an enterprise development environment: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. 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.
- An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route.
- A pull request adding a known-risk dependency is flagged before merge while safe updates pass.
- Security logging coverage varies by audit method and event type, so detailed API request telemetry should be enabled deliberately where supported.
- Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance.
- Restrict public repository creation through supported governing policy and provide a controlled publication review.
- Add appropriate code scanning status requirements through the owning organization ruleset with a carefully approved bypass process.
Explanation
Correct Answers
A:An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route. Restrict public repository creation through supported governing policy and provide a controlled publication review. Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance.
D:Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance. Restrict public repository creation through supported governing policy and provide a controlled publication review. An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route.
E:Restrict public repository creation through supported governing policy and provide a controlled publication review. Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance. An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route.
Incorrect Answers
B:A pull request adding a known-risk dependency is flagged before merge while safe updates pass. It would not independently demonstrate that the control works: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route. Restrict public repository creation through supported governing policy and provide a controlled publication review.
C:Security logging coverage varies by audit method and event type, so detailed API request telemetry should be enabled deliberately where supported. It is not the rule that supports the proposed change and acceptance test: A corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance. Restrict public repository creation through supported governing policy and provide a controlled publication review.
F: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 corporate organization has a confidential source policy, but a newly onboarded engineer can still create public repositories under the organization. Restrict public repository creation through supported governing policy and provide a controlled publication review. An ordinary member cannot create an unreviewed public repository, while approved open-source releases use a documented route.