Microsoft GH-900 Practice Test 45
Question 440
An engineering manager is defining a durable safeguard for this problem: A team runs pull request automation from outside contributors and worries that a job might expose sensitive publishing credentials. What repeatable follow-up control best addresses the root weakness? Select ONE answer.
- Review supported model choices and privacy policies rather than hardcoding assumptions about permanent product entitlements.
- Recheck GitHub's current plan documentation when entitlement or data-handling expectations change.
- Maintain dev environment configuration and apply usage, cost and access controls for cloud-based workspaces.
- Keep secrets rotated and limit permissions for automated jobs, especially on external pull request events.
Explanation
Correct Answer
D:Keep secrets rotated and limit permissions for automated jobs, especially on external pull request events. It complements the initial correction to give workflow jobs least-privilege token permissions and use approved secret handling and trusted event boundaries. Check periodically that the authorized release job can perform its scoped action without printing or exposing reusable credentials to untrusted changes.
Incorrect Answers
A:Review supported model choices and privacy policies rather than hardcoding assumptions about permanent product entitlements. It complements the initial correction to give workflow jobs least-privilege token permissions and use approved secret handling and trusted event boundaries. This would not prevent the recurrence of the workflow permissions and secrets minimize risk failure.
B:Recheck GitHub's current plan documentation when entitlement or data-handling expectations change. It complements the initial correction to give workflow jobs least-privilege token permissions and use approved secret handling and trusted event boundaries. This would not prevent the recurrence of the workflow permissions and secrets minimize risk failure.
C:Maintain dev environment configuration and apply usage, cost and access controls for cloud-based workspaces. It complements the initial correction to give workflow jobs least-privilege token permissions and use approved secret handling and trusted event boundaries. This would not prevent the recurrence of the workflow permissions and secrets minimize risk failure.
Question 441
An impatient project team suggests risky shortcuts for this case: A team runs pull request automation from outside contributors and worries that a job might expose sensitive publishing credentials. Which suggested shortcut should be REJECTED in this situation? Select ONE answer.
- Hardcode a long-lived production token into repository workflow YAML so every contributor can inspect it.
- Select an appropriate Actions runner environment with approved tooling and trust boundaries for the workflow's jobs.
- Configure a GitHub Actions matrix so the same test job runs across required supported runtime or platform combinations.
- Treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging.
Explanation
Correct Answer
A:Hardcode a long-lived production token into repository workflow YAML so every contributor can inspect it. The safer GitHub workflow is to give workflow jobs least-privilege token permissions and use approved secret handling and trusted event boundaries after checking whether the team can review workflow permissions, secret references and trigger trust context before allowing sensitive steps to run. A team runs pull request automation from outside contributors and worries that a job might expose sensitive publishing credentials.
Incorrect Answers
B:Select an appropriate Actions runner environment with approved tooling and trust boundaries for the workflow's jobs. The safer GitHub workflow is to give workflow jobs least-privilege token permissions and use approved secret handling and trusted event boundaries after checking whether the team can review workflow permissions, secret references and trigger trust context before allowing sensitive steps to run. The direct risk in the case is workflow permissions and secrets minimize risk, not this other concern.
C:Configure a GitHub Actions matrix so the same test job runs across required supported runtime or platform combinations. The safer GitHub workflow is to give workflow jobs least-privilege token permissions and use approved secret handling and trusted event boundaries after checking whether the team can review workflow permissions, secret references and trigger trust context before allowing sensitive steps to run. The direct risk in the case is workflow permissions and secrets minimize risk, not this other concern.
D:Treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging. The safer GitHub workflow is to give workflow jobs least-privilege token permissions and use approved secret handling and trusted event boundaries after checking whether the team can review workflow permissions, secret references and trigger trust context before allowing sensitive steps to run. The direct risk in the case is workflow permissions and secrets minimize risk, not this other concern.
Question 442
A GitHub contributor is asked to resolve this report: A beginner accepts AI-generated code without understanding whether it meets their application's security requirements. What is the most defensible technical action for this case? Select ONE answer.
- Select the appropriate Copilot subscription and organization policy model based on governance and deployment requirements.
- Treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging.
- Configure and launch a GitHub Codespace using a supported repository configuration and suitable resource settings.
- Define a supported dev container configuration describing the intended development image, tools and setup steps.
Explanation
Correct Answer
B:Treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging. Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. The first useful confirmation step is to inspect the proposed changes, project tests and security assumptions instead of assuming an AI suggestion is authoritative.
Incorrect Answers
A:Select the appropriate Copilot subscription and organization policy model based on governance and deployment requirements. Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. The case instead calls for the following: treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging.
C:Configure and launch a GitHub Codespace using a supported repository configuration and suitable resource settings. Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. The case instead calls for the following: treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging.
D:Define a supported dev container configuration describing the intended development image, tools and setup steps. Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. The case instead calls for the following: treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging.
Question 443
An internal auditor needs the first meaningful check for this situation: A beginner accepts AI-generated code without understanding whether it meets their application's security requirements. Which focused investigation provides the most useful initial evidence? Select ONE answer.
- Inspect the strategy.matrix values and individual run entries to verify the desired combinations were scheduled.
- Review workflow permissions, secret references and trigger trust context before allowing sensitive steps to run.
- Inspect the proposed changes, project tests and security assumptions instead of assuming an AI suggestion is authoritative.
- Inspect the agent's changed-file list, executed tools and test results before accepting the resulting patch.
Explanation
Correct Answer
C:Inspect the proposed changes, project tests and security assumptions instead of assuming an AI suggestion is authoritative. The principle behind this distinction is that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. If the check supports this diagnosis, the next controlled response is to treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging.
Incorrect Answers
A:Inspect the strategy.matrix values and individual run entries to verify the desired combinations were scheduled. The principle behind this distinction is that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. It does not isolate the copilot inline suggestions need review issue described.
B:Review workflow permissions, secret references and trigger trust context before allowing sensitive steps to run. The principle behind this distinction is that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. It does not isolate the copilot inline suggestions need review issue described.
D:Inspect the agent's changed-file list, executed tools and test results before accepting the resulting patch. The principle behind this distinction is that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. It does not isolate the copilot inline suggestions need review issue described.
Question 444
A change-control team asks what result would establish real resolution: A beginner accepts AI-generated code without understanding whether it meets their application's security requirements. How should the team demonstrate that the approved change worked? Select ONE answer.
- New environments start with compatible tooling and can run documented project checks without undocumented manual installation.
- The writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace.
- A qualifying repository event starts the expected workflow and reports the intended test result on the associated change.
- The final committed code meets the stated requirements and passes independent validation after human review.
Explanation
Correct Answer
D:The final committed code meets the stated requirements and passes independent validation after human review. Closing an issue without this result would not prove technical resolution because Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. An independent review should first inspect the proposed changes, project tests and security assumptions instead of assuming an AI suggestion is authoritative.
Incorrect Answers
A:New environments start with compatible tooling and can run documented project checks without undocumented manual installation. Closing an issue without this result would not prove technical resolution because Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. This validates an adjacent control rather than the outcome of copilot inline suggestions need review.
B:The writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. Closing an issue without this result would not prove technical resolution because Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. This validates an adjacent control rather than the outcome of copilot inline suggestions need review.
C:A qualifying repository event starts the expected workflow and reports the intended test result on the associated change. Closing an issue without this result would not prove technical resolution because Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. This validates an adjacent control rather than the outcome of copilot inline suggestions need review.
Question 445
An organization wants to identify the least appropriate response to this event: A beginner accepts AI-generated code without understanding whether it meets their application's security requirements. Which suggested shortcut should be REJECTED in this situation? Select ONE answer.
- Accept every generated completion automatically and skip testing because Copilot's suggestions always match the project.
- Use Copilot Agent Mode for an authorized multi-file task and review its proposed edits, commands and verification output.
- Delegate a well-scoped issue through the supported coding-agent workflow and review the resulting proposed branch or pull request.
- Choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy.
Explanation
Correct Answer
A:Accept every generated completion automatically and skip testing because Copilot's suggestions always match the project. The shortcut contradicts the principle that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. The safer GitHub workflow is to treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging after checking whether the team can inspect the proposed changes, project tests and security assumptions instead of assuming an AI suggestion is authoritative.
Incorrect Answers
B:Use Copilot Agent Mode for an authorized multi-file task and review its proposed edits, commands and verification output. The shortcut contradicts the principle that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. The reported issue instead calls for rejecting accept every generated completion automatically and skip testing because Copilot's suggestions always match the project.
C:Delegate a well-scoped issue through the supported coding-agent workflow and review the resulting proposed branch or pull request. The shortcut contradicts the principle that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. The reported issue instead calls for rejecting accept every generated completion automatically and skip testing because Copilot's suggestions always match the project.
D:Choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy. The shortcut contradicts the principle that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. The reported issue instead calls for rejecting accept every generated completion automatically and skip testing because Copilot's suggestions always match the project.
Question 446
A contributor receives this specific collaboration request: A developer uses GitHub Copilot to draft repetitive tests but wants to avoid confusing generated suggestions with verified implementations. What is the most defensible technical action for this case? Select ONE answer.
- Define clear GitHub Actions jobs and their explicit dependencies so publishing waits for required validation jobs.
- Treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging.
- Select an appropriate Actions runner environment with approved tooling and trust boundaries for the workflow's jobs.
- Configure a GitHub Actions matrix so the same test job runs across required supported runtime or platform combinations.
Explanation
Correct Answer
B:Treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging. Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. The first useful confirmation step is to inspect the proposed changes, project tests and security assumptions instead of assuming an AI suggestion is authoritative. A developer uses GitHub Copilot to draft repetitive tests but wants to avoid confusing generated suggestions with verified implementations.
Incorrect Answers
A:Define clear GitHub Actions jobs and their explicit dependencies so publishing waits for required validation jobs. Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. Applying it first would leave copilot inline suggestions need review unresolved.
C:Select an appropriate Actions runner environment with approved tooling and trust boundaries for the workflow's jobs. Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. Applying it first would leave copilot inline suggestions need review unresolved.
D:Configure a GitHub Actions matrix so the same test job runs across required supported runtime or platform combinations. Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. Applying it first would leave copilot inline suggestions need review unresolved.
Question 447
A repository owner is standardizing processes after this earlier failure: A developer uses GitHub Copilot to draft repetitive tests but wants to avoid confusing generated suggestions with verified implementations. What operational safeguard should remain after the immediate fix? Select ONE answer.
- Recheck GitHub's current plan documentation when entitlement or data-handling expectations change.
- Maintain dev environment configuration and apply usage, cost and access controls for cloud-based workspaces.
- Include AI-assisted contributions in ordinary code review and secure development practices.
- Version and test development-container configuration when dependencies or supported runtimes change.
Explanation
Correct Answer
C:Include AI-assisted contributions in ordinary code review and secure development practices. The reason it is relevant is that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. It complements the initial correction to treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging.
Incorrect Answers
A:Recheck GitHub's current plan documentation when entitlement or data-handling expectations change. The reason it is relevant is that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. This would not prevent the recurrence of the copilot inline suggestions need review failure.
B:Maintain dev environment configuration and apply usage, cost and access controls for cloud-based workspaces. The reason it is relevant is that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. This would not prevent the recurrence of the copilot inline suggestions need review failure.
D:Version and test development-container configuration when dependencies or supported runtimes change. The reason it is relevant is that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. This would not prevent the recurrence of the copilot inline suggestions need review failure.
Question 448
A GitHub maintainer must reject an unsound recommendation after this report: A developer uses GitHub Copilot to draft repetitive tests but wants to avoid confusing generated suggestions with verified implementations. Which tempting bypass would undermine rather than resolve the case? Select ONE answer.
- Configure a GitHub Actions matrix so the same test job runs across required supported runtime or platform combinations.
- Give workflow jobs least-privilege token permissions and use approved secret handling and trusted event boundaries.
- Use Copilot Agent Mode for an authorized multi-file task and review its proposed edits, commands and verification output.
- Accept every generated completion automatically and skip testing because Copilot's suggestions always match the project.
Explanation
Correct Answer
D:Accept every generated completion automatically and skip testing because Copilot's suggestions always match the project. The shortcut contradicts the principle that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. The safer GitHub workflow is to treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging after checking whether the team can inspect the proposed changes, project tests and security assumptions instead of assuming an AI suggestion is authoritative. A developer uses GitHub Copilot to draft repetitive tests but wants to avoid confusing generated suggestions with verified implementations.
Incorrect Answers
A:Configure a GitHub Actions matrix so the same test job runs across required supported runtime or platform combinations. The shortcut contradicts the principle that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. The direct risk in the case is copilot inline suggestions need review, not this other concern.
B:Give workflow jobs least-privilege token permissions and use approved secret handling and trusted event boundaries. The shortcut contradicts the principle that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. The direct risk in the case is copilot inline suggestions need review, not this other concern.
C:Use Copilot Agent Mode for an authorized multi-file task and review its proposed edits, commands and verification output. The shortcut contradicts the principle that Copilot provides AI-assisted development suggestions, but correctness and policy compliance remain the contributor's responsibility. The direct risk in the case is copilot inline suggestions need review, not this other concern.
Question 449
During a repository review, the maintainer finds this condition: A developer asks Copilot to refactor code across several files but mistakes a single-line completion for a multi-step agent workflow. Which response best meets this GitHub and Git requirement without creating unnecessary risk? Select ONE answer.
- Use Copilot Agent Mode for an authorized multi-file task and review its proposed edits, commands and verification output.
- Configure and launch a GitHub Codespace using a supported repository configuration and suitable resource settings.
- Define a supported dev container configuration describing the intended development image, tools and setup steps.
- Use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required.
Explanation
Correct Answer
A:Use Copilot Agent Mode for an authorized multi-file task and review its proposed edits, commands and verification output. Agent Mode can coordinate multiple editing and tool steps, but human review and security boundaries still apply. The first useful confirmation step is to inspect the agent's changed-file list, executed tools and test results before accepting the resulting patch.
Incorrect Answers
B:Configure and launch a GitHub Codespace using a supported repository configuration and suitable resource settings. Agent Mode can coordinate multiple editing and tool steps, but human review and security boundaries still apply. The case instead calls for the following: use Copilot Agent Mode for an authorized multi-file task and review its proposed edits, commands and verification output.
C:Define a supported dev container configuration describing the intended development image, tools and setup steps. Agent Mode can coordinate multiple editing and tool steps, but human review and security boundaries still apply. The case instead calls for the following: use Copilot Agent Mode for an authorized multi-file task and review its proposed edits, commands and verification output.
D:Use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required. Agent Mode can coordinate multiple editing and tool steps, but human review and security boundaries still apply. The case instead calls for the following: use Copilot Agent Mode for an authorized multi-file task and review its proposed edits, commands and verification output.
Question 450
A repository maintainer begins diagnosis of the following report: A developer asks Copilot to refactor code across several files but mistakes a single-line completion for a multi-step agent workflow. Which diagnostic review best explains this exact reported behavior? Select ONE answer.
- Review workflow permissions, secret references and trigger trust context before allowing sensitive steps to run.
- Inspect the agent's changed-file list, executed tools and test results before accepting the resulting patch.
- Inspect the proposed changes, project tests and security assumptions instead of assuming an AI suggestion is authoritative.
- Check the task instructions, agent activity and submitted diff for the expected scope and required test evidence.
Explanation
Correct Answer
B:Inspect the agent's changed-file list, executed tools and test results before accepting the resulting patch. Verify the improvement by checking that the requested refactor is reviewable as explicit file changes with appropriate tests rather than an unverified chat claim. If the check supports this diagnosis, the next controlled response is to use Copilot Agent Mode for an authorized multi-file task and review its proposed edits, commands and verification output.
Incorrect Answers
A:Review workflow permissions, secret references and trigger trust context before allowing sensitive steps to run. Verify the improvement by checking that the requested refactor is reviewable as explicit file changes with appropriate tests rather than an unverified chat claim. It does not isolate the copilot agent mode spans multi-step ide tasks issue described.
C:Inspect the proposed changes, project tests and security assumptions instead of assuming an AI suggestion is authoritative. Verify the improvement by checking that the requested refactor is reviewable as explicit file changes with appropriate tests rather than an unverified chat claim. It does not isolate the copilot agent mode spans multi-step ide tasks issue described.
D:Check the task instructions, agent activity and submitted diff for the expected scope and required test evidence. Verify the improvement by checking that the requested refactor is reviewable as explicit file changes with appropriate tests rather than an unverified chat claim. It does not isolate the copilot agent mode spans multi-step ide tasks issue described.