2026年最新のGH-900試験問題集で最近更新された77問題 [Q33-Q52]

2026年最新のGH-900試験問題集で最近更新された77問題

Microsoft GH-900リアル2026年最新のブレーン問題集で模擬試験問題集

質問 # 33
Which of the following best describes GitHub Pages?

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

正解：B

解説：
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.

質問 # 34
New open source contributors can receive funding from GitHub sponsors:

A. After setting up a sponsored developer profile.
B. Equal to 95% of the contribution value.
C. Using PayPal as a payment processor.
D. By including GitHub matching funds.

正解：A

解説：
GitHub Sponsors allows developers and organizations to financially support open-source contributors directly on the GitHub platform.
Setting Up a Sponsored Developer Profile:
Option D is correct because before a contributor can receive funding through GitHub Sponsors, they need

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

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

正解：D

解説：
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.
Reference:
GitHub Docs: Managing Your Profile

質問 # 36
Which of the following is a key characteristic of GitHub Projects?

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

正解：C

解説：
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.

質問 # 37
Where should a repository admin navigate to view pre-built visualizations from repository data?

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

正解：B

解説：
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." Reference:
GitHub Docs: Viewing Repository Insights

質問 # 38
What should be done to locate an existing action that was provided by a GitHub-approved vendor?
(Each correct answer presents part of the solution. Choose two.)

A. Create a new workflow file.
B. Search the GitHub Marketplace for Actions by the vendor.
C. Install the GitHub App that was provided by the vendor.
D. Search the vendor's website for a github.yaml index.
E. Add the vendor as an allowed Actions Source.
F. Confirm that the action has a verification badge.

正解：B、F

解説：
To locate an existing GitHub Action provided by a GitHub-approved vendor, you can use the following methods:
Verification Badge:
Option C is correct because actions provided by GitHub-approved vendors will typically have a verification badge. This badge indicates that the action is from a trusted source, giving users confidence in its security and reliability.
Search the GitHub Marketplace:
Option F is correct because GitHub Marketplace is the official location to find and install actions, including those provided by third-party vendors. You can search for actions by the vendor's name to find the specific one you need.
Incorrect Options:
Option A is not necessary to locate an existing action; creating a workflow file is for implementing the action, not locating it.
Option B is incorrect because searching the vendor's website for a github.yaml index is not a standard practice for finding actions.
Option D is incorrect because installing a GitHub App is unrelated to finding an existing action.
Option E is incorrect because adding a vendor as an allowed Actions Source is a configuration step for using the action, not for locating it.
Reference:
GitHub Marketplace: Verified Actions

質問 # 39
Where can you go to discover, browse, and install tools?

A. GitHub Apps
B. Organization settings
C. Explore
D. GitHub Marketplace

正解：D

解説：
The GitHub Marketplace is the place where users can discover, browse, and install various tools and integrations that extend the functionality of GitHub. These tools can include CI/CD services, security checks, and other development utilities that enhance workflow automation and project management.

質問 # 40
What qualifier finds issues that mention a certain user?

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

正解：D

解説：
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.

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

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

正解：B、C、D

解説：
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.
Reference:
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.

質問 # 42
Which of the following can be performed within GitHub Mobile?

A. Managing notifications from github.com
B. Chat with other GitHub Mobile users via voice calling
C. Utilizing the mobile device as a self-hosted runner
D. Managing enterprise and organization settings
E. Forking and cloning repositories

正解：A

解説：
GitHub Mobile provides a streamlined experience for managing your GitHub notifications and participating in discussions, but it does not offer full functionality compared to the desktop or web interface.
Managing Notifications:
Option E is correct because GitHub Mobile allows users to manage notifications, keeping them up to date with their repositories, issues, pull requests, and other activities on GitHub.
Incorrect Options:
Option A is incorrect because GitHub Mobile cannot be used as a self-hosted runner.
Option B is incorrect because managing enterprise and organization settings is not supported in GitHub Mobile.
Option C is incorrect because GitHub Mobile does not offer a chat or voice calling feature.
Option D is incorrect because forking and cloning repositories are not actions available in GitHub Mobile.
Reference:
GitHub Docs: GitHub Mobile

質問 # 43
What are primary benefits of using GitHub issues templates?
(Each answer presents a complete solution. Choose two.)

A. To provide an easy-to-fill-out form for creating new issues
B. To easily coerce existing issues into a standard format
C. To automatically create new branches when issues are created
D. To automatically label or assign newly created issues

正解：A、D

