Get Microsoft GH-900 Exam Practice Questions - Real and Updated

Answer : B, D, E

A dev container defines the development environment for a GitHub Codespace. It allows a repository to specify tools, runtimes, dependencies, extensions, and setup behavior so contributors get a consistent workspace. Programming languages and project tools can be installed through the container configuration, making onboarding faster and reducing environment differences between developers. Extensions and plugins can also be included so the editor has the right support for the project. Shell preferences and scripts can be configured through dotfiles, helping users personalize terminal behavior and setup steps. The default region for Codespace data storage and the inactivity timeout period are not configured inside the dev container. Those are controlled through Codespaces account, organization, or service-level settings.

Answer : C

A centralized version control system stores the main project history in one central location, usually a server. Developers connect to that server to check out files, make changes, and submit updates. This differs from Git, which is distributed and allows every developer to have a full local copy of the repository history. In a centralized model, collaboration depends heavily on the availability of the central server. If the server is unavailable, developers may be limited in what they can do. GitHub Foundations emphasizes this distinction because GitHub is built around Git, a distributed version control system. Option C correctly describes centralized version control because the central server holds the authoritative project history.

Answer : C

Answer : D

Answer : D

Assigning collaborators to an issue or pull request helps clarify responsibility and ownership. When multiple collaborators are assigned, GitHub does not limit responsibility to only the first assignee. Instead, all assigned users are associated with the work item and can receive notifications based on their notification settings. This is useful when several people share responsibility for investigation, implementation, review, or follow-up. Assignment does not automatically lock the issue or pull request, and it does not automatically change the item's status to ''In Progress.'' Status tracking is usually handled through labels, Projects fields, or workflow automation. In GitHub collaboration workflows, assignees make it clear who is expected to work on or respond to an issue or pull request.