必ず合格できるGitHub GitHub-Foundations試験の正確な75問題と解答あります
最新 [2024年12月20日]2024年最新の実際にある検証済みのGitHub-Foundations問題集
GitHub GitHub-Foundations 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
| トピック 6 |
|
質問 # 11
Workflows can reference actions in:
(Each correct answer presents a complete solution. Choose three.)
- A. Any public repository.
- B. A published Docker container image on Docker Hub.
- C. The same repository as your workflow file.
- D. GitHub Packages.
- E. An enterprise marketplace.
正解：A、B、C
解説：
As mentioned in the answer to Question no. 66, GitHub Actions workflows can reference actions from a variety of sources:
* Any Public Repository:
* Option Ais correct. Actions can be sourced from any public GitHub repository.
* The Same Repository as Your Workflow File:
* Option Bis correct. Actions within the same repository as the workflow file can be referenced directly.
* A Published Docker Container Image on Docker Hub:
* Option Eis correct. Workflows can also use actions provided as Docker container images from Docker Hub.
* Incorrect Options:
* Option CandDare not relevant for directly referencing actions in workflows.
References:
* GitHub Docs: Reusing Workflows
質問 # 12
Which of the following are available statuses of a pull request?
(Each answer presents a complete solution. Choose four.)
- A. Open
- B. Closed
- C. Modified
- D. Draft
- E. Merged
- F. Rebasing
正解：A、B、D、E
解説：
Pull requests (PRs) on GitHub can have several statuses that indicate their current state in the development and review process:
* Draft:
* Option Ais 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 Bis 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 Dis 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 Fis 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
質問 # 13
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 automatically validates user interactions using the identity provider (IdP) conditional access policy (CAP).
- C. It enables GitHub user accounts access to protected resources using SAML SSO.
- D. It offers additional collaboration and content creation capabilities for managed user accounts.
正解：A
解説：
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 iscentralized 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.
質問 # 14
Who can be assigned to an Issue or pull request?
(Each answer presents a complete solution. Choose two.)
- A. Anyone who has commented on the Issue or pull request
- B. Anyone who has a personal GitHub account
- C. Anyone with write permissions to the repository
- D. Anyone who has an enterprise GitHub account
正解：A、C
解説：
In GitHub, issues and pull requests (PRs) are essential tools for managing work and collaboration in a project.
Assigning individuals to these issues or PRs is a way to indicate responsibility for addressing the issue or completing the PR.
* Anyone with write permissions to the repository:
* Users who have write permissions to a repository can be assigned to issues and pull requests.
Write permissions allow users to push changes to the repository, create branches, and modify issues and pull requests. Assigning them to an issue or PR ensures they are recognized as responsible for the task.
* Anyone who has commented on the Issue or pull request:
* GitHub allows you to assign issues or pull requests to users who have already engaged with the discussion by commenting on it. This feature is particularly useful for quickly assigning tasks to those who are already involved in the conversation.
* Incorrect Options:
* Option Ais incorrect because having an enterprise GitHub account alone does not necessarily grant the ability to be assigned to issues or PRs. Permission to assign is based on repository-specific roles and permissions.
* Option Cis incorrect because not all personal GitHub accounts can be assigned to issues or PRs.
The user needs either write permissions to the repository or must have commented on the issue or PR.
References:
* GitHub Docs: Assigning Issues and Pull Requests
* GitHub Docs: Permission Levels for a Repository
This detailed explanation provides clarity on GitHub's assignment mechanics for issues and pull requests, reflecting the platform's collaborative nature.
質問 # 15
After 30 minutes of inactivity, a GitHub Codespace will:
- A. Be deleted
- B. Restart
- C. Time out
- D. Commit changes
正解：C
解説：
After 30 minutes of inactivity, a GitHub Codespace willtime out. This is designed to conserve resources when the Codespace is not being actively used. The session will be paused, and you'll need to reconnect to resume your work. However, the Codespace is not deleted, and any unsaved changes might not be lost but should be committed or saved to prevent data loss.
質問 # 16
What qualifier finds issues that mention a certain user?
- A. mentioned:
- B. threads:
- C. Smentioned:
- D. mentions:
正解：D
解説：
The qualifiermentions: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 usementions:username.
This helps in tracking where a user has been involved in discussions across issues or pull requests.
質問 # 17
As a user, what feature can you use to merge proposed changes in a repository on GitHub?
- A. Projects
- B. Issues
- C. Discussions
- D. Pull requests
正解：D
解説：
The feature you can use to merge proposed changes in a repository on GitHub isPull 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.
質問 # 18
Where can you go to discover, browse, and install tools?
- A. GitHub Marketplace
- B. Organization settings
- C. GitHub Apps
- D. Explore
正解：A
解説：
TheGitHub Marketplaceis 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.
質問 # 19
How can a user choose to receive ongoing updates about a specific activity on GitHub.com?
- A. By customizing the types of notifications you will receive in the future
- B. By upgrading from a free to a paid account
- C. By automatically watching all repositories you have push access to
- D. By subscribing to notifications for all activity in a repository
正解：D
解説：
On GitHub, you can choose to receive ongoing updates about specific activities bysubscribing 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.
質問 # 20
Which of the following best describes a Codespace?
- A. A Visual Studio Code plug-in to manage local devcontainers
- B. A lightweight editing experience that runs entirely in your browser
- C. A development environment hosted in the cloud
- D. An AI pair programmer that offers autocomplete-style suggestions
正解：C
解説：
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 Cis 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 Ais 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 Bis incorrect because this describes GitHub Copilot, not Codespaces.
* Option Dis 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
質問 # 21
In GitHub, why is it recommended to deploy from your feature branch before merging into the main branch?
- A. To speed up the process of merging changes into the main branch
- B. To directly deploy changes from the main branch without any intermediate testing
- C. To ensure the changes are verified and validated in a production environment
- D. To avoid the need for testing changes in production
正解：C
解説：
It is recommended to deploy from your feature branch before merging into the main branchto 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.
質問 # 22
Which of the following best describes GitHub Pages?
- A. Hosts long-form documentation about your project
- B. Webpages hosted and published through GitHub repositories
- C. Curated guides around how to use GitHub products
- D. Handles pagination for API requests
正解：B
解説：
GitHub Pagesis a feature provided by GitHub that allows you to createwebpages 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.
質問 # 23
Pull requests can only be created between two branches that are:
- A. The same.
- B. Different.
- C. Authored by the same user.
- D. Authored by different users.
正解：B
解説：
Pull requests are created to propose changes from one branch to another. These branches must bedifferent; otherwise, there would be no changes to propose. Typically, pull requests are made from a feature or topic branch to a main branch (such asmainormaster), allowing for code review and integration before the changes are merged.
質問 # 24
If there are multiple README files, which of the following locations will be displayed first?
- A. .github
- B. Root
- C. /src
- D. /docs
正解：B
解説：
When multipleREADMEfiles exist in different locations within a GitHub repository, theREADME.mdfile located in the root directory of the repository will be displayed first by default. This file serves as the main documentation for the repository and is automatically rendered on the repository's home page.
* Root Directory:
* Option Cis correct because theREADME.mdfile in the root directory is prioritized and displayed first on GitHub. This is the standard behavior for how GitHub presents documentation.
* Incorrect Options:
* Option A(.github) is incorrect because while aREADME.mdfile in the.githubdirectory might be used for certain configurations, it is not the first to be displayed.
* Option B(/src) is incorrect because theREADME.mdin thesrcdirectory is not prioritized over the root.
* Option D(/docs) is incorrect because documentation in the/docsfolder is typically secondary to the rootREADME.md.
References:
* GitHub Docs: About READMEs
質問 # 25
Which of the following statements most accurately describes who can access a private repository Wiki?
- A. Wikis will not be visible until shared with a specific user.
- B. Wikis can be viewed by the same people who have Read access to the repository.
- C. Wikis are only viewable by repository admins.
- D. Wikis are public regardless of whether you have access to the repository.
正解：B
解説：
For private repositories on GitHub, the Wiki is accessible to anyone who hasRead accessto the repository. This means that if you can view the code and files in the repository, you can also view its Wiki. This makes Wikis a useful tool for documenting projects in a way that is available to all collaborators without requiring special permissions beyond those needed to access the repository itself.
質問 # 26
The difference between GitHub Desktop and github.com is that Desktop:
- A. Enables integration with office suite applications.
- B. Is a standalone software application.
- C. Is a self-hosted version of GitHub.
- D. Offers a graphical user interface.
- E. Is only available on Windows operating systems.
正解：D
解説：
GitHub Desktop is a standalone application that provides a graphical user interface (GUI) for interacting with GitHub repositories, as opposed to the command-line or web-based interfaces available on github.com.
* Graphical User Interface:
* Option Dis correct because GitHub Desktop offers a GUI, making it easier for users to manage repositories, perform commits, and handle other Git-related tasks without needing to use the command line.
* Incorrect Options:
* Option Ais partially correct in that GitHub Desktop is a standalone application, but the key difference is the GUI.
* Option Bis incorrect because GitHub Desktop does not specifically enable integration with office suite applications.
* Option Cis incorrect because GitHub Desktop is available on both Windows and macOS.
* Option Eis incorrect because GitHub Desktop is not a self-hosted version of GitHub; it is a client application for accessing GitHub repositories.
References:
* GitHub Docs: GitHub Desktop Documentation
質問 # 27
From the list of projects for an organization, how can a user identify a GitHub Projects template?
- A. Select the Templates tab.
- B. View the contents in the .github/projects folder.
- C. Use the "is
" filter in the search text box. - D. Check the "show template" checkbox.
正解：A
解説：
In GitHub, when viewing the list of projects for an organization, a user can identify a GitHub Projects template byselecting the Templates tab. This tab specifically lists available templates that can be used to create new projects based on predefined structures and workflows.
質問 # 28
What is the primary purpose of creating a new branch in the GitHub flow?
- A. To incorporate changes from a review
- B. To create a backup of the main branch
- C. To capture information about an issue
- D. To experiment with new features or fixes
正解：D
解説：
In GitHub Flow, creating a new branch is a key step in the development process that allows for isolated development of new features or fixes without affecting the main codebase.
* Experimenting with New Features or Fixes:
* Option Cis correct. The primary purpose of creating a new branch in the GitHub flow is to provide a safe space to experiment with new features or fixes. This allows developers to work on changes independently and only merge them into the main branch after they have been reviewed and approved.
* Incorrect Options:
* Option A(To create a backup of the main branch) is incorrect because branches are not typically used for backups; they are for active development.
* Option B(To capture information about an issue) is incorrect because issues are tracked separately; branches are for code changes.
* Option D(To incorporate changes from a review) is incorrect because incorporating changes is done during the pull request process, not when creating a branch.
References:
* GitHub Docs: GitHub Flow
質問 # 29
......
無料でゲット！2024年最新のに更新されたGitHub GitHub-Foundations試験問題と解答：https://www.passtest.jp/GitHub/GitHub-Foundations-shiken.html
合格させるGitHub-Foundations試験には更新された75問題あります：https://drive.google.com/open?id=1Ed8TkGQZHpL_CTdkHnByY7yyr1YUYoEc