Get GitHub fundamentals – Administration basics and product features. Microsoft Quiz Answers
In this learning path, learn the basics of GitHub administration and discover the products that GitHub offers.
Prerequisites:
Familiarity with personal and organizational authentication technologies and processes would be helpful
Enroll on Microsoft
Module 1: Introduction to GitHub
Learn to use key GitHub features, including issues, notifications, branches, commits, and pull requests.
Learning objectives:
In this module, you will:
- Communicate with the project community in issues
- Manage notifications for project events
- Create branches to manage work in parallel
- Make commits to update project source
- Introduce changes with pull requests
- Deploy a web page to GitHub Pages
Prerequisites:
Quiz 1: Knowledge check
Q1. What is the best way to report a bug to a GitHub project?
- Send an email to a project owner.
- I don’t bother reporting software bugs because there’s no transparency and they never get fixed anyway.
- Search for the bug in the project’s existing issues and create a new one if it hasn’t been reported yet.
Q2. Suppose you have created a bug fix on a new branch and want it to become part of the next production build generated from the main
branch. What should you do next?
- Copy your branch changes and commit them directly to the
main
branch. - Create a pull request to merge your new branch into the
main
branch. - On second thought, maybe I won’t share this fix. I’ll just put it in my own private version of the source code.
Q3. Suppose you’d like to work with a project on GitHub but you don’t have write access to the project. What can you do to contribute?
- Fork the project’s repository to your GitHub account, clone the forked repository to your local machine, push changes to your repository, and submit a pull request to the target (upstream) repository.
- Clone the project to your local machine and push updates directly to the project repository.
- Use git commands to make a copy of the project so that you can work locally. Submit an issue to get your changes into the target repository.
Module 2: Introduction to GitHub administration
Understand the security and control measures available to GitHub administrators within an organization or enterprise.
Learning objectives:
By the end of this module, you will be able to:
- Summarize the organizational structures and permission levels that GitHub administrators can use to organize members in order to control access and security.
- Identify the various technologies that enable a secure authentication strategy allowing administrators to centrally manage repository access.
- Describe the technologies required to centrally manage teams and members using existing directory information services and how GitHub can itself be used as an identity provider for authentication and authorization.
Prerequisites:
- Familiarity with GitHub, repositories, and the basics of managing individual accounts is required
- Familiarity with personal and organizational authentication technologies and processes would be helpful
Quiz 1: Knowledge check
Q1. You want to grant a user the permissions required to add and remove organization members to a team. Which permission would you need to grant that user?
- The admin permission on a repository
- The maintain permission on a repository
- Organization billing manager
- Team maintainer
Q2. As an organization owner, you want to ensure that everyone who is signed in to your corporate network can access the GitHub website without requiring a second sign-in. Which technology will you enable to accomplish this?
- Single Sign-On
- Two-factor authentication
- SSH Keys
- Personal Access Tokens
Q3. What is the appropriate repository permission level for contributors who will actively push changes to your repository?
Module 3: Introduction to GitHub’s Products
Overview GitHub’s products, associated features, and licensing of per-use and metered features.
Learning objectives:
After completing this module, you will be able to:
- Explain the difference between each GitHub product, and which features are available with each product.
- Make key distinctions between plans, account types, teams, repository permissions, organization permission levels, and so on.
- Describe licensing terms for GitHub Actions, GitHub Packages, and Codespaces.
Prerequisites:
- Familiarity with GitHub, repositories, and the basics of managing individual accounts is required
- A high-level familiarity with GitHub’s product plans and features would be helpful, but not required
Quiz 1: Knowledge check
Q1. You plan on using GitHub Actions to build, test, and deliver your cross-platform code. Which of the following platforms will be the most expensive to use?
Q2. When would you decide to upgrade to the GitHub Enterprise product?
- Because you want to use GitHub Actions and Codespaces.
- Because your VP needs to use GitHub Insights.
- Because you want to centrally manage users and repositories across multiple organizations.
- Because you want to use the team pull request reviewers feature.
Q3. What is the purpose of a team?
- A team allows you to manage an organization account.
- A team allows you to control permission levels for an enterprise.
- A team allows a single user to log in using different accounts credentials.
- A team is intended to reflect a company or group’s structure, and is used to provide cascading access permissions and make it easy to notify all team members via mentions
Conclusion:
I hope this GitHub fundamentals – Administration basics and product features. Microsoft Quiz Answers would be useful for you to learn something new from this problem. If it helped you then don’t forget to bookmark our site for more Coding Solutions.
This Problem is intended for audiences of all experiences who are interested in learning about Data Science in a business context; there are no prerequisites.
Keep Learning!
More Coding Solutions >>
LeetCode Solutions
Hacker Rank Solutions
CodeChef Solutions