Microsoft GH-900 Online Practice Questions and Exam Preparation

Microsoft GH-900 Online Questions & Answers

• Question 21:

  Which of the following are advantages of saved replies? (Each correct answer presents part of the solution. Choose two.)

  A. Saved replies are tied to a GitHub user's personal account.
  B. Saved replies are allocated at the enterprise level for all users.
  C. Saved replies allow you to create a reusable response to issues and pull requests.
  D. Saved replies will send auto notifications when a user is tagged to an issue.
  A. Saved replies are tied to a GitHub user's personal account.
  C. Saved replies allow you to create a reusable response to issues and pull requests.

  ---

  Explanation

  Saved replies in GitHub are a feature that allows users to create and save templates of commonly used responses for issues and pull requests. This feature can significantly enhance productivity and ensure consistent communication.

  Saved Replies Are Tied to a User's Personal Account:

  Option A is correct because saved replies are specific to a user's GitHub account, meaning they are accessible to the user across all repositories they have access to.

  Saved Replies Allow Reusable Responses:

  Option C is correct because the primary purpose of saved replies is to allow users to create reusable responses for issues and pull requests, saving time and ensuring consistency.

  Incorrect Options:

  Option B is incorrect because saved replies are not allocated at the enterprise level; they are specific to individual user accounts. Option D is incorrect because saved replies do not send auto notifications; they are manually inserted by the

  user when responding to issues or pull requests.

  References: GitHub Docs: Using Saved Replies

• Question 22:

  What is the difference between an organization member and an outside collaborator?

  A. Organization base permissions do not apply to outside collaborators.
  B. Two-factor authentication (2FA) is not required for outside collaborators.
  C. Outside collaborators cannot be given the admin role on a repository.
  D. Outside collaborators do not consume paid licenses.
  A. Organization base permissions do not apply to outside collaborators.

  ---

  Explanation

  In GitHub, an organization member is a user who has been added to an organization and is subject to the organization's base permissions and policies. An outside collaborator is a user who is not a member of the organization but has been

  granted access to one or more repositories within the organization. Here’s the difference between an organization member and an outside collaborator:

  Organization Members:

  Members are subject to the organization's base permissions, which apply across all repositories within the organization. These permissions might include read, write, or admin access, depending on what has been set as the default.

  Members consume paid licenses if the organization is on a paid plan.

  Members are required to have two-factor authentication (2FA) if the organization enforces it.

  Outside Collaborators:

  Outside collaborators do not have organization-wide permissions. They only have access to specific repositories to which they have been granted permission. This means organization base permissions do not apply to them (making option A

  correct).

  Outside collaborators do not consume paid licenses. They are only counted toward the license if they are made organization members.

  Outside collaborators can be granted any level of permission, including the admin role on specific repositories.

  Two-factor authentication (2FA) can be enforced for outside collaborators at the repository level, depending on the organization's security settings. Given this information, option A is the correct answer: "Organization base permissions do not

  apply to outside collaborators."

  References:

  GitHub Documentation: Roles in an organization GitHub Documentation: About outside collaborators GitHub Documentation: Managing repository access for your organization

• Question 23:

  Which of the following is always true about the feature preview phases Alpha and Beta?

  A. Alpha features are not available to the public.
  B. Alpha features are documented.
  C. Alpha and Beta features offer Service Level Agreements (SLAs).
  D. Beta features provide technical support.
  A. Alpha features are not available to the public.

  ---

  Explanation

  The terms Alpha and Beta are often used in software development to describe different stages of feature testing and release.

  Alpha Features:

  Option A is correct because Alpha features are typically in the early stages of development and are not available to the public. They are usually tested internally or by a limited audience.

  Incorrect Options:

  Option B is incorrect because Alpha features are often undocumented as they are in the early development phase.

  Option C is incorrect because Alpha and Beta features usually do not offer Service Level Agreements (SLAs) due to their experimental nature.

  Option D is incorrect because Beta features might offer limited support, but it is not guaranteed, especially compared to fully released features.

  References:

  GitHub Docs: About Feature Previews

• Question 24:

  Where should a repository admin navigate to view pre-built visualizations from repository data?

  A. Settings
  B. Issues
  C. Insights
  D. Charts
  C. Insights

  ---

  Explanation

  GitHub provides repository admins with a feature called "Insights" where they can view various pre-built visualizations and analytics related to the repository.

  Insights:

  Option C is correct because the "Insights" tab in a GitHub repository offers various pre-built visualizations, including contributions, traffic, code frequency, dependency graphs, and more. This helps admins and maintainers track the project's

  activity and health.

  Other Options:

  Option A (Settings) is incorrect because the Settings tab is where you configure repository settings, permissions, and integrations, but it does not provide visualizations of repository data.

  Option B (Issues) is incorrect because the Issues tab is used for tracking bugs, enhancements, and other tasks but does not provide data visualizations.

  Option D (Charts) is incorrect as there is no "Charts" tab or section in GitHub. The correct location for data visualizations is under "Insights."

  References:

  GitHub Docs: Viewing Repository Insights

• Question 25:

  Which of the following statements most accurately describes secret gists?

  A. Anyone with the URL for the gist can view the gist.
  B. Secret gists require GitHub Enterprise.
  C. Anyone can see the gist from the gist Discover page.
  D. Users with assigned access can view the gist.
  A. Anyone with the URL for the gist can view the gist.

  ---

  Explanation

  Secret gists on GitHub are "unlisted" gists, meaning they are not publicly discoverable but can be viewed by anyone who has the URL.Visibility of Secret Gists:

  Option A is correct because secret gists can be viewed by anyone who has the direct URL, making them accessible yet unlisted.

  Incorrect Options:

  Option B is incorrect because secret gists do not require GitHub Enterprise; they are available on all GitHub accounts.

  Option C is incorrect because secret gists do not appear on the gist Discover page.

  Option D is incorrect because secret gists do not have an "assigned access" feature; access is determined by sharing the URL.

  References:

  GitHub Docs: About Gists

• Question 26:

  Which of the following is the purpose of a GitHub repository?

  A. To provide a folder that stores project files, including documentation, on your local machine
  B. To provide a version control system designed for small projects, offering simple tools for organizing files on your laptop
  C. To provide a cloud-based hosting service for project documentation, providing a secure and centralized location for file storage
  D. To provide a collaborative space where developers can share and manage code files, track changes, and store revision history
  D. To provide a collaborative space where developers can share and manage code files, track changes, and store revision history

  ---

  Explanation

  A GitHub repository serves as a collaborative space where developers can share and manage code files, track changes, and store revision history. It is much more than just a folder or simple tool; it is a comprehensive version control system that allows teams to collaborate effectively on codebases. Repositories enable developers to work together, manage contributions, review code, and maintain a complete history of every change made to the project.

• Question 27:

  As a user, which of the following default labels is used to indicate that a maintainer needs assistance on an issue or pull request?

  A. Enhancement
  B. Question
  C. Help wanted
  D. Documentation
  C. Help wanted

  ---

  Explanation

  In GitHub, labels are used to categorize issues and pull requests, and certain default labels are provided to help manage tasks:

  Help Wanted Label:

  Option C is correct. The "Help wanted" label is used to indicate that the maintainer of the repository needs assistance on a particular issue or pull request. This label helps in attracting contributors who might be interested in helping with

  specific tasks.

  Other Options:

  Option A ("Enhancement") is incorrect because it indicates a request for a new feature or improvement rather than a call for help. Option B ("Question") is incorrect because it is used to flag issues or pull requests that seek clarification or

  additional information, not necessarily requiring assistance.

  Option D ("Documentation") is incorrect because it labels issues or PRs related to documentation, not for seeking help.

  References:

  GitHub Docs: Using Labels

• Question 28:

  What are three valid states for a file in a git repository? (Each correct answer presents part of the solution. Choose three.)

  A. Committed
  B. Modified
  C. Uncommitted
  D. Staged
  E. Tracked
  A. Committed
  B. Modified
  D. Staged

  ---

  Explanation

  In a Git repository, a file can be in one of the following three valid states: Committed: The file is saved in the local repository. It is part of the permanent history of the project. Modified: The file has been changed but not yet staged or

  committed. It is in the working directory. Staged: The file has been marked to be included in the next commit. It is in the staging area, ready to be committed.

  These states represent the typical lifecycle of a file as it moves through the process of being edited, reviewed, and saved in Git.

• Question 29:

  Which of the following best describes GitHub flow?

  A. A branching model that uses feature branches and multiple primary branches
  B. A strategy where separate branches are created for each release, and pull requests are used to collaborate on and approve releases
  C. A lightweight workflow that allows for safe experimentation with new ideas and collaboration on projects through branching, pull requests, and merging
  D. A strict workflow that enforces a linear development process with all changes made directly on the main branch
  C. A lightweight workflow that allows for safe experimentation with new ideas and collaboration on projects through branching, pull requests, and merging

  ---

  Explanation

  GitHub Flow is a simple, yet powerful, branching strategy that is widely used in modern software development. It emphasizes collaboration and flexibility.

  GitHub Flow:

  Option C is correct because GitHub Flow is a lightweight workflow designed for safe experimentation and collaboration. It involves creating branches for new features or fixes, opening pull requests for review, and merging changes back into

  the main branch after approval.

  Incorrect Options:

  Option A is incorrect because GitHub Flow uses a single main branch, not multiple primary branches.

  Option B is incorrect because GitHub Flow is not specifically designed around releases; it is more focused on continuous development and integration.

  Option D is incorrect because GitHub Flow is not strict or linear; it encourages branching and pull requests rather than direct changes on the main branch.

  References:

  GitHub Docs: Understanding the GitHub Flow

  GitHub Guides: The GitHub Flow

• Question 30:

  What is the primary purpose of creating a security policy in a repository?

  A. To ensure that peer code review occurs before new changes are merged
  B. To define which types of secrets are blocked with push protection
  C. To describe how security vulnerabilities should be responsibly disclosed
  D. To customize the repository's Dependabot configuration
  C. To describe how security vulnerabilities should be responsibly disclosed

  ---

  Explanation

  The primary purpose of creating a security policy in a GitHub repository is to guide users and contributors on how to report security vulnerabilities in a responsible and secure manner. This policy outlines the preferred method of

  communication, timelines, and any other pertinent information related to handling security issues.

  Security Policy:

  Option C is correct because a security policy provides guidelines for responsibly disclosing security vulnerabilities. This helps maintainers respond to and address security concerns promptly and securely, thereby protecting the project and its

  users.

  Incorrect Options:

  Option A is incorrect because ensuring peer code review is a best practice for code quality, but it is not the primary purpose of a security policy.

  Option B is incorrect because push protection for secrets is managed through repository settings, not the security policy.

  Option D is incorrect because customizing Dependabot configuration is related to dependency management, not directly to security policies.

  References:

  GitHub Docs: Adding a Security Policy to Your Repository