GitHub Administration Certification Quiz 2

This exam is designed for system administrators, software developers, application administrators, and IT professionals with intermediate-level experience in GitHub Enterprise Administration. This is a practice quiz for the certification.

Total questions: 32
Time: 50 minutes
Passing score: 70%

START QUIZ

#1. Which tools can be used to remove sensitive data from a Git repository's history?

git filter-repo & BFG Repo-Cleaner

Git Stash & Git Checkout

Git Pull & Git Fetch

Git Merge & Git Rebase

#2. What should you do before running git filter-repo or BFG Repo-Cleaner to remove sensitive data from your repository?

Merge or close all open pull requests

Push all local changes to GitHub

Create a new branch

Delete the .git directory

#3. After sensitive data is removed from a repository's history and pushed to GitHub, what is a necessary step to fully remove the data from GitHub?

Rename the repository

Notify all users who have forked the repository

Change the repository's visibility to private

Contact GitHub Support to remove cached views and references

#4. Which of these practices can help avoid committing sensitive data or files to a git repository?

Using git add . before all commits

Disabling push access to the repository

Using a visual program like GitHub Desktop to review commits

Regularly changing your passwords

#5. How does the role of an outside collaborator differ from that of a member within a GitHub organization?

Outside collaborators can add or remove members from the organization.

Outside collaborators are assigned access on a repository-by-repository basis, while members may have broader permissions within the organization depending on their role.

There is no distinction in access levels between outside collaborators and members.

Outside collaborators have the capability to modify organization settings.

#6. How can an organization owner change the role of a member within the organization?

Role changes within an organization are not possible; a new organization must be created.

By navigating to the organization's settings, selecting Members, and then adjusting the member's role from the list.

Members can change their own roles within the organization settings.

By deleting and re-inviting the member with the desired role.

#7. How can you give a user the minimum required permissions necessary for accessing a specific repository within a GitHub organization?

It's not possible to grant users access to specific repositories; they must be given access to the entire organization.

Add the user as an outside collaborator to the repository with Read access, granting them the ability to clone the repository without allowing them to push changes.

Provide them with 'Write' access to all repositories in the organization to ensure they can contribute to projects.

Automatically grant them 'Owner' access to ensure they can manage organization settings and repository access.

#8. What are the key features and functionalities of teams within a GitHub organization?

Teams in GitHub organizations enable managing access and notifications for groups reflecting the company's structure, with capabilities for admin, read, or write access to repositories, mentioning for notifications, and the use of nested teams for hierarchical management.

GitHub teams are identical to organization members, with no distinct features or functionalities, such as access management or notifications.

Teams are solely for social networking within GitHub, allowing members of an organization to communicate and share updates without any impact on repository access or organizational notifications.

Teams within GitHub can include outside collaborators and are mainly used for external communication, without any internal organizational structure or repository access permissions.

#9. What distinguishes a visible team from a secret team in a GitHub organization?

There is no functional difference; the terms simply reflect the team's preference for communication.

Visible teams can be viewed and mentioned by any organization member, whereas secret teams are only visible to team members and organization owners, enhancing privacy for sensitive collaborations.

Secret teams can manage organization settings, unlike visible teams which can only manage repository settings.

Visible teams have access to all repositories by default, while secret teams do not have any repository access until explicitly granted.

#10. How do nested teams benefit an organization's structure within GitHub?

Members of nested teams have restricted access to communicate with members of their parent teams, enhancing security.

Nested teams complicate the organization's structure and should be avoided to simplify team management.

Child teams can override the access permissions of their parent teams, providing flexibility in access control.

Nested teams reflect the organization's hierarchy, inheriting access permissions from parent teams and streamlining permission management and communication across multiple levels of the organization.

#11. What can be found on a team’s page within a GitHub organization?

Financial reports related to the team's use of organization resources.

Team members, child teams, the team’s repositories, and access to team settings, including the ability to update the team’s description and profile picture.

External links to non-GitHub resources used by the team.

A live chat feature that allows real-time communication between team members.

#12. What is the role of a Security Manager within a GitHub organization?

A security manager has permissions to view security alerts and manage settings for code security across the organization, in addition to read permissions for all repositories.

Security managers exclusively manage two-factor authentication settings for all organization members.

Security managers are responsible for financial transactions and billing information security within the organization.

They can delete or transfer ownership of any repository within the organization for security reasons.

#13. What permissions does a GitHub App manager have within an organization?

They have the ability to grant app installation permissions to outside collaborators.

GitHub App managers can manage the settings of GitHub App registrations owned by the organization but do not have permissions to install or uninstall GitHub Apps.

They can access and modify the source code of any GitHub Apps owned by the organization.

GitHub App managers are the only roles that can create new GitHub Apps within the organization.

#14. What roles can a team member hold within a GitHub team?

Project manager, Contributor, Viewer

Billing manager, Security manager, App manager

Repository owner, Repository collaborator

Team maintainer, Team member

