Microsoft GH-900 Online Practice Questions and Exam Preparation

Microsoft GH-900 Online Questions & Answers

• Question 31:

  Which of the following is a key characteristic of GitHub Projects?

  A. Ability to visualize the commit history
  B. Ability to import Gantt charts from Microsoft Project
  C. Ability to create and customize multiple views
  D. Ability to enforce required fields
  C. Ability to create and customize multiple views

  ---

  Explanation

  GitHub Projects is a flexible and powerful tool for project management that allows users to manage their work with ease. One of the key characteristics of GitHub Projects is the ability to create and customize multiple views. This feature enables teams to tailor the project management experience to their specific workflow needs, offering various ways to visualize tasks, issues, and work items. Custom Views: You can set up different views like Kanban boards, tables, or timelines, and apply filters to show only what is relevant for a particular aspect of the project. This customization allows teams to organize their work in a way that best suits their processes, making it a highly adaptable project management tool. Other options, such as visualizing commit history (which would fall under the 'Insights' feature), importing Gantt charts (which GitHub Projects does not natively support), or enforcing required fields (which might relate to form-based tools but not to GitHub Projects specifically), do not align with the key characteristics of GitHub Projects.

• Question 32:

  Workflows can reference actions in: (Each correct answer presents a complete solution. Choose three.)

  A. Any public repository.
  B. The same repository as your workflow file.
  C. GitHub Packages.
  D. An enterprise marketplace.
  E. A published Docker container image on Docker Hub.
  A. Any public repository.
  B. The same repository as your workflow file.
  E. A published Docker container image on Docker Hub.

  ---

  Explanation

  In GitHub Actions workflows, actions can be referenced from various sources depending on the needs of the workflow.

  Any Public Repository:

  Option A is correct. Actions can be referenced from any public GitHub repository, allowing the reuse of shared actions across multiple projects.

  The Same Repository as Your Workflow File:

  Option B is correct. Actions stored in the same repository as the workflow file can be referenced directly, which is common for custom actions specific to that project.

  A Published Docker Container Image on Docker Hub:

  Option E is correct. Workflows can reference actions that are provided as Docker container images hosted on Docker Hub, allowing integration of complex tools and environments.

  Incorrect Options:

  Option C (GitHub Packages) is incorrect as it is more commonly used for storing and managing dependencies, not actions. Option D (An enterprise marketplace) is incorrect because GitHub Actions are not directly referenced from an

  enterprise marketplace but rather from public repositories or Docker images.

  References: GitHub Docs: Reusing Workflows

• Question 33:

  From the Organization settings, which restrictions can organization owners place on GitHub Actions usage? (Each answer presents a complete solution. Choose three.)

  A. Allow actions that use self-hosted runners.
  B. Allow an action to be run from a Codespace.
  C. Allow specified actions.
  D. Allow actions by Marketplace verified creators.
  E. Allow actions created by GitHub.
  A. Allow actions that use self-hosted runners.
  C. Allow specified actions.
  D. Allow actions by Marketplace verified creators.

  ---

  Explanation

  Organization owners on GitHub have control over how GitHub Actions can be used within their organization. They can enforce restrictions to ensure security and compliance with organizational policies.

  Allow Actions That Use Self-Hosted Runners:

  Option A is correct because organization owners can configure the usage of self-hosted runners, allowing greater control over the environment where actions are run.

  Allow Specified Actions:

  Option C is correct because organization owners can allow only specific actions to run, adding a layer of security by limiting actions to those that have been vetted.

  Allow Actions by Marketplace Verified Creators:

  Option D is correct because organization owners can choose to allow actions created by GitHub Marketplace verified creators, ensuring that only trusted actions are used.

  Incorrect Options:

  Option B is incorrect because GitHub Actions are not designed to be run directly from a Codespace; Codespaces are for development environments. Option E is a valid choice, but since the prompt asks for only three answers, it is not

  included in this response.

  References: GitHub Docs: Managing GitHub Actions Settings for Your Organization