解説：
The primary benefits of using GitHub issues templates include:
A . To automatically label or assign newly created issues: Issue templates can be configured to automatically apply labels or assign users when the issue is created, helping to streamline triage and management processes.
B . To provide an easy-to-fill-out form for creating new issues: Templates provide a standardized format for submitting issues, ensuring that all necessary information is captured and reducing the need for follow-up questions.
Coercing existing issues into a standard format or automatically creating new branches when issues are created are not functions provided by GitHub issues templates.

質問 # 44
Which of the following are included as pre-defined repository roles?
(Each answer presents a complete solution. Choose three.)

A. Maintain
B. Delete
C. Triage
D. Write
E. View
F. Security

正解：A、C、D

解説：
GitHub provides several pre-defined repository roles that determine the level of access and permissions a user has within a repository. The roles that are included by default are:
Triage: Allows users to manage issues and pull requests without write access to the code.
Maintain: Provides more extensive access, including managing settings, but without full administrative control.
Write: Grants permission to push changes and manage issues and pull requests.
Roles like "Security" and "Delete" are not standard pre-defined roles, and "View" is generally referred to as "Read" in GitHub's permission structure.

質問 # 45
What best describes Markdown?

A. Version control system
B. Containerization solution
C. Programming language
D. Markup language
E. Scripting language

正解：D

解説：
Markdown is a lightweight markup language with plain-text formatting syntax. It is designed to be easy to write and read in its raw form, and it can be converted into HTML and other formats. Markdown is commonly used for formatting readme files, writing messages in online discussion forums, and creating rich text documents.
Markup Language:
Option A is correct because Markdown is indeed a markup language. It is not a programming language, scripting language, version control system, or containerization solution.
Incorrect Options:
Option B is incorrect because Markdown is not a programming language; it does not involve control structures or variables.
Option C is incorrect because Markdown is not used for scripting or automation.
Option D is incorrect because Markdown does not manage version control.
Option E is incorrect because Markdown is not related to containerization technologies like Docker.
Reference:
GitHub Docs: Basic writing and formatting syntax

質問 # 46
What is the purpose of GitHub Sponsors?

A. It allows the developer community to financially support open source projects.
B. It provides a channel for GitHub to support open source projects.
C. It funds the most popular open source projects based on stars.
D. It offers a way for companies to purchase software on GitHub.

正解：A

解説：
GitHub Sponsors is a program designed to provide a platform for developers and companies to financially support open-source projects and their maintainers.
Financial Support for Open Source Projects:
Option D is correct because the main purpose of GitHub Sponsors is to allow members of the developer community, including individuals and organizations, to financially support open-source projects and maintainers. This helps sustain open-source development by providing developers with the resources they need to continue their work.
Incorrect Options:
Option A is incorrect because GitHub Sponsors is not based on project popularity (e.g., stars); it is based on voluntary contributions.
Option B is incorrect because while GitHub provides the platform, the purpose of GitHub Sponsors is not for GitHub itself to fund projects, but to enable the broader community to do so.
Option C is incorrect because GitHub Sponsors is not a marketplace for purchasing software but a platform for supporting developers.
Reference:
GitHub Docs: GitHub Sponsors

質問 # 47
What is the difference between an organization member and an outside collaborator?

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

正解：A

解説：
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." Reference:
GitHub Documentation: Roles in an organization
GitHub Documentation: About outside collaborators
GitHub Documentation: Managing repository access for your organization

質問 # 48
Which of the following is the best GitHub feature for long-form documentation for a project?

A. Projects
B. Insights
C. Wikis
D. Pull Requests

正解：C

解説：
GitHub offers a variety of features for different aspects of project management and documentation. For long-form documentation, the best feature is Wikis. Wikis in GitHub allow you to create detailed, structured documentation that is easy to navigate and edit. Each repository in GitHub can have its own Wiki, which acts as a space for collaborators to maintain project documentation, guides, manuals, or any other long-form content.
Wikis are specifically designed to host extensive documentation in a way that is easy to reference and edit over time. They support Markdown, allowing you to format your documentation effectively. Unlike the other options, Wikis are explicitly intended for the purpose of long-form content, making them the best choice for this use case.

質問 # 49
Pull requests can only be created between two branches that are:

A. Different.
B. The same.
C. Authored by different users.
D. Authored by the same user.

正解：A

解説：
Pull requests are created to propose changes from one branch to another. These branches must be different; otherwise, there would be no changes to propose. Typically, pull requests are made from a feature or topic branch to a main branch (such as main or master), allowing for code review and integration before the changes are merged.

