Microsoft GH-900 Practice Test 64
Question 630
An organization wants to identify the least appropriate response to this event: A security analyst investigates a recent organization role adjustment but relies on vague recollections from team chat. Which proposed response would create the clearest avoidable risk here? Select ONE answer.
- Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.
- Delete review records and assume repository commit history captures every organization security-setting change.
- Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements.
- Set and verify repository visibility to match the actual intended audience and hosting plan capabilities.
Explanation
Correct Answer
B:Delete review records and assume repository commit history captures every organization security-setting change. Objective closure would show that the team can attribute the recorded administrative event and determine whether it matched an approved change request. The unsafe proposal is to delete review records and assume repository commit history captures every organization security-setting change. A security analyst investigates a recent organization role adjustment but relies on vague recollections from team chat.
Incorrect Answers
A:Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch. Objective closure would show that the team can attribute the recorded administrative event and determine whether it matched an approved change request. The direct risk in the case is audit logs support administrative investigation, not this other concern.
C:Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements. Objective closure would show that the team can attribute the recorded administrative event and determine whether it matched an approved change request. The direct risk in the case is audit logs support administrative investigation, not this other concern.
D:Set and verify repository visibility to match the actual intended audience and hosting plan capabilities. Objective closure would show that the team can attribute the recorded administrative event and determine whether it matched an approved change request. The direct risk in the case is audit logs support administrative investigation, not this other concern.
Question 631
A contributor receives this specific collaboration request: A developer accidentally adds an API credential to a commit and assumes its deletion from the latest file makes the secret safe. Which controlled GitHub workflow action is most appropriate here? Select ONE best answer.
- Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.
- Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors.
- Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure.
- Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.
Explanation
Correct Answer
C:Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. The first useful confirmation step is to inspect the reported secret location, exposure context and current token status without copying secrets into new logs.
Incorrect Answers
A:Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing. Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. The case instead calls for the following: revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure.
B:Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors. Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. The case instead calls for the following: revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure.
D:Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan. Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. The case instead calls for the following: revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure.
Question 632
An engineer needs to distinguish root causes for the following workflow problem: A developer accidentally adds an API credential to a commit and assumes its deletion from the latest file makes the secret safe. Which check best distinguishes the actual cause from a different GitHub issue? Select ONE answer.
- Inspect effective ruleset targets, enforcement state and bypass permissions before assuming a rule applies.
- Inspect current visibility and effective account permissions before publishing sensitive content.
- Inspect the enterprise account type and identity provisioning configuration before proposing an access migration.
- Inspect the reported secret location, exposure context and current token status without copying secrets into new logs.
Explanation
Correct Answer
D:Inspect the reported secret location, exposure context and current token status without copying secrets into new logs. If the check supports this diagnosis, the next controlled response is to revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. Verify the improvement by checking that the compromised credential is no longer usable and relevant repository protection alerts are addressed.
Incorrect Answers
A:Inspect effective ruleset targets, enforcement state and bypass permissions before assuming a rule applies. If the check supports this diagnosis, the next controlled response is to revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. It does not isolate the secret scanning and push protection respond to leaks issue described.
B:Inspect current visibility and effective account permissions before publishing sensitive content. If the check supports this diagnosis, the next controlled response is to revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. It does not isolate the secret scanning and push protection respond to leaks issue described.
C:Inspect the enterprise account type and identity provisioning configuration before proposing an access migration. If the check supports this diagnosis, the next controlled response is to revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. It does not isolate the secret scanning and push protection respond to leaks issue described.
Question 633
A repository owner asks for objective proof that this issue is fixed: A developer accidentally adds an API credential to a commit and assumes its deletion from the latest file makes the secret safe. Which verifiable state directly confirms successful remediation? Select ONE answer.
- The compromised credential is no longer usable and relevant repository protection alerts are addressed.
- The account can authenticate through the supported passkey flow without revealing a reusable password to a phishing page.
- The intended authorized API call succeeds while unrelated repositories and privileged operations remain inaccessible.
- The contributor can perform required tasks without unwanted authority to change sensitive settings.
Explanation
Correct Answer
A:The compromised credential is no longer usable and relevant repository protection alerts are addressed. Closing an issue without this result would not prove technical resolution because Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. An independent review should first inspect the reported secret location, exposure context and current token status without copying secrets into new logs.
Incorrect Answers
B:The account can authenticate through the supported passkey flow without revealing a reusable password to a phishing page. Closing an issue without this result would not prove technical resolution because Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. This validates an adjacent control rather than the outcome of secret scanning and push protection respond to leaks.
C:The intended authorized API call succeeds while unrelated repositories and privileged operations remain inaccessible. Closing an issue without this result would not prove technical resolution because Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. This validates an adjacent control rather than the outcome of secret scanning and push protection respond to leaks.
D:The contributor can perform required tasks without unwanted authority to change sensitive settings. Closing an issue without this result would not prove technical resolution because Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. This validates an adjacent control rather than the outcome of secret scanning and push protection respond to leaks.
Question 634
An impatient project team suggests risky shortcuts for this case: A developer accidentally adds an API credential to a commit and assumes its deletion from the latest file makes the secret safe. Which proposed response would create the clearest avoidable risk here? Select ONE answer.
- Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints.
- Close the alert without revoking the leaked token because its visible source line was deleted in a later commit.
- Review and set available organization or enterprise Copilot policies and seat assignments for approved users.
- Inspect available organization or enterprise audit-log events for the action, actor and time window.
Explanation
Correct Answer
B:Close the alert without revoking the leaked token because its visible source line was deleted in a later commit. The shortcut contradicts the principle that Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. The safer GitHub workflow is to revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure after checking whether the team can inspect the reported secret location, exposure context and current token status without copying secrets into new logs.
Incorrect Answers
A:Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints. The shortcut contradicts the principle that Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. The reported issue instead calls for rejecting close the alert without revoking the leaked token because its visible source line was deleted in a later commit.
C:Review and set available organization or enterprise Copilot policies and seat assignments for approved users. The shortcut contradicts the principle that Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. The reported issue instead calls for rejecting close the alert without revoking the leaked token because its visible source line was deleted in a later commit.
D:Inspect available organization or enterprise audit-log events for the action, actor and time window. The shortcut contradicts the principle that Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. The reported issue instead calls for rejecting close the alert without revoking the leaked token because its visible source line was deleted in a later commit.
Question 635
A GitHub contributor is asked to resolve this report: A private repository has a suspected exposed deployment token and maintainers want to limit further accidental publication. Which controlled GitHub workflow action is most appropriate here? Select ONE best answer.
- Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities.
- Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.
- Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure.
- Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements.
Explanation
Correct Answer
C:Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. The first useful confirmation step is to inspect the reported secret location, exposure context and current token status without copying secrets into new logs. A private repository has a suspected exposed deployment token and maintainers want to limit further accidental publication.
Incorrect Answers
A:Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities. Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. Applying it first would leave secret scanning and push protection respond to leaks unresolved.
B:Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch. Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. Applying it first would leave secret scanning and push protection respond to leaks unresolved.
D:Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements. Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. Applying it first would leave secret scanning and push protection respond to leaks unresolved.
Question 636
An administrator is building an ongoing checklist for this issue: A private repository has a suspected exposed deployment token and maintainers want to limit further accidental publication. Which maintenance policy is most appropriate for this specific risk? Select ONE answer.
- Keep dependency manifests current and maintain a regular vulnerability review cycle.
- Enforce applicable organization authentication requirements and review lost-device recovery procedures.
- Review passkey availability, device access and recovery options during security onboarding.
- Educate contributors about safe secret storage and configure scanning or push protection where supported.
Explanation
Correct Answer
D:Educate contributors about safe secret storage and configure scanning or push protection where supported. The reason it is relevant is that Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. Check periodically that the compromised credential is no longer usable and relevant repository protection alerts are addressed.
Incorrect Answers
A:Keep dependency manifests current and maintain a regular vulnerability review cycle. The reason it is relevant is that Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. This would not prevent the recurrence of the secret scanning and push protection respond to leaks failure.
B:Enforce applicable organization authentication requirements and review lost-device recovery procedures. The reason it is relevant is that Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. This would not prevent the recurrence of the secret scanning and push protection respond to leaks failure.
C:Review passkey availability, device access and recovery options during security onboarding. The reason it is relevant is that Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. This would not prevent the recurrence of the secret scanning and push protection respond to leaks failure.
Question 637
A developer evaluates unsafe proposals following this situation: A private repository has a suspected exposed deployment token and maintainers want to limit further accidental publication. What action should the team explicitly avoid in this scenario? Select ONE answer.
- Close the alert without revoking the leaked token because its visible source line was deleted in a later commit.
- Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements.
- Set and verify repository visibility to match the actual intended audience and hosting plan capabilities.
- Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints.
Explanation
Correct Answer
A:Close the alert without revoking the leaked token because its visible source line was deleted in a later commit. The shortcut contradicts the principle that Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. The safer GitHub workflow is to revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure after checking whether the team can inspect the reported secret location, exposure context and current token status without copying secrets into new logs. A private repository has a suspected exposed deployment token and maintainers want to limit further accidental publication.
Incorrect Answers
B:Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements. The shortcut contradicts the principle that Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. The direct risk in the case is secret scanning and push protection respond to leaks, not this other concern.
C:Set and verify repository visibility to match the actual intended audience and hosting plan capabilities. The shortcut contradicts the principle that Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. The direct risk in the case is secret scanning and push protection respond to leaks, not this other concern.
D:Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints. The shortcut contradicts the principle that Leaked secrets remain sensitive even if code is edited later; scanning and preventive controls complement credential revocation. The direct risk in the case is secret scanning and push protection respond to leaks, not this other concern.
Question 638
A project owner is investigating an operational GitHub workflow issue: A library repository contains outdated dependencies and the team learns of a vulnerability advisory involving one package version. Which practical next step fits this specific repository situation? Select ONE answer.
- Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors.
- Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.
- Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.
- Create a narrowly scoped fine-grained token with only the repository access and permissions actually required.
Explanation
Correct Answer
B:Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing. Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. The first useful confirmation step is to inspect dependency graph version information, advisory scope and update pull request test results before deciding on remediation.
Incorrect Answers
A:Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors. Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. The case instead calls for the following: triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.
C:Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan. Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. The case instead calls for the following: triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.
D:Create a narrowly scoped fine-grained token with only the repository access and permissions actually required. Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. The case instead calls for the following: triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.
Question 639
An administrator requests evidence about this repository behavior: A library repository contains outdated dependencies and the team learns of a vulnerability advisory involving one package version. What should the team verify first to isolate the problem correctly? Select ONE answer.
- Inspect current visibility and effective account permissions before publishing sensitive content.
- Inspect the enterprise account type and identity provisioning configuration before proposing an access migration.
- Inspect dependency graph version information, advisory scope and update pull request test results before deciding on remediation.
- Inspect current policy settings, assigned licenses and product capabilities to determine effective restrictions.
Explanation
Correct Answer
C:Inspect dependency graph version information, advisory scope and update pull request test results before deciding on remediation. The principle behind this distinction is that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. If the check supports this diagnosis, the next controlled response is to triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.
Incorrect Answers
A:Inspect current visibility and effective account permissions before publishing sensitive content. The principle behind this distinction is that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. It does not isolate the dependabot advisories and maintenance issue described.
B:Inspect the enterprise account type and identity provisioning configuration before proposing an access migration. The principle behind this distinction is that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. It does not isolate the dependabot advisories and maintenance issue described.
D:Inspect current policy settings, assigned licenses and product capabilities to determine effective restrictions. The principle behind this distinction is that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. It does not isolate the dependabot advisories and maintenance issue described.
Question 640
A project sponsor requires a clear acceptance check for this scenario: A library repository contains outdated dependencies and the team learns of a vulnerability advisory involving one package version. Which measured or visible outcome most reliably establishes success? Select ONE answer.
- The intended authorized API call succeeds while unrelated repositories and privileged operations remain inaccessible.
- The contributor can perform required tasks without unwanted authority to change sensitive settings.
- Approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges.
- Affected dependencies are evaluated and safely updated or otherwise mitigated with evidence of compatibility.
Explanation
Correct Answer
D:Affected dependencies are evaluated and safely updated or otherwise mitigated with evidence of compatibility. Closing an issue without this result would not prove technical resolution because Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. An independent review should first inspect dependency graph version information, advisory scope and update pull request test results before deciding on remediation.
Incorrect Answers
A:The intended authorized API call succeeds while unrelated repositories and privileged operations remain inaccessible. Closing an issue without this result would not prove technical resolution because Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. This validates an adjacent control rather than the outcome of dependabot advisories and maintenance.
B:The contributor can perform required tasks without unwanted authority to change sensitive settings. Closing an issue without this result would not prove technical resolution because Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. This validates an adjacent control rather than the outcome of dependabot advisories and maintenance.
C:Approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. Closing an issue without this result would not prove technical resolution because Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. This validates an adjacent control rather than the outcome of dependabot advisories and maintenance.