#15. What is the primary purpose of a GitHub organization?

To provide individual users with personal space to host their private projects.

To offer a platform for personal blogging and website hosting.

To allow businesses and open-source projects to collaborate across many projects at once with advanced security and administrative features.

To serve as a backup service for code repositories.

#16. Which role in a GitHub organization has the authority to manage access to the organization's resources?

Organization owner

Outside collaborator

Repository contributor

Team member

#17. How can access management and collaboration be simplified within a GitHub organization?

Limiting repository creation to organization owners only.

By granting all members owner-level permissions.

By creating nested teams that reflect the group's structure, with cascading access permissions and mentions.

Through the use of single sign-on (SSO) for all members exclusively.

#18. Which GitHub plan allows to use secret scanning in private repositories?

GitHub Enterprise Server

GitHub Team

GitHub Pro

GitHub Enterprise Cloud

Any GitHub Enterprise plan with a GHAS license

#19. What is the advantage of having an enterprise account on GitHub Enterprise Cloud for an organization?

It automatically enrolls the organization in a premium support plan.

It allows owners to centrally manage policy and billing for multiple organizations.

It offers a free domain for hosting the organization's website.

It provides unlimited private repositories for individual users.

#20. How can an organization enhance the security of their GitHub Actions workflows?

By requiring all members to use biometric authentication for accessing GitHub.

By making all repositories within the organization public to ensure transparency.

By disabling the creation and processing of issues and pull requests to reduce attack surfaces.

By adopting security practices like secure handling of secrets and regularly reviewing audit logs for anomalies.

#21. Which of the following are recognized roles within a GitHub organization?

Lead developers, Junior developers, Senior developers, Project owners

Project managers, Contributors, Observers, External consultants

System administrators, Database managers, IT support, External auditors

Organization owners, Organization members, Organization moderators, Billing managers, Security managers, GitHub App managers, Outside collaborators

#22. Which role in a GitHub organization has the highest level of access?

Owner

Member

Outside collaborator

Billing manager

#23. What are the default permissions of a member in a GitHub organization?

They have the ability to delete the organization.

Members can create private repositories (subject to the organization's policy) and participate in projects within the organization to which they are granted access.

They can manage billing information.

Members cannot interact with the organization's repositories until promoted to owner.

#24. What is the primary responsibility of a billing manager in a GitHub organization?

Creating and deleting all repositories within the organization.

Managing billing settings for the organization, including updating payment methods and reviewing invoices.

Assigning and removing organization owners.

They can manage team permissions and repository settings.

#25. Which environments can GitHub Enterprise Server be deployed to?

Directly onto personal computing devices

Exclusively to private cloud environments

On-premises data center or to a public cloud service (e.g., AWS, GCP, Azure)

Only on GitHub-managed servers

#26. Which of the following is a key feature of GitHub Enterprise Server?

Unlimited public and private repositories on GitHub.com

Automatic deployment to any cloud service provider

Runs on your infrastructure and governed by access and security controls you define

Free access to GitHub Actions and GitHub Packages

#27. How can GitHub Enterprise Server's administration be handled?

Via GitHub.com's web interface exclusively

Through third-party management tools only

Via browser, administrative SSH access, and REST or GraphQL APIs

Only through direct access to the server's console

#28. What does GitHub recommend for safeguarding against data loss in GitHub Enterprise Server?

Establishing a plan for disaster recovery and configuring backups

Using third-party cloud storage services for backup

Manual backup by exporting data to local storage periodically

Relying on GitHub's automatic cloud backup services

#29. What's the usage cost of GitHub Actions for public repositories?

Public repositories are given half the amount of free minutes compared to private repositories.

GitHub Actions is not available for public repositories.

GitHub Actions usage is free for public repositories.

GitHub Actions incurs a charge for every minute used in public repositories.

#30. How are minutes calculated for jobs that run on different operating systems in GitHub Actions?

All jobs, regardless of the operating system, consume minutes at the same rate.

Jobs on Windows and macOS consume minutes at 2 and 10 times the rate of jobs on Linux runners.

Jobs on Linux consume minutes at 2 and 10 times the rate of jobs on Windows and macOS runners.

Only jobs on macOS consume minutes at a different rate, 5 times that of Linux and Windows.

#31. What is the default spending limit for GitHub Actions on monthly-billed accounts?

The default spending limit varies based on the account's historical usage.

The default spending limit is 0$, preventing additional usage beyond the included amounts.

There is no default spending limit, and users are billed for any usage beyond the free tier.

The default spending limit is 50$, allowing some overage beyond the included amounts.

#32. How can an organization owner find statistics on license usage for their GitHub Enterprise Server?

By navigating to the Site admin dashboard to view the license usage under Enterprise account settings.

Through direct email requests to GitHub Support.

Checking the organization's public profile page for real-time stats.

Using the GitHub API to fetch real-time license usage data for GitHub Enterprise Server.

Finish

Results

pass

Post Views: 3

fail

Post Views: 3

Post Views: 3