[2026年08月05日]GH-900テスト準備できるトレーニング練習テスト試験問題
試験問題解答ブレーン問題集でGH-900試験問題集PDFを使おう
質問 # 25
Which of the following are characteristics of GitHub Teams? (Choose two.)
- A. Teams has a maximum size of 100 users.
- B. Teams requires access to at least one repository.
- C. Teams can be nested.
- D. Team visibility can be visible or secret.
正解：C、D
解説：
[B] You can reflect your group or company's hierarchy within your GitHub organization with multiple levels of nested teams. A parent team can have multiple child teams, while each child team only has one parent team. You cannot nest secret teams.
[C] Team visibility
Teams can be visible or secret:
Visible teams can be viewed and @mentioned by every organization member.
Secret teams are only visible to the people on the team and people with owner permissions.
They're great for hiding teams with sensitive names or members, such as those used for working with external partners or clients. Secret teams cannot be nested under parent teams or have child teams.
Reference:
https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams
質問 # 26
How can a user resume an existing Codespace that is bound to a repository? (Choose two.)
- A. Open https://github.com/codespaces in the browser, select the repository, and then select the existing Codespace.
- B. Use the git CLI with the codespace parameter (e.g., "git codespace code -web").
- C. Browse to the repository in GitHub.com and press the period "." key.
- D. Browse to the repository in GitHub.com, press the comma "," key and select Resume this codespace.
正解：A、D
解説：
Opening an existing codespace
You can reopen a codespace that you have closed or stopped and return to your work.
You can reopen any of your active or stopped codespaces on GitHub, in Visual Studio Code, or by using GitHub CLI.
[C] Opening an existing codespace from the "Your codespaces" page
1. In the top-left corner of GitHub, select , then click Codespaces to take you to the "Your codespaces" page at github.com/codespaces.
2. To open a codespace in your default editor, click the name of the codespace. You can set your default editor for Codespaces in your personal settings page.
[D, not A] Resuming a codespace from a repository page
You can quickly resume a codespace when you're viewing a repository on GitHub.
With the Code tab of your repository displayed on GitHub, press , (the comma key).
The "Resume codespace" page is displayed. This allows you to resume your most recently used codespace for the currently selected branch of the repository or, if you were viewing a pull request, for the topic branch of the pull request.
Incorrect:
[Not B] If you have installed GitHub CLI, you can use it to work with GitHub Codespaces.
In a terminal, enter one of the following GitHub CLI commands.
To open a codespace in VS Code, enter:
gh codespace code
Etc.
Reference:
https://docs.github.com/en/codespaces/developing-in-a-codespace/opening-an-existing- codespace
質問 # 27
Which of the following are available statuses of a pull request?
(Each answer presents a complete solution. Choose four.)
- A. Open
- B. Closed
- C. Merged
- D. Draft
- E. Rebasing
- F. Modified
正解：A、B、C、D
解説：
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.
References:
GitHub Docs: About Pull Requests
質問 # 28
What template types are available when creating an issue template? (Each correct answer presents part of the solution. Choose three.)
- A. Security notification
- B. Standard template
- C. Feature request
- D. Custom template
Bug report
正解：B、C、D
質問 # 29
As a user, what feature can you use to add an issue to the top of the Issues page for easier visibility?
- A. Pin the issue.
- B. Star the issue.
- C. Label the issue.
- D. Subscribe to the issue.
正解：A
質問 # 30
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 offers a way for companies to purchase software on GitHub.
- D. It funds the most popular open source projects based on stars.
正解：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.
References:
GitHub Docs: GitHub Sponsors
質問 # 31
Which three of the following types of sensitive information can GitHub Secret Scanning detect? Each answer presents a complete solution.
- A. Passwords
- B. API keys
- C. Database connection strings
- D. Hardcoded email addresses
- E. SSH private keys
- F. Code formatting issues
正解：B、C、E
解説：
GitHub Secret Scanning helps protect repositories by detecting committed credentials and other sensitive values that should not be exposed in source code. SSH private keys are sensitive because they can allow unauthorized access to servers or repositories. API keys are also critical because they can grant access to external services, cloud platforms, or applications. Database connection strings may expose usernames, passwords, hosts, or database endpoints, making them dangerous if leaked. Secret Scanning is designed to identify these kinds of credential patterns and alert repository maintainers or security teams. Hardcoded email addresses are usually not treated as secrets, and code formatting issues are handled by linters or code quality tools, not Secret Scanning.
質問 # 32
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. Documentation
- C. Question
- D. Help wanted
正解：D
解説：
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.
質問 # 33
What qualifier finds issues that mention a certain user?
- A. mentions:
- B. Smentioned:
- C. mentioned:
- D. threads:
正解：A
解説：
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.
質問 # 34
From the Organization settings, which restrictions can organization owners place on GitHub Actions usage? (Choose three.)
- A. Allow actions by Marketplace verified creators.
- B. Allow specified actions.
- C. Allow actions that use self-hosted runners.
- D. Allow actions created by GitHub.
- E. Allow an action to be run from a Codespace.
正解：A、B、C
解説：
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.
質問 # 35
You are working on a new project on your local machine called "Git and GitHub tutorial." You have created a folder for the project on your desktop and added a todo.txt file inside it. You now want Git to start tracking changes in this folder. What steps should you take to correctly initialize the Git repository and configure Git for this project? (Choose two.)
- A. Use git start to initialize the Git repository
- B. Run git init inside the "Git and GitHub tutorial" folderright
- C. Create a GitHub repository before initializing Git locally
- D. Run git config --global user.name "YourName" and git config --global user.email
"[email protected]"right
正解：B、D
解説：
A establishes the repository, and C ensures your identity is configured properly for commits.
Option A is CORRECT because this command initializes a new Git repository in your project folder, allowing Git to start tracking changes. It's the first step in setting up version control for a new project.
Option C is CORRECT because these commands set your global Git user name and email, ensuring that all commits you make are correctly attributed to you. This is essential for collaboration and tracking contributions.
References:
https://docs.github.com/en/get-started/using-git/about-git
https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup
質問 # 36
Which of the following types of charts can a user create to get GitHub Projects insights? (Each answer presents a complete solution. Choose two.)
- A. current charts
- B. pie charts
- C. Gantt charts
- D. historical charts
- E. forecast charts
正解：A、D
質問 # 37
What are advantages of GitHub Projects over GitHub Projects Classic?
(Each answer presents a complete solution. Choose two.)
- A. GitHub Projects can be connected to third-party tools.
- B. GitHub Projects has multiple layout views.
- C. GitHub Projects has Insights.
- D. GitHub Projects are Copilot enabled.
正解：B、C
解説：
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.
Reference:
GitHub Docs: Managing Projects
質問 # 38
As a user, what feature can you use to merge proposed changes in a repository on GitHub?
- A. Projects
- B. Discussions
- C. Issues
- D. Pull requests
正解：D
解説：
The feature you can use to merge proposed changes in a repository on GitHub is Pull requests. Pull requests are a core feature of GitHub, allowing developers to propose changes to a codebase, review code, discuss the changes, and eventually merge them into the main branch. This collaborative workflow ensures that code is reviewed and vetted before becoming part of the project.
質問 # 39
Which of the following is an Innersource development practice?
- A. Making all repositories publicly accessible
- B. Adopting open source code into the organization
- C. Sharing code between teams within the organization
- D. Removing open source code from the organization
正解：C
解説：
Innersource is a development practice where an organization adopts open-source development methodologies within its own internal environment. The primary goal of innersource is to break down silos and encourage collaboration across different teams within the organization.
Sharing Code Between Teams:
Option B is correct because innersource involves sharing code between teams within the organization, similar to how open-source communities share code across the public domain. This practice fosters collaboration, improves code quality, and allows for reuse of code, reducing duplication of efforts.
質問 # 40
......
無料ダウンロードMicrosoft GH-900リアルな試験問題で合格しよう：https://jp.fast2test.com/GH-900-premium-file.html
GH-900試験問題集、GH-900練習テスト問題：https://drive.google.com/open?id=1S3fcDUFuERby8ow2yFuNwQSML4Ej3w5E