Microsoft GH-900 Online Practice Questions and Exam Preparation

Microsoft GH-900 Online Questions & Answers

• Question 41:

  What qualifier finds issues that mention a certain user?

  A. mentions:
  B. Smentioned:
  C. mentioned:
  D. threads:
  A. mentions:

  ---

  Explanation

  The qualifier mentions: is used in GitHub's search functionality to find issues that mention a certain user. For example, if you want to find all issues where a specific user is mentioned, you would use mentions:username. This helps in tracking where a user has been involved in discussions across issues or pull requests.

• Question 42:

  Which of the following options is available as a default Discussion category?

  A. Bug report
  B. Daily check-in
  C. Show and tell
  D. Security concern
  C. Show and tell

  ---

  Explanation

  In GitHub Discussions, several default categories are provided to help organize conversations within a project. One of the default categories is Show and tell. This category is designed for users to showcase their work, share progress, or discuss achievements with the community. The other options listed (Bug report, Daily check-in, Security concern) are not default categories but could be custom categories created by the repository maintainers.

• Question 43:

  When using Organizations, GitHub Teams is better than GitHub Free because it offers: A. Advanced tools and insights in private repositories.

  B. Authentication with SAML single sign-on and increased GitHub Actions minutes.

  C. Expanded storage and priority support.

  D. Increased GitHub Actions minutes and additional GitHub Packages storage.

  Correct Answer. B
  B

  ---

  Explanation

  GitHub Teams, as part of GitHub’s paid plans, offers additional features and capabilities compared to GitHub Free, particularly for organizations.

  GitHub Teams Benefits:

  Option B is correct because GitHub Teams provides advanced security features like SAML single sign-on for secure authentication, as well as increased minutes for running GitHub Actions, which are essential for continuous integration and

  deployment workflows.

  Incorrect Options:

  Option A is incorrect because private repositories and advanced tools are features available, but the key differentiator in this context is the SAML SSO and additional GitHub Actions minutes.

  Option C is incorrect because while expanded storage and priority support are valuable, SAML SSO and increased GitHub Actions minutes are more central to the differences between GitHub Free and GitHub Teams. Option D is partially

  correct, but since the question asks for the best reason, Option B provides the most critical features that differentiate GitHub Teams from GitHub Free.

  References:

  GitHub Docs: About GitHub Teams

• Question 44:

  Which of the following information is available by default in a user's GitHub profile?

  A. Personal biography and profile picture
  B. Public Secure Shell Protocol (SSH) keys
  C. A list of the user's private repositories
  D. Email address and password
  A. Personal biography and profile picture

  ---

  Explanation

  A user's GitHub profile typically includes public information such as a personal biography, profile picture, and a list of public repositories. More sensitive information, like email addresses and passwords, is not publicly displayed.

  Personal Biography and Profile Picture:

  Option A is correct because these are standard elements displayed on a user's public GitHub profile. This information is meant to provide a brief introduction to the user and their interests or skills.

  Incorrect Options:

  Option B is incorrect because public SSH keys may be associated with a user's account but are not displayed by default on the profile page.

  Option C is incorrect because private repositories are not listed on a public profile.

  Option D is incorrect because a user's email address and password are private information and not displayed on their public profile.

  References:

  GitHub Docs: Managing Your Profile

• Question 45:

  What is a benefit of using GitHub Enterprise Cloud with Enterprise Managed Users (EMU)?

  A. It provides centralized control and streamlined management of user accounts through their identity provider (IdP).
  B. It offers additional collaboration and content creation capabilities for managed user accounts.
  C. It automatically validates user interactions using the identity provider (IdP) conditional access policy (CAP).
  D. It enables GitHub user accounts access to protected resources using SAML SSO.
  A. It provides centralized control and streamlined management of user accounts through their identity provider (IdP).

  ---

  Explanation

  GitHub Enterprise Cloud with Enterprise Managed Users (EMU) integrates closely with an organization's identity provider (IdP), such as Azure Active Directory, to manage user accounts. The primary benefit of this setup is centralized control and streamlined management. It allows organizations to enforce policies, manage user permissions, and provision or deprovision accounts directly through their IdP, ensuring consistency and security across the organization. This approach is ideal for large enterprises that require tight control over their users and resources.