• Question 34:

  Which of the following best describes a Codespace?

  A. A lightweight editing experience that runs entirely in your browser
  B. An AI pair programmer that offers autocomplete-style suggestions
  C. A development environment hosted in the cloud
  D. A Visual Studio Code plug-in to manage local devcontainers
  C. A development environment hosted in the cloud

  ---

  Explanation

  A Codespace is a cloud-hosted development environment provided by GitHub. It allows developers to code in a fully-configured environment that can be accessed from any device with an internet connection. Codespaces integrate with Visual

  Studio Code, either through the desktop app or directly in the browser, providing a consistent development experience without the need to manually set up a local environment.

  Cloud-Hosted Development Environment:

  Option C is correct because GitHub Codespaces are essentially cloud-based environments that are pre-configured with the tools and dependencies needed for development. This allows developers to start coding immediately without the

  overhead of setting up a local environment.

  Incorrect Options:

  Option A is partially correct in that Codespaces can be accessed and used in a browser, but the defining feature is that it's a full development environment, not just a lightweight editor.

  Option B is incorrect because this describes GitHub Copilot, not Codespaces.

  Option D is incorrect because Codespaces is not a Visual Studio Code plug-in; it is a cloud-based service that integrates with Visual Studio Code.

  References:

  GitHub Docs: About GitHub Codespaces

• Question 35:

  In GitHub, why is it recommended to deploy from your feature branch before merging into the main branch?

  A. To directly deploy changes from the main branch without any intermediate testing
  B. To speed up the process of merging changes into the main branch
  C. To avoid the need for testing changes in production
  D. To ensure the changes are verified and validated in a production environment
  D. To ensure the changes are verified and validated in a production environment

  ---

  Explanation

  It is recommended to deploy from your feature branch before merging into the main branch to ensure the changes are verified and validated in a production environment. This practice helps in identifying any potential issues or bugs in a real-world scenario before the changes are permanently integrated into the main branch. By deploying from the feature branch, developers can catch and address issues early, reducing the risk of introducing bugs into the main branch, which is usually considered the stable branch.

• Question 36:

  Which of the following are displayed in the "Pinned Repositories" section of a GitHub user profile?

  A. Repositories with the most recent activity
  B. Repositories that were personally selected to be highlighted
  C. Repositories that are owned by organizations in which the user is a member
  D. Repositories with the highest number of stars
  B. Repositories that were personally selected to be highlighted

  ---

  Explanation

  The "Pinned Repositories" section of a GitHub user profile displays repositories that were personally selected to be highlighted by the user. Users can choose which repositories they want to feature prominently on their profile, regardless of recent activity, star count, or organizational ownership.

• Question 37:

  How can a user choose to receive ongoing updates about a specific activity on GitHub.com?

  A. By automatically watching all repositories you have push access to
  B. By upgrading from a free to a paid account
  C. By subscribing to notifications for all activity in a repository
  D. By customizing the types of notifications you will receive in the future
  C. By subscribing to notifications for all activity in a repository

  ---

  Explanation

  On GitHub, you can choose to receive ongoing updates about specific activities by subscribing to notifications for all activity in a repository. This allows you to stay informed about all changes, discussions, and updates related to a particular project. Additionally, GitHub provides the ability to customize notifications to suit your preferences.

• Question 38:

  Which of the following describes a branch in Git?

  A. A pointer to an identical snapshot of the project at a specific point in time
  B. A physical copy of the entire project stored on disk
  C. A new repository that shares code with the original "upstream" repository
  C. A new repository that shares code with the original "upstream" repository

  ---

  Explanation

  In Git, a branch is a fundamental concept that represents an independent line of development within a project. Here's a more detailed explanation:

  Branch in Git:

  Option C is correct because a branch in Git is essentially a separate, isolated copy of the project's codebase where you can make changes without affecting the main codebase. Branches allow developers to work on features, fixes, or

  experiments in parallel to the main project.

  Other Options:

  Option A is incorrect because while a branch does point to a specific commit (which represents a snapshot of the project), the description lacks the emphasis on the isolated and parallel development aspect that is critical to the understanding

  of branches.

  Option B is incorrect because a branch is not a physical copy stored on disk; it is a logical

  reference within the repository.

  Option D is incorrect because that description better fits the concept of a fork, not a branch. A fork is a new repository that is a copy of another repository, usually used to contribute back to the original ("upstream") repository.

  References:

  Git Documentation: Branches in a Nutshell

  GitHub Docs: Understanding the GitHub Flow

• Question 39:

  What are advantages of GitHub Projects over GitHub Projects Classic? (Each answer presents a complete solution. Choose two.)

  A. GitHub Projects has multiple layout views.
  B. GitHub Projects has Insights.
  C. GitHub Projects are Copilot enabled.
  D. GitHub Projects can be connected to third-party tools.
  A. GitHub Projects has multiple layout views.
  B. GitHub Projects has Insights.

  ---

  Explanation

  GitHub Projects is a newer, more powerful version of project management within GitHub, offering enhanced features over the classic version.

  Multiple Layout Views:

  Option A is correct because GitHub Projects supports multiple views, such as board, table, and timeline views, allowing users to visualize their work in different ways according to their needs.

  Insights:

  Option B is correct because GitHub Projects provides insights and analytics, enabling teams to track progress and make data-driven decisions.

  Incorrect Options:

  Option C is incorrect because while GitHub Copilot is a tool for code suggestions, it is not directly integrated with GitHub Projects as a feature. Option D is incorrect because both GitHub Projects and GitHub Projects Classic can be connected

  to third-party tools, so it is not an exclusive advantage of the newer GitHub Projects.

  References: GitHub Docs: Managing Projects

• Question 40:

  What are the key areas of focus for GitHub? (Each answer presents a complete solution. Choose three.)

  A. Nurturing a community that supports open source principles
  B. Providing access and opportunities for developers
  C. Providing a social media platform for project managers
  D. Building a technology platform for secure code sharing and collaboration
  E. Hosting video calls with other developers
  A. Nurturing a community that supports open source principles
  B. Providing access and opportunities for developers
  D. Building a technology platform for secure code sharing and collaboration

  ---

  Explanation

  GitHub focuses on several key areas that align with its mission to support developers and foster collaboration:

  Nurturing a Community That Supports Open Source Principles:

  Option A is correct. GitHub is a major advocate for open-source software development, providing tools and platforms that enable open collaboration. GitHub hosts millions of open-source projects and supports a community-driven approach to

  software development.

  Providing Access and Opportunities for Developers:

  Option B is correct. GitHub provides a wide range of resources, such as GitHub Education, GitHub Actions, and GitHub Marketplace, to empower developers. These tools and opportunities help developers of all levels to learn, contribute, and

  improve their skills.

  Building a Technology Platform for Secure Code Sharing and Collaboration:

  Option D is correct. GitHub’s core function is to provide a platform where developers can securely share code and collaborate. Features like private repositories, branch protections, and GitHub Actions for CI/CD (Continuous Integration/

  Continuous Deployment) workflows highlight this focus.

  Incorrect Options:

  Option C is incorrect because GitHub is not a social media platform for project managers; it is a code hosting platform with social features primarily aimed at developers.

  Option E is incorrect because GitHub does not focus on hosting video calls. While some integrations might allow for video conferencing, it is not a core focus of GitHub.

  References: GitHub Docs: The GitHub Developer Experience GitHub

  Docs: About GitHub This detailed explanation covers the primary focuses of GitHub, emphasizing its role in the open-source community and its commitment to providing a secure and collaborative platform for developers.