質問 # 50
What does a CODEOWNERS file do in a repository?

A. Defines access permissions for the repository
B. Restricts who can edit specific files
C. Requires peer code review for code changes
D. Sets the reviewers for pull requests automatically

正解：D

解説：
The CODEOWNERS file in a GitHub repository is used to define individuals or teams that are responsible for specific parts of the codebase. When changes are made to files or directories that match the patterns specified in the CODEOWNERS file, GitHub automatically requests reviews from the listed code owners.
Setting Reviewers Automatically:
Option D is correct because the primary purpose of a CODEOWNERS file is to automatically set reviewers for pull requests that affect the specified files or directories. This ensures that the appropriate team members are notified and review the changes before they are merged.
Incorrect Options:
Option A is incorrect because the CODEOWNERS file does not restrict who can edit specific files; it only influences who is required to review changes.
Option B is partially related but not fully accurate because while CODEOWNERS does require certain reviews, it does not mandate peer review for all code changes.
Option C is incorrect because the CODEOWNERS file does not define access permissions for the repository; it deals with code review processes.
Reference:
GitHub Docs: About CODEOWNERS
GitHub Blog: Automatically Requesting Reviews with CODEOWNERS

質問 # 51
Which of the following are available statuses of a pull request?
(Each answer presents a complete solution. Choose four.)

A. Draft
B. Merged
C. Modified
D. Closed
E. Rebasing
F. Open

正解：A、B、D、F

解説：
Pull requests (PRs) on GitHub can have several statuses that indicate their current state in the development and review process:
Draft:
Option A is correct. A pull request can be in a "Draft" status, indicating that it is a work in progress and not yet ready for review.
Closed:
Option B is correct. A pull request can be "Closed" without being merged, which might happen if the proposed changes are not needed or are incorporated differently.
Merged:
Option D is correct. A pull request that has been reviewed and approved can be "Merged" into the target branch, indicating that the changes have been successfully incorporated.
Open:
Option F is correct. An "Open" pull request is one that is active and awaiting review or further action.
Incorrect Options:
Option C (Rebasing) is incorrect because "Rebasing" is not a status; it's an operation that can be performed on branches.
Option E (Modified) is incorrect because there is no "Modified" status for pull requests.
Reference:
GitHub Docs: About Pull Requests

質問 # 52
......

Microsoft GH-900 認定試験の出題範囲：

トピック	出題範囲
トピック 1	Git と GitHub 入門：このセクションでは、ジュニア開発者とプラットフォームサポートスペシャリストのスキルを測定し、Git と GitHub の基礎知識を網羅します。Git とは何か、なぜ使われるのか、Git の基本的なワークフロー、そしてローカルとリモートの違いを含むリポジトリ関連の概念について説明します。受験者は、リポジトリの初期化とクローン作成、変更の追加とコミット、更新のプッシュとプル、ブランチとマージといった基本的な Git コマンドを学習します。また、アカウントの作成、リポジトリの管理、インターフェースの理解、問題やプルリクエストの処理といった GitHub の操作についても学習します。
トピック 2	GitHubコミュニティのメリット：このセクションは、コミュニティマネージャーとオープンソースコントリビューターを対象としており、GitHubコミュニティとの関わり方に焦点を当てています。受講者は、オープンソースプロジェクトへの参加方法、GitHubディスカッションを活用したコラボレーションとサポートの活用方法、そしてコミュニティ主導のプロジェクトへの有意義な貢献方法を学びます。
トピック 3	コラボレーション機能：このセクションでは、ソフトウェアエンジニアとチームリーダーのスキルを測定し、GitHub を使用したコラボレーションワークフローを網羅します。リポジトリのフォーク、プルリクエストの作成と管理、コード変更のレビューとマージ、GitHub Actions を使用した CI CD パイプラインのサポートなどが含まれます。また、課題の作成と管理、ラベル、マイルストーン、プロジェクトボードの使用、GitHub プロジェクトによる進捗状況の追跡といったプロジェクト管理機能についても学習します。
トピック 4	モダン開発：この領域では、DevOpsエンジニアと継続的インテグレーションスペシャリストがモダン開発プラクティスを実装する能力を評価します。DevOpsの原則を理解し、GitHub Actionsを活用した自動化とCI CDパイプラインの実装に重点を置きます。また、コードレビューの実施と管理に関するGitHubのツールとベストプラクティスも学習します。