• Question 46:

  How are commits related to pull requests?

  A. Commits are made on a branch that can have a linked pull request.
  B. Commits can only be made after a pull request is created.
  C. Commits can only be made before a pull request is created.
  D. Commits are made on a pull request that can have a linked branch.
  A. Commits are made on a branch that can have a linked pull request.

  ---

  Explanation

  Commits and pull requests (PRs) are fundamental concepts in Git and GitHub workflows, particularly in collaborative software development.

  Commits:

  Commits are individual changes or updates made to the codebase. Each commit is identified by a unique SHA-1 hash and typically includes a commit message describing the changes.

  Commits are made to a specific branch in the repository. The branch could be the main branch, or more commonly, a feature branch created for specific work or a feature.

  Pull Requests (PRs):

  A pull request is a mechanism for developers to notify team members that a branch is ready to be merged into another branch, usually the main branch.

  PRs are used to review code, discuss changes, and make improvements before the branch is merged into the target branch.

  Relationship Between Commits and PRs:

  Option A is correct because commits are made on a branch, and this branch can have a pull request associated with it. The pull request tracks the branch’s commits and allows for code review before merging into the target branch.

  Commits can be added to the branch both before and after the pull request is created. Any new commits pushed to the branch are automatically included in the pull request.

  Incorrect Options:

  Option B is incorrect because commits can be made both before and after a pull request is created.

  Option C is incorrect because it suggests that commits can only be made before a pull request is created, which is not true.

  Option D is incorrect because commits are not made on a pull request; they are made on a branch. The pull request links a branch to another branch (e.g., feature branch to the main branch).

  References: GitHub Documentation: About Pull

  Requests GitHub Docs: Understanding the GitHub Flow Git Documentation: Git Basics - Getting a Git Repository

• Question 47:

  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

  As mentioned in the answer to Question no. 66, GitHub Actions workflows can reference actions from a variety of sources:

  Any Public Repository:

  Option A is correct. Actions can be sourced from any public GitHub repository.

  The Same Repository as Your Workflow File:

  Option B is correct. Actions within the same repository as the workflow file can be referenced directly.

  A Published Docker Container Image on Docker Hub:

  Option E is correct. Workflows can also use actions provided as Docker container images from Docker Hub.

  Incorrect Options:

  Option C and D are not relevant for directly referencing actions in workflows.

  References:

  GitHub Docs: Reusing Workflows

• Question 48:

  Which of the following best describes GitHub Pages?

  A. Webpages hosted and published through GitHub repositories
  B. Handles pagination for API requests
  C. Hosts long-form documentation about your project
  D. Curated guides around how to use GitHub products
  A. Webpages hosted and published through GitHub repositories

  ---

  Explanation

  GitHub Pages is a feature provided by GitHub that allows you to create webpages hosted and published through GitHub repositories. It is commonly used for hosting project documentation, personal websites, or blogs directly from a GitHub repository. It integrates seamlessly with the repository, making it easy to deploy and manage website content.

• Question 49:

  What are the defining features of Git?

  A. Distributed version control, open source software, and being designed for handling projects of any size with efficiency
  B. Sequential version control, cloud-based hosting service, and being designed for collaboration on large projects
  C. Low-cost local branching, convenient staging areas, multiple workflows, and being designed for managing small projects
  D. Centralized version control, proprietary software, and being designed for small projects
  A. Distributed version control, open source software, and being designed for handling projects of any size with efficiency

  ---

  Explanation

  Git is a widely-used version control system that has several defining features:

  Distributed Version Control:

  Git is a distributed version control system, meaning that every developer has a full copy of the entire repository, including its history, on their local machine. This enables greater flexibility, as work can be done offline and each user has access

  to the full project history.

  Open Source Software:

  Git is open-source, meaning its source code is freely available for use, modification, and distribution. This fosters a large community of users and contributors who continuously improve the software.

  Efficiency with Large Projects:

  Git is designed to handle projects of any size with speed and efficiency. It can manage large codebases and many contributors without significant performance degradation, making it suitable for everything from small personal projects to

  large, complex software systems.

  Incorrect Options:

  Option B is incorrect because Git is not a sequential version control system, nor is it inherently tied to cloud-based services. GitHub, GitLab, and other platforms offer cloud hosting for Git repositories, but Git itself is a version control tool.

  Option C is incorrect because Git is not limited to small projects; it is designed to scale efficiently, and the other features mentioned are only partial descriptions of Git's capabilities. Option D is incorrect because Git is not a centralized version

  control system; it is distributed. Additionally, Git is open-source, not proprietary, and is used for projects of all sizes.

  References:

  Pro Git Book: What is Git?

  Git Documentation: Distributed Version Control

  GitHub Docs: Understanding the Git Workflow

• Question 50:

  What is the minimum access needed to contribute to a repository?

  A. Read
  B. Triage
  C. Maintain
  D. Write
  D. Write

  ---

  Explanation

  To contribute to a GitHub repository, a user typically needs to be able to create branches, push changes, and open pull requests. These actions require Write access, which is the minimum level of access needed to contribute code directly to

  a repository.

  Write Access:

  Option D is correct because "Write" access allows users to contribute to the repository by pushing changes, creating branches, and opening pull requests. This is the minimum required access level for contributing code.

  Incorrect Options:

  Option A (Read) is incorrect because "Read" access only allows viewing the repository, not making changes. Option B (Triage) is incorrect because while Triage access allows managing issues and pull requests, it does not allow pushing

  code.

  Option C (Maintain) is incorrect because "Maintain" access includes additional permissions beyond those needed for basic contributions, such as managing repository settings.

  References:

  GitHub Docs: Repository Roles for an Organization