GitHub Administration Certification Quiz 3

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. How can an organization admin set default permissions for new members in a GitHub organization?

In the Access section of the organization's settings, select Member privileges, then under Base permissions, choose a permissions level and confirm the change.

By individually setting permissions for each new member as they are added to the organization, with no default level available.

Default permissions are automatically determined by GitHub based on the organization's activity and cannot be manually set.

Default permissions for new members are set through a GitHub API call specifying the desired base permission level for the organization.

#2. How does team synchronization with Microsoft Entra ID (previously Azure AD) benefit GitHub Enterprise Cloud organizations?

It enables GitHub to serve as an identity provider for Microsoft Entra ID, streamlining user authentication processes.

It automatically converts Microsoft Entra ID group memberships into corresponding GitHub repositories, facilitating resource allocation.

It allows for automatic reflection of membership changes in the IdP group on GitHub, reducing the need for manual updates and custom scripts by synchronizing teams in GitHub organizations with IdP groups.

It backs up GitHub organization data to Microsoft Entra ID servers, providing an additional layer of data redundancy.

#3. What are the implications of a managed user needing to contribute to resources outside of the enterprise?

Managed users must request special permission from GitHub to contribute to external resources.

Managed users can freely contribute to public resources and external enterprises without restrictions.

Managed users are not allowed to contribute to public resources, and they need a separate personal account for this purpose.

Contributions to external resources are automatically managed by the enterprise's IdP.

#4. What is SCIM in the context of GitHub?

SCIM is a user management system exclusive to GitHub, allowing users to customize their profiles and repositories. In GitHub, SCIM works by providing a platform-specific interface for these customizations.

SCIM is a GitHub-specific tool used for enhancing the network performance of GitHub servers. It works by managing internet bandwidth and traffic within the GitHub ecosystem, ensuring optimal performance for all users.

SCIM, or System for Cross-domain Identity Management, is a protocol designed to automate identity provisioning and management. In GitHub, SCIM integrates with external Identity Providers (IdPs) to manage GitHub Enterprise Cloud organization memberships, using a base URL for SCIM endpoints to perform operations like listing, inviting, and updating user identities.

SCIM stands for System for Cross-domain Identity Management. It's a protocol that GitHub uses to manage internal database systems, focusing mainly on securing data and user information without integrating with any external systems.

#5. What's the purpose of SCIM and team synchronization in GitHub?

Both team synchronization and SCIM in GitHub are used for user provisioning services, inviting non-members to join organizations and managing public profiles and repositories.

Team synchronization connects GitHub teams with IdP groups for membership management, relying on SAML single sign-on, whereas SCIM automates identity provisioning and management across systems, including creating and updating user identities and access.

Team synchronization is an automated process that allows users to manage their public profiles and repositories through a GitHub-specific interface.

Team synchronization is used for internal data security and user information management, while SCIM is an interface for user profile and repository customization.

#6. What are valid authentication methods available in GitHub? (Choose six.)

Select all that apply:

Authentication via social media accounts like Facebook or Google

Personal access token (PAT)

SAML SSO for enterprise accounts

Username and password (with optional 2FA)

Passkey authentication (opt-in beta for passwordless login)

SSH KEY

OAuth tokens for third-party app integrations

QR code system linked to a mobile device

#7. How does GitHub Enterprise Cloud differ from GitHub Enterprise Server?

GitHub Enterprise Cloud is hosted by GitHub, while GitHub Enterprise Server is hosted on your own servers

GitHub Enterprise Cloud is hosted on your servers, while GitHub Enterprise Server is hosted by GitHub

GitHub Enterprise Cloud is designed for individual use, while GitHub Enterprise Server is for organizations

GitHub Enterprise Cloud offers only public repositories, while GitHub Enterprise Server offers private repositories

#8. Which of the following are extra features provided by GitHub Enterprise Cloud over GitHub Free plan? (Choose four.)

Select all that apply:

Automatic code review for every push

Additional GitHub Actions minutes

Privately published GitHub Pages sites

Unlimited private repositories for individual users

Free public repositories for all users

Ability to restrict email notifications to verified domains

SAML authentication

#9. What is the purpose of enterprise accounts in GitHub Enterprise Cloud?

To offer free access to GitHub Enterprise Server

To provide administrators with a single point of visibility and management across multiple organizations

To allow users to manage their public and private contributions separately

To provide individual users with unlimited private repositories

#10. Which of the following is a management option exclusive to GitHub Enterprise Cloud?

Forcing all users to adopt a uniform coding standard

Allowing users to create and manage their own personal accounts without restrictions

Using Enterprise Managed Users to create and manage user accounts through your IdP

Requiring all code to be reviewed by GitHub before being published

#11. Which is the main restriction of Enterprise Managed User accounts in GitHub Enterprise Cloud?

They require administrator approval to create or join organizations outside the enterprise.

Access to third-party integrations is limited and must be approved by an enterprise administrator.

They are restricted to a single organization within the GitHub Enterprise account.

They cannot interact with public repositories outside their enterprise.

#12. What is GitHub Enterprise Server primarily designed for?

A service for deploying and managing containerized applications

A cloud-based software development platform for open-source projects

A self-hosted platform for software development within your enterprise

A platform for individual developers to host personal projects

#13. What is a key difference between enabling SAML Single Sign-On (SSO) for all organizations in an enterprise account versus enabling it for a single organization in GitHub Enterprise Cloud?

There is no difference in the implementation of SAML SSO between a single organization and all organizations in an enterprise account.

Enabling SAML SSO for all organizations requires separate authentication for each organization.

Enabling SAML SSO for all organizations limits repository access to internal collaborators only.

SAML SSO for a single organization allows for different IdPs for each organization, whereas enabling it for all organizations mandates a single IdP for the entire enterprise.

#14. Which GitHub Support level provides SLA and written support in English 24/7?

GitHub Community Support

GitHub Premium Support

GitHub Standard Support

GitHub Enterprise Support

#15. What are the steps to enable and enforce SAML SSO for a single organization?

Navigate to Your organizations, choose Settings, click on Authentication security, select Enable SAML authentication, configure IdP settings, test SAML configuration, and enforce SAML SSO.

Access Organization Settings, click Security, enable SAML SSO, add IdP URL, test the configuration, and opt to enforce SAML SSO upon successful testing.

In the main menu, select Organization, then Security Settings, enable SAML SSO, fill in the IdP details, test the SSO configuration, and then enforce SAML SSO.

Go to Organization Settings, select Security, choose SAML Authentication, enter IdP information, perform a test of the SAML configuration, and enforce SAML SSO.

#16. Which of the following identity providers (IdPs) is NOT officially supported and internally tested by GitHub Enterprise Cloud for SAML SSO?

Active Directory Federation Services (AD FS)

Shibboleth

Google Identity Platform

Microsoft Entra ID

#17. How do you require two-factor authentication (2FA) for an organization?

Send an email to all organization members asking them to manually enable 2FA on their accounts.

Go to the organization's page, click on Members, and individually set up 2FA for each member.

In the organization's settings, under Security, select Authentication security, and then choose Require two-factor authentication for everyone in your organization.

In your organization's settings, under Billing, select Require two-factor authentication for billing managers only.

#18. Which identity providers (IdPs) support GitHub Enterprise Cloud SCIM API for organizations? (Choose three.)

Select all that apply:

Microsoft Entra ID

Google Identity Platform

OneLogin

Amazon Cognito

Okta

Auth0

Keycloak

#19. What is the primary function of Enterprise Managed Users in GitHub?

To centrally manage identity and access of enterprise members on GitHub from an identity provider (IdP).

To provide a platform for individual developers to manage their private projects.

To allow users to manage their own profile information and repository access independently.

To enable users to create public content and collaborate with other users on GitHub.

#20. How are user accounts provisioned with Enterprise Managed Users?

User accounts are provisioned by GitHub without any input from the enterprise's IdP.

User accounts are created manually by each user on GitHub.com.

User accounts are automatically generated based on public email addresses.

User accounts are provisioned by the enterprise's IdP, with access provided to GitHub Enterprise Cloud.

#21. What is required for a user to authenticate with an Enterprise Managed Users account?

Users authenticate through a public GitHub login page without any enterprise interference.

Authentication is bypassed for enterprise managed users for ease of access.

Users must authenticate on the enterprise's IdP to access resources on GitHub.com.

Users provide a special GitHub-managed authentication token.

#22. Which statement is true regarding usernames and profile information for Enterprise Managed Users?

Usernames and profile information are set by the users themselves during the GitHub account setup.

GitHub automatically assigns random usernames and profile information for enhanced security.

Usernames and profile information are set through the enterprise's IdP and cannot be changed by the users.

Users can change their usernames and profile information at any time on GitHub.

#23. As a GitHub Organization administrator, you want users to authenticate using a corporate identity provider. Which of the following is a way to achieve this?

Corporate SSH Keys

Setup SAML SSO

Setup MFA

Setup OAuth SSO

#24. What is the GitHub dependency graph?

It is a representation of a repository's dependencies and dependents.

It is a GitHub maintained list of known vulnerabilities in open source software packages.

It is a tool that automatically proposes version updates to dependencies in a repository.

There is no such thing as the GitHub dependency graph.

#25. Which is the minimum level of support that provides help with installing and using Advanced Security?

GitHub Standard Support

GitHub Community Support

GitHub Premium Support

GitHub Enterprise Support

#26. Which of the following issues can GitHub Support help resolve? (Choose four.)

Select all that apply:

Technical advice on third-party integrations like Jira

Guidance on writing/debugging new queries for CodeQL

Installing and using GitHub Enterprise Server

Identifying and verifying the causes of suspected errors

Installing and using Advanced Security

Help with external CI/CD tools such as Jenkins

Assistance with GitHub account and billing queries

#27. Which of the following are correct methods to generate and share a diagnostic file for GitHub Enterprise Server? (Choose two.)

Select all that apply:

Use the ghe-support-bundle command to create and upload the diagnostic file.

Create a diagnostic file from the Management Console by navigating to the Support tab and clicking Download diagnostics info.

Generate a diagnostic file using the GitHub mobile app.

Run the ghe-diagnostics -u command to create and automatically upload the diagnostic file to GitHub Support.

Use the ghe-diagnostics command-line utility to retrieve the diagnostics for your instance.

#28. Which of the following is the correct procedure for generating a support bundle in GitHub Enterprise Server? (Choose two.)

Select all that apply:

First, access the Settings in your enterprise account, click on License, and under GitHub Enterprise Help, select Upload a support bundle. This will automatically generate and download the support bundle.

Generate and download a support bundle directly to your local machine via SSH using the ghe-support-bundle -o > support-bundle.tgz CLI command.

Navigate to your GitHub Enterprise Server instance, select the Site admin page, then Management Console. Choose Support in the top navigation bar and click Download support bundle.

Click your profile, then Your enterprises. In the enterprise account sidebar, select Settings and under License, click Generate a support bundle. This will create and download the bundle.

#29. Which endpoints does the GitHub API provide to administer your enterprise? (Choose six.)

Select all that apply:

Projects

Code security and analysis

SCIM

Marketplace

Billing

Audit log

Admin stats

License

#30. What are the steps to install a GitHub App from GitHub Marketplace for an organization?

Download the app from an external site and manually upload it to your GitHub organization's repositories.

Contact GitHub support to manually install the app, then configure it via email instructions.

Browse GitHub Marketplace, select the app, choose a plan, select the organization, and then review and install the app.

Install the app directly from the organization's dashboard without selecting any specific plan.

#31. What are the benefits and risks of using apps and actions from the GitHub Marketplace?

Benefits include official support from GitHub; risks include limited functionality and lack of customization options.

Benefits are limited to user interface improvements; risks include high costs and increased system complexity.

Benefits include automation of workflows and enhanced functionality; risks include potential security vulnerabilities and dependency on third-party services.

The only benefit is the ease of installation; risks involve complete access to codebase and data.

#32. What are the key implications of enabling SAML single sign-on (SSO) for an organization in GitHub Enterprise Cloud?

Enabling SAML SSO requires members to authenticate through GitHub, not the IdP.

SAML SSO allows organization owners to control and secure access to organization resources.

Once SAML SSO is enabled, public repositories become inaccessible.

SAML SSO restricts repository access to only those with a linked SAML identity.

Finish

Results

pass

Post Views: 5

fail

Post Views: 5

Post Views: 5