Microsoft GH-900 Practice Test 50
Question 490
A GitHub maintainer must reject an unsound recommendation after this report: A GitHub Codespaces project opens in a cloud editor but lacks the required development tools and extensions. Which proposed response would create the clearest avoidable risk here? Select ONE answer.
- Select the appropriate Copilot subscription and organization policy model based on governance and deployment requirements.
- Assume a repository's README automatically provisions every language runtime inside any new Codespace.
- Configure and launch a GitHub Codespace using a supported repository configuration and suitable resource settings.
- Use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required.
Explanation
Correct Answer
B:Assume a repository's README automatically provisions every language runtime inside any new Codespace. Objective closure would show that new environments start with compatible tooling and can run documented project checks without undocumented manual installation. The safer GitHub workflow is to define a supported dev container configuration describing the intended development image, tools and setup steps after checking whether the team can inspect.devcontainer configuration and rebuild a fresh environment to verify packages and startup commands. A GitHub Codespaces project opens in a cloud editor but lacks the required development tools and extensions.
Incorrect Answers
A:Select the appropriate Copilot subscription and organization policy model based on governance and deployment requirements. Objective closure would show that new environments start with compatible tooling and can run documented project checks without undocumented manual installation. The direct risk in the case is dev container configuration defines toolchain, not this other concern.
C:Configure and launch a GitHub Codespace using a supported repository configuration and suitable resource settings. Objective closure would show that new environments start with compatible tooling and can run documented project checks without undocumented manual installation. The direct risk in the case is dev container configuration defines toolchain, not this other concern.
D:Use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required. Objective closure would show that new environments start with compatible tooling and can run documented project checks without undocumented manual installation. The direct risk in the case is dev container configuration defines toolchain, not this other concern.
Question 491
During a repository review, the maintainer finds this condition: A technical writer needs to edit Markdown quickly but does not need a terminal, container or full local development setup. 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.
- Use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required.
- Treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging.
Explanation
Correct Answer
C:Use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required. The underlying distinction is that github.dev is a lightweight web editor, whereas Codespaces provides a cloud development environment with runnable tooling. The first useful confirmation step is to compare the intended task's terminal and runtime needs with the capabilities visible in github.dev and Codespaces.
Incorrect Answers
A:Configure a GitHub Actions matrix so the same test job runs across required supported runtime or platform combinations. The underlying distinction is that github.dev is a lightweight web editor, whereas Codespaces provides a cloud development environment with runnable tooling. The case instead calls for the following: use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required.
B:Give workflow jobs least-privilege token permissions and use approved secret handling and trusted event boundaries. The underlying distinction is that github.dev is a lightweight web editor, whereas Codespaces provides a cloud development environment with runnable tooling. The case instead calls for the following: use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required.
D:Treat GitHub Copilot completions as suggestions and manually review, test and adjust the code before merging. The underlying distinction is that github.dev is a lightweight web editor, whereas Codespaces provides a cloud development environment with runnable tooling. The case instead calls for the following: use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required.
Question 492
A repository maintainer begins diagnosis of the following report: A technical writer needs to edit Markdown quickly but does not need a terminal, container or full local development setup. Which check best distinguishes the actual cause from a different GitHub issue? Select ONE answer.
- Check the codespace's repository, creation settings, installed dependencies and terminal availability against the project instructions.
- Inspect .devcontainer configuration and rebuild a fresh environment to verify packages and startup commands.
- Inspect the workflow YAML event conditions and a representative run's logs to confirm when the automation starts.
- Compare the intended task's terminal and runtime needs with the capabilities visible in github.dev and Codespaces.
Explanation
Correct Answer
D:Compare the intended task's terminal and runtime needs with the capabilities visible in github.dev and Codespaces. Verify the improvement by checking that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. If the check supports this diagnosis, the next controlled response is to use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required.
Incorrect Answers
A:Check the codespace's repository, creation settings, installed dependencies and terminal availability against the project instructions. Verify the improvement by checking that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. It does not isolate the github.dev is a lightweight browser editor issue described.
B:Inspect.devcontainer configuration and rebuild a fresh environment to verify packages and startup commands. Verify the improvement by checking that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. It does not isolate the github.dev is a lightweight browser editor issue described.
C:Inspect the workflow YAML event conditions and a representative run's logs to confirm when the automation starts. Verify the improvement by checking that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. It does not isolate the github.dev is a lightweight browser editor issue described.
Question 493
An onboarding lead requires measurable closure for this problem: A technical writer needs to edit Markdown quickly but does not need a terminal, container or full local development setup. Which verifiable state directly confirms successful remediation? Select ONE answer.
- The writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace.
- The final committed code meets the stated requirements and passes independent validation after human review.
- The requested refactor is reviewable as explicit file changes with appropriate tests rather than an unverified chat claim.
- A reviewer can inspect an explicit proposed implementation and accept or reject it through the repository's normal controls.
Explanation
Correct Answer
A: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 github.dev is a lightweight web editor, whereas Codespaces provides a cloud development environment with runnable tooling. An independent review should first compare the intended task's terminal and runtime needs with the capabilities visible in github.dev and Codespaces.
Incorrect Answers
B: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 github.dev is a lightweight web editor, whereas Codespaces provides a cloud development environment with runnable tooling. This validates an adjacent control rather than the outcome of github.dev is a lightweight browser editor.
C:The requested refactor is reviewable as explicit file changes with appropriate tests rather than an unverified chat claim. Closing an issue without this result would not prove technical resolution because github.dev is a lightweight web editor, whereas Codespaces provides a cloud development environment with runnable tooling. This validates an adjacent control rather than the outcome of github.dev is a lightweight browser editor.
D:A reviewer can inspect an explicit proposed implementation and accept or reject it through the repository's normal controls. Closing an issue without this result would not prove technical resolution because github.dev is a lightweight web editor, whereas Codespaces provides a cloud development environment with runnable tooling. This validates an adjacent control rather than the outcome of github.dev is a lightweight browser editor.
Question 494
A developer evaluates unsafe proposals following this situation: A technical writer needs to edit Markdown quickly but does not need a terminal, container or full local development setup. Which proposed response would create the clearest avoidable risk here? Select ONE answer.
- Define a GitHub Actions workflow with an appropriate event trigger and an auditable build or test job.
- Describe github.dev as automatically supplying the same terminal, configured runtimes and compute as a full Codespace.
- 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:Describe github.dev as automatically supplying the same terminal, configured runtimes and compute as a full Codespace. Objective closure would show that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. The safer GitHub workflow is to use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required after checking whether the team can compare the intended task's terminal and runtime needs with the capabilities visible in github.dev and Codespaces.
Incorrect Answers
A:Define a GitHub Actions workflow with an appropriate event trigger and an auditable build or test job. Objective closure would show that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. The reported issue instead calls for rejecting describe github.dev as automatically supplying the same terminal, configured runtimes and compute as a full Codespace.
C:Define clear GitHub Actions jobs and their explicit dependencies so publishing waits for required validation jobs. Objective closure would show that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. The reported issue instead calls for rejecting describe github.dev as automatically supplying the same terminal, configured runtimes and compute as a full Codespace.
D:Select an appropriate Actions runner environment with approved tooling and trust boundaries for the workflow's jobs. Objective closure would show that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. The reported issue instead calls for rejecting describe github.dev as automatically supplying the same terminal, configured runtimes and compute as a full Codespace.
Question 495
A project owner is investigating an operational GitHub workflow issue: A novice opens github.dev and expects to compile a native binary there exactly as in a provisioned Codespace. Which controlled GitHub workflow action is most appropriate here? Select ONE best answer.
- Choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy.
- Select the appropriate Copilot subscription and organization policy model based on governance and deployment requirements.
- Use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required.
- Configure and launch a GitHub Codespace using a supported repository configuration and suitable resource settings.
Explanation
Correct Answer
C:Use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required. The underlying distinction is that github.dev is a lightweight web editor, whereas Codespaces provides a cloud development environment with runnable tooling. The first useful confirmation step is to compare the intended task's terminal and runtime needs with the capabilities visible in github.dev and Codespaces. A novice opens github.dev and expects to compile a native binary there exactly as in a provisioned Codespace.
Incorrect Answers
A:Choose an available Copilot-supported model for the task and validate the output against requirements and organizational policy. The underlying distinction is that github.dev is a lightweight web editor, whereas Codespaces provides a cloud development environment with runnable tooling. Applying it first would leave github.dev is a lightweight browser editor unresolved.
B:Select the appropriate Copilot subscription and organization policy model based on governance and deployment requirements. The underlying distinction is that github.dev is a lightweight web editor, whereas Codespaces provides a cloud development environment with runnable tooling. Applying it first would leave github.dev is a lightweight browser editor unresolved.
D:Configure and launch a GitHub Codespace using a supported repository configuration and suitable resource settings. The underlying distinction is that github.dev is a lightweight web editor, whereas Codespaces provides a cloud development environment with runnable tooling. Applying it first would leave github.dev is a lightweight browser editor unresolved.
Question 496
A contributor asks how to keep this workflow problem from happening again: A novice opens github.dev and expects to compile a native binary there exactly as in a provisioned Codespace. Which maintenance policy is most appropriate for this specific risk? Select ONE answer.
- Review matrix dimensions whenever compatibility support policies or dependencies change.
- Keep secrets rotated and limit permissions for automated jobs, especially on external pull request events.
- Include AI-assisted contributions in ordinary code review and secure development practices.
- Include editor selection guidance so contributors know when they need a proper development environment.
Explanation
Correct Answer
D:Include editor selection guidance so contributors know when they need a proper development environment. Check periodically that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace.
Incorrect Answers
A:Review matrix dimensions whenever compatibility support policies or dependencies change. Check periodically that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. This would not prevent the recurrence of the github.dev is a lightweight browser editor failure.
B:Keep secrets rotated and limit permissions for automated jobs, especially on external pull request events. Check periodically that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. This would not prevent the recurrence of the github.dev is a lightweight browser editor failure.
C:Include AI-assisted contributions in ordinary code review and secure development practices. Check periodically that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. This would not prevent the recurrence of the github.dev is a lightweight browser editor failure.
Question 497
During a review, a contributor proposes an emergency bypass for this problem: A novice opens github.dev and expects to compile a native binary there exactly as in a provisioned Codespace. What action should the team explicitly avoid in this scenario? Select ONE answer.
- Describe github.dev as automatically supplying the same terminal, configured runtimes and compute as a full Codespace.
- 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.
- Define a GitHub Actions workflow with an appropriate event trigger and an auditable build or test job.
Explanation
Correct Answer
A:Describe github.dev as automatically supplying the same terminal, configured runtimes and compute as a full Codespace. Objective closure would show that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. The safer GitHub workflow is to use github.dev for lightweight repository browsing and editing, and choose Codespaces when compute and terminal tools are required after checking whether the team can compare the intended task's terminal and runtime needs with the capabilities visible in github.dev and Codespaces. A novice opens github.dev and expects to compile a native binary there exactly as in a provisioned Codespace.
Incorrect Answers
B:Configure and launch a GitHub Codespace using a supported repository configuration and suitable resource settings. Objective closure would show that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. The direct risk in the case is github.dev is a lightweight browser editor, not this other concern.
C:Define a supported dev container configuration describing the intended development image, tools and setup steps. Objective closure would show that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. The direct risk in the case is github.dev is a lightweight browser editor, not this other concern.
D:Define a GitHub Actions workflow with an appropriate event trigger and an auditable build or test job. Objective closure would show that the writer can make and propose source edits in the browser without misrepresenting it as a full compute workspace. The direct risk in the case is github.dev is a lightweight browser editor, not this other concern.
Question 498
A distributed project team must respond to the following case: A product group tracks issues from several repositories in separate spreadsheets and cannot see one cross-team backlog. Which practical next step fits this specific repository situation? Select ONE answer.
- Define well-scoped project fields such as priority, iteration or estimate and populate them consistently for each item.
- Use a GitHub Project table view and add the relevant repository issues or pull requests with useful custom fields.
- Configure an appropriate supported GitHub Project workflow automation for the intended event and status transition.
- Assign relevant GitHub repository issues to a meaningful release milestone and maintain each issue's real status.
Explanation
Correct Answer
B:Use a GitHub Project table view and add the relevant repository issues or pull requests with useful custom fields. GitHub Projects provides structured views over work items while those issues and pull requests remain linked to their repositories. The first useful confirmation step is to inspect project items, repository links, columns and filters to ensure the right work records are represented.
Incorrect Answers
A:Define well-scoped project fields such as priority, iteration or estimate and populate them consistently for each item. GitHub Projects provides structured views over work items while those issues and pull requests remain linked to their repositories. The case instead calls for the following: use a GitHub Project table view and add the relevant repository issues or pull requests with useful custom fields.
C:Configure an appropriate supported GitHub Project workflow automation for the intended event and status transition. GitHub Projects provides structured views over work items while those issues and pull requests remain linked to their repositories. The case instead calls for the following: use a GitHub Project table view and add the relevant repository issues or pull requests with useful custom fields.
D:Assign relevant GitHub repository issues to a meaningful release milestone and maintain each issue's real status. GitHub Projects provides structured views over work items while those issues and pull requests remain linked to their repositories. The case instead calls for the following: use a GitHub Project table view and add the relevant repository issues or pull requests with useful custom fields.
Question 499
Before changing GitHub settings, a project reviewer examines this case: A product group tracks issues from several repositories in separate spreadsheets and cannot see one cross-team backlog. What should the team verify first to isolate the problem correctly? Select ONE answer.
- Check board grouping and each item's status value against the source issue's actual implementation state.
- Inspect the project date or iteration fields and the view configuration before interpreting the visible schedule.
- Inspect project items, repository links, columns and filters to ensure the right work records are represented.
- Inspect field types, allowed values and filled item records to identify missing or inconsistent classifications.
Explanation
Correct Answer
C:Inspect project items, repository links, columns and filters to ensure the right work records are represented. If the check supports this diagnosis, the next controlled response is to use a GitHub Project table view and add the relevant repository issues or pull requests with useful custom fields. Verify the improvement by checking that the team can view and sort the consolidated backlog while the linked source issues retain their original discussion.
Incorrect Answers
A:Check board grouping and each item's status value against the source issue's actual implementation state. If the check supports this diagnosis, the next controlled response is to use a GitHub Project table view and add the relevant repository issues or pull requests with useful custom fields. It does not isolate the github projects table view organizes items issue described.
B:Inspect the project date or iteration fields and the view configuration before interpreting the visible schedule. If the check supports this diagnosis, the next controlled response is to use a GitHub Project table view and add the relevant repository issues or pull requests with useful custom fields. It does not isolate the github projects table view organizes items issue described.
D:Inspect field types, allowed values and filled item records to identify missing or inconsistent classifications. If the check supports this diagnosis, the next controlled response is to use a GitHub Project table view and add the relevant repository issues or pull requests with useful custom fields. It does not isolate the github projects table view organizes items issue described.
Question 500
Following a proposed correction, a reviewer revisits the following case: A product group tracks issues from several repositories in separate spreadsheets and cannot see one cross-team backlog. Which measured or visible outcome most reliably establishes success? Select ONE answer.
- Contributors receive consistent actionable guidance without receiving an irrelevant canned reply.
- The report describes the selected throughput or status trends without mislabeling duplicates as shipped product features.
- Backlog, active and completed items appear in the expected columns with status reflecting verified progress.
- The team can view and sort the consolidated backlog while the linked source issues retain their original discussion.
Explanation
Correct Answer
D:The team can view and sort the consolidated backlog while the linked source issues retain their original discussion. Closing an issue without this result would not prove technical resolution because GitHub Projects provides structured views over work items while those issues and pull requests remain linked to their repositories. An independent review should first inspect project items, repository links, columns and filters to ensure the right work records are represented.
Incorrect Answers
A:Contributors receive consistent actionable guidance without receiving an irrelevant canned reply. Closing an issue without this result would not prove technical resolution because GitHub Projects provides structured views over work items while those issues and pull requests remain linked to their repositories. This validates an adjacent control rather than the outcome of github projects table view organizes items.
B:The report describes the selected throughput or status trends without mislabeling duplicates as shipped product features. Closing an issue without this result would not prove technical resolution because GitHub Projects provides structured views over work items while those issues and pull requests remain linked to their repositories. This validates an adjacent control rather than the outcome of github projects table view organizes items.
C:Backlog, active and completed items appear in the expected columns with status reflecting verified progress. Closing an issue without this result would not prove technical resolution because GitHub Projects provides structured views over work items while those issues and pull requests remain linked to their repositories. This validates an adjacent control rather than the outcome of github projects table view organizes items.