Microsoft GH-900 Practice Test 47
Question 460
A GitHub platform user encounters this scenario: A maintainer assigns an issue to a GitHub coding agent and wants a pull request trail for the result. Which controlled GitHub workflow action is most appropriate here? Select ONE best 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.
- Treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging.
- Delegate a well-scoped issue through the supported coding-agent workflow and review the resulting proposed branch or pull request.
Explanation
Correct Answer
D:Delegate a well-scoped issue through the supported coding-agent workflow and review the resulting proposed branch or pull request. GitHub coding agents can propose work through collaborative surfaces, but delegation does not eliminate change-control obligations. The first useful confirmation step is to check the task instructions, agent activity and submitted diff for the expected scope and required test evidence. A maintainer assigns an issue to a GitHub coding agent and wants a pull request trail for the result.
Incorrect Answers
A:Configure a GitHub Actions matrix so the same test job runs across required supported runtime or platform combinations. GitHub coding agents can propose work through collaborative surfaces, but delegation does not eliminate change-control obligations. Applying it first would leave copilot coding agent and task delegation unresolved.
B:Give workflow jobs least-privilege token permissions and use approved secret handling and trusted event boundaries. GitHub coding agents can propose work through collaborative surfaces, but delegation does not eliminate change-control obligations. Applying it first would leave copilot coding agent and task delegation unresolved.
C:Treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging. GitHub coding agents can propose work through collaborative surfaces, but delegation does not eliminate change-control obligations. Applying it first would leave copilot coding agent and task delegation unresolved.
Question 461
A project retrospective considers the long-term control for this situation: A maintainer assigns an issue to a GitHub coding agent and wants a pull request trail for the result. Which maintenance policy is most appropriate for this specific risk? Select ONE answer.
- Define clear agent tasks and preserve human merge approval and repository permission restrictions.
- Version and test development-container configuration when dependencies or supported runtimes change.
- Include editor selection guidance so contributors know when they need a proper development environment.
- Keep workflow triggers and maintenance dependencies under review as branches or repository requirements evolve.
Explanation
Correct Answer
A:Define clear agent tasks and preserve human merge approval and repository permission restrictions. Check periodically that a reviewer can inspect an explicit proposed implementation and accept or reject it through the repository's normal controls. It complements the initial correction to delegate a well-scoped issue through the supported coding-agent workflow and review the resulting proposed branch or pull request.
Incorrect Answers
B:Version and test development-container configuration when dependencies or supported runtimes change. Check periodically that a reviewer can inspect an explicit proposed implementation and accept or reject it through the repository's normal controls. This would not prevent the recurrence of the copilot coding agent and task delegation failure.
C:Include editor selection guidance so contributors know when they need a proper development environment. Check periodically that a reviewer can inspect an explicit proposed implementation and accept or reject it through the repository's normal controls. This would not prevent the recurrence of the copilot coding agent and task delegation failure.
D:Keep workflow triggers and maintenance dependencies under review as branches or repository requirements evolve. Check periodically that a reviewer can inspect an explicit proposed implementation and accept or reject it through the repository's normal controls. This would not prevent the recurrence of the copilot coding agent and task delegation failure.
Question 462
An organization wants to identify the least appropriate response to this event: A maintainer assigns an issue to a GitHub coding agent and wants a pull request trail for the result. What action should the team explicitly avoid in this scenario? Select ONE answer.
- Treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging.
- Grant an agent unrestricted secret access and assume delegated changes should bypass branch protections.
- Use Copilot Agent Mode for an authorized multi-file task and review its proposed edits, commands and verification output.
- Choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy.
Explanation
Correct Answer
B:Grant an agent unrestricted secret access and assume delegated changes should bypass branch protections. Objective closure would show that a reviewer can inspect an explicit proposed implementation and accept or reject it through the repository's normal controls. The safer GitHub workflow is to delegate a well-scoped issue through the supported coding-agent workflow and review the resulting proposed branch or pull request after checking whether the team can check the task instructions, agent activity and submitted diff for the expected scope and required test evidence. A maintainer assigns an issue to a GitHub coding agent and wants a pull request trail for the result.
Incorrect Answers
A:Treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging. Objective closure would show that a reviewer can inspect an explicit proposed implementation and accept or reject it through the repository's normal controls. The direct risk in the case is copilot coding agent and task delegation, not this other concern.
C:Use Copilot Agent Mode for an authorized multi-file task and review its proposed edits, commands and verification output. Objective closure would show that a reviewer can inspect an explicit proposed implementation and accept or reject it through the repository's normal controls. The direct risk in the case is copilot coding agent and task delegation, not this other concern.
D:Choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy. Objective closure would show that a reviewer can inspect an explicit proposed implementation and accept or reject it through the repository's normal controls. The direct risk in the case is copilot coding agent and task delegation, not this other concern.
Question 463
A contributor receives this specific collaboration request: A developer expects every Copilot model to behave identically and wants to use the same prompt for specialized tasks without evaluation. Which practical next step fits this specific repository situation? Select ONE answer.
- Use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required.
- Define a GitHub Actions workflow with an appropriate event trigger and an auditable build or test job.
- Choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy.
- Define clear GitHub Actions jobs and their explicit dependencies so publishing waits for required validation jobs.
Explanation
Correct Answer
C:Choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy. Copilot model options and capabilities vary by plan, client, configuration and ongoing product availability. The first useful confirmation step is to inspect model availability in the current product context and compare the generated result with independent tests.
Incorrect Answers
A:Use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required. Copilot model options and capabilities vary by plan, client, configuration and ongoing product availability. The case instead calls for the following: choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy.
B:Define a GitHub Actions workflow with an appropriate event trigger and an auditable build or test job. Copilot model options and capabilities vary by plan, client, configuration and ongoing product availability. The case instead calls for the following: choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy.
D:Define clear GitHub Actions jobs and their explicit dependencies so publishing waits for required validation jobs. Copilot model options and capabilities vary by plan, client, configuration and ongoing product availability. The case instead calls for the following: choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy.
Question 464
An engineer needs to distinguish root causes for the following workflow problem: A developer expects every Copilot model to behave identically and wants to use the same prompt for specialized tasks without evaluation. What should the team verify first to isolate the problem correctly? Select ONE answer.
- Inspect the agent's changed-file list, executed tools and test results before accepting the resulting patch.
- Check the task instructions, agent activity and submitted diff for the expected scope and required test evidence.
- Check current documented plan entitlements and enterprise-level controls before asserting a feature is available to all users.
- Inspect model availability in the current product context and compare the generated result with independent tests.
Explanation
Correct Answer
D:Inspect model availability in the current product context and compare the generated result with independent tests. If the check supports this diagnosis, the next controlled response is to choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy. Verify the improvement by checking that the selected model is allowed for the account and its output meets the team's documented quality expectations.
Incorrect Answers
A:Inspect the agent's changed-file list, executed tools and test results before accepting the resulting patch. If the check supports this diagnosis, the next controlled response is to choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy. It does not isolate the copilot multi-model selection has implications issue described.
B:Check the task instructions, agent activity and submitted diff for the expected scope and required test evidence. If the check supports this diagnosis, the next controlled response is to choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy. It does not isolate the copilot multi-model selection has implications issue described.
C:Check current documented plan entitlements and enterprise-level controls before asserting a feature is available to all users. If the check supports this diagnosis, the next controlled response is to choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy. It does not isolate the copilot multi-model selection has implications issue described.
Question 465
A repository owner asks for objective proof that this issue is fixed: A developer expects every Copilot model to behave identically and wants to use the same prompt for specialized tasks without evaluation. Which measured or visible outcome most reliably establishes success? Select ONE answer.
- The selected model is allowed for the account and its output meets the team's documented quality expectations.
- The publishing job starts only after its required validation predecessors complete successfully according to policy.
- Build steps run on a compatible runner with the expected toolchain and produce traceable job output.
- Test results are available for every required variant and failures identify the affected runtime or platform.
Explanation
Correct Answer
A:The selected model is allowed for the account and its output meets the team's documented quality expectations. Closing an issue without this result would not prove technical resolution because Copilot model options and capabilities vary by plan, client, configuration and ongoing product availability. An independent review should first inspect model availability in the current product context and compare the generated result with independent tests.
Incorrect Answers
B:The publishing job starts only after its required validation predecessors complete successfully according to policy. Closing an issue without this result would not prove technical resolution because Copilot model options and capabilities vary by plan, client, configuration and ongoing product availability. This validates an adjacent control rather than the outcome of copilot multi-model selection has implications.
C:Build steps run on a compatible runner with the expected toolchain and produce traceable job output. Closing an issue without this result would not prove technical resolution because Copilot model options and capabilities vary by plan, client, configuration and ongoing product availability. This validates an adjacent control rather than the outcome of copilot multi-model selection has implications.
D:Test results are available for every required variant and failures identify the affected runtime or platform. Closing an issue without this result would not prove technical resolution because Copilot model options and capabilities vary by plan, client, configuration and ongoing product availability. This validates an adjacent control rather than the outcome of copilot multi-model selection has implications.
Question 466
An impatient project team suggests risky shortcuts for this case: A developer expects every Copilot model to behave identically and wants to use the same prompt for specialized tasks without evaluation. What action should the team explicitly avoid in this scenario? Select ONE answer.
- Select the appropriate Copilot subscription and organization policy model based on governance and deployment requirements.
- Treat every newly available model as a guaranteed source of correct answers for all tasks without checking policy or tests.
- 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 every newly available model as a guaranteed source of correct answers for all tasks without checking policy or tests. That suggestion is specifically risky for the case: A developer expects every Copilot model to behave identically and wants to use the same prompt for specialized tasks without evaluation. The safer GitHub workflow is to choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy after checking whether the team can inspect model availability in the current product context and compare the generated result with independent tests.
Incorrect Answers
A:Select the appropriate Copilot subscription and organization policy model based on governance and deployment requirements. That suggestion is specifically risky for the case: A developer expects every Copilot model to behave identically and wants to use the same prompt for specialized tasks without evaluation. The reported issue instead calls for rejecting treat every newly available model as a guaranteed source of correct answers for all tasks without checking policy or tests.
C:Configure and launch a GitHub Codespace using a supported repository configuration and suitable resource settings. That suggestion is specifically risky for the case: A developer expects every Copilot model to behave identically and wants to use the same prompt for specialized tasks without evaluation. The reported issue instead calls for rejecting treat every newly available model as a guaranteed source of correct answers for all tasks without checking policy or tests.
D:Define a supported dev container configuration describing the intended development image, tools and setup steps. That suggestion is specifically risky for the case: A developer expects every Copilot model to behave identically and wants to use the same prompt for specialized tasks without evaluation. The reported issue instead calls for rejecting treat every newly available model as a guaranteed source of correct answers for all tasks without checking policy or tests.
Question 467
A GitHub contributor is asked to resolve this report: A platform team introduces model selection but cannot explain why availability, capabilities and results can differ. Which practical next step fits this specific repository situation? Select ONE answer.
- Give workflow jobs least-privilege token permissions and use approved secret handling and trusted event boundaries.
- Treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging.
- Choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy.
- Use Copilot Agent Mode for an authorized multi-file task and review its proposed edits, commands and verification output.
Explanation
Correct Answer
C:Choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy. Copilot model options and capabilities vary by plan, client, configuration and ongoing product availability. The first useful confirmation step is to inspect model availability in the current product context and compare the generated result with independent tests. A platform team introduces model selection but cannot explain why availability, capabilities and results can differ.
Incorrect Answers
A:Give workflow jobs least-privilege token permissions and use approved secret handling and trusted event boundaries. Copilot model options and capabilities vary by plan, client, configuration and ongoing product availability. Applying it first would leave copilot multi-model selection has implications unresolved.
B:Treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging. Copilot model options and capabilities vary by plan, client, configuration and ongoing product availability. Applying it first would leave copilot multi-model selection has implications unresolved.
D:Use Copilot Agent Mode for an authorized multi-file task and review its proposed edits, commands and verification output. Copilot model options and capabilities vary by plan, client, configuration and ongoing product availability. Applying it first would leave copilot multi-model selection has implications unresolved.
Question 468
An administrator is building an ongoing checklist for this issue: A platform team introduces model selection but cannot explain why availability, capabilities and results can differ. Which ongoing practice most reliably prevents this same GitHub issue from recurring? Select ONE answer.
- Include editor selection guidance so contributors know when they need a proper development environment.
- Keep workflow triggers and maintenance dependencies under review as branches or repository requirements evolve.
- Keep job dependencies aligned with release gates whenever workflow tasks are added or reorganized.
- Review supported model choices and privacy policies rather than hardcoding assumptions about permanent product entitlements.
Explanation
Correct Answer
D:Review supported model choices and privacy policies rather than hardcoding assumptions about permanent product entitlements. Check periodically that the selected model is allowed for the account and its output meets the team's documented quality expectations. It complements the initial correction to choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy.
Incorrect Answers
A:Include editor selection guidance so contributors know when they need a proper development environment. Check periodically that the selected model is allowed for the account and its output meets the team's documented quality expectations. This would not prevent the recurrence of the copilot multi-model selection has implications failure.
B:Keep workflow triggers and maintenance dependencies under review as branches or repository requirements evolve. Check periodically that the selected model is allowed for the account and its output meets the team's documented quality expectations. This would not prevent the recurrence of the copilot multi-model selection has implications failure.
C:Keep job dependencies aligned with release gates whenever workflow tasks are added or reorganized. Check periodically that the selected model is allowed for the account and its output meets the team's documented quality expectations. This would not prevent the recurrence of the copilot multi-model selection has implications failure.
Question 469
A developer evaluates unsafe proposals following this situation: A platform team introduces model selection but cannot explain why availability, capabilities and results can differ. What is the least defensible workaround for this project? Select ONE answer.
- Treat every newly available model as a guaranteed source of correct answers for all tasks without checking policy or tests.
- 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.
- Select the appropriate Copilot subscription and organization policy model based on governance and deployment requirements.
Explanation
Correct Answer
A:Treat every newly available model as a guaranteed source of correct answers for all tasks without checking policy or tests. That suggestion is specifically risky for the case: A platform team introduces model selection but cannot explain why availability, capabilities and results can differ. The safer GitHub workflow is to choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy after checking whether the team can inspect model availability in the current product context and compare the generated result with independent tests.
Incorrect Answers
B:Use Copilot Agent Mode for an authorized multi-file task and review its proposed edits, commands and verification output. That suggestion is specifically risky for the case: A platform team introduces model selection but cannot explain why availability, capabilities and results can differ. The direct risk in the case is copilot multi-model selection has implications, not this other concern.
C:Delegate a well-scoped issue through the supported coding-agent workflow and review the resulting proposed branch or pull request. That suggestion is specifically risky for the case: A platform team introduces model selection but cannot explain why availability, capabilities and results can differ. The direct risk in the case is copilot multi-model selection has implications, not this other concern.
D:Select the appropriate Copilot subscription and organization policy model based on governance and deployment requirements. That suggestion is specifically risky for the case: A platform team introduces model selection but cannot explain why availability, capabilities and results can differ. The direct risk in the case is copilot multi-model selection has implications, not this other concern.
Question 470
A project owner is investigating an operational GitHub workflow issue: A company needs centrally managed Copilot settings but a developer assumes a personal subscription automatically supplies organization policy controls. What should the contributor do to resolve this exact situation correctly? Select ONE answer.
- Define a GitHub Actions workflow with an appropriate event trigger and an auditable build or test job.
- Select the appropriate Copilot subscription and organization policy model based on governance and deployment requirements.
- Define clear GitHub Actions jobs and their explicit dependencies so publishing waits for required validation jobs.
- Select an appropriate Actions runner environment with approved tooling and trust boundaries for the workflow's jobs.
Explanation
Correct Answer
B:Select the appropriate Copilot subscription and organization policy model based on governance and deployment requirements. Copilot individual and organization-oriented offerings differ in administration and governance, and details may change over time. The first useful confirmation step is to check current documented plan entitlements and enterprise-level controls before asserting a feature is available to all users.
Incorrect Answers
A:Define a GitHub Actions workflow with an appropriate event trigger and an auditable build or test job. Copilot individual and organization-oriented offerings differ in administration and governance, and details may change over time. The case instead calls for the following: select the appropriate Copilot subscription and organization policy model based on governance and deployment requirements.
C:Define clear GitHub Actions jobs and their explicit dependencies so publishing waits for required validation jobs. Copilot individual and organization-oriented offerings differ in administration and governance, and details may change over time. The case instead calls for the following: select the appropriate Copilot subscription and organization policy model based on governance and deployment requirements.
D:Select an appropriate Actions runner environment with approved tooling and trust boundaries for the workflow's jobs. Copilot individual and organization-oriented offerings differ in administration and governance, and details may change over time. The case instead calls for the following: select the appropriate Copilot subscription and organization policy model based on governance and deployment requirements.