GitHub Administration Certification Quiz 1

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. By which header can you check the number of requests you have made in the current rate limit window when using the GitHub REST API?

x-ratelimit-remaining

x-ratelimit-reset

x-ratelimit-resource

x-ratelimit-limit

x-ratelimit-used

#2. What are the differences and use cases between GitHub Packages and releases?

Releases are used for private software distribution, whereas GitHub Packages is exclusively for public package hosting.

GitHub Packages and releases are functionally identical, with no differences in use cases.

GitHub Packages require external CI/CD integration for distribution, unlike releases which are fully managed within GitHub.

GitHub Packages is optimized for hosting and managing packages, offering integrated permissions management and billing, while releases are for distributing software versions directly linked to Git tags.

#3. What is required to download or publish a GitHub Package within workflows, such as with GitHub Actions or other CI/CD tools?

GitHub Packages cannot be used in GitHub Actions workflows or any CI/CD tools.

Manual download and upload of packages is required for each workflow run.

Only SSH keys are required for using GitHub Packages in workflows.

Use GITHUB_TOKEN for publishing packages associated with the workflow repository, and a PAT for installing packages from private repositories.

#4. How can one authenticate GitHub Packages?

By authenticating using a PAT with appropriate scope

GitHub Packages can be accessed and shared publicly without any authentication.

Access to GitHub Packages is restricted to GitHub Enterprise accounts only.

By using the default GitHub login without needing any special authentication tokens.

#5. Which package managers and formats are supported by GitHub Packages? (Choose five.)

Select all that apply:

Docker and OCI images

Nuget for .NET

npm for JavaScript

Cargo for Rust

Poetry for Python

Maven and Gradle for Java

RubyGems for Ruby

#6. How can you use 3rd party vaults to manage secrets for GitHub Actions?

Direct integration with 3rd party vaults is supported natively within GitHub Actions without needing any additional configuration.

GitHub Actions does not support the use of 3rd party vaults for secret management; all secrets must be stored within GitHub.

Third party vaults should be accessed by embedding their API keys within the workflow files and using the API or CLI of that vendor.

Store secrets in the 3rd party vault and use a decryption step in your workflow to access them, with the decryption key stored as a GitHub Actions secret.

#7. Which runners must you use with GitHub Actions when an IP allow list is enabled on your enterprise?

Any runner without considering the IP address

Only GitHub-hosted standard runners

Self-hosted runners or GitHub-hosted larger runners with static IP address ranges

Only runners within the organization's network without IP restrictions

#8. How can you ensure your self-hosted or larger hosted runners can communicate with GitHub when using an IP allow list?

Use a VPN for all runners to bypass the IP allow list

Add the IP address or IP address range of your runners to the IP allow list configured for your enterprise

Disable the IP allow list for GitHub Actions runners

#9. When an Enterprise IP allow list is in place, what happens when you try publish your GitHub Pages site from a branch instead of using a custom GitHub Actions workflow?

You must manually trigger builds for GitHub Pages sites

GitHub Pages cannot be built or updated until the IP allow list is disabled

The build runner will be blocked from accessing the repository until manually added to the allow list

The build runner will have access to the repository for the GitHub Pages site by default

#10. What are some potential abuse vectors of enabling self-hosted runners on public repositories? (Choose four.)

Select all that apply:

Limited integration with GitHub-hosted services

Malicious programs running on the machine

Escaping the runner sandbox environment

Automatic environment cleanup after job execution can cause data loss

Exposing network environment

Lower computational efficiency due to security measures

Persisting dangerous data

#11. How should you select appropriate runners to support your workflow's specific workloads?

Use only self-hosted runners, regardless of workload complexity, to minimize costs.

Restrict to using GitHub-hosted runners with custom hardware configurations for better performance.

Choose self-hosted runners for customized environments or GitHub-hosted for automatic updates and clean instances.

Always prefer GitHub-hosted runners for all workloads to ensure maximum security.

#12. How do you add a self-hosted runner to a GitHub repository?

Use the GitHub API to send a request for adding a self-hosted runner without any manual configuration.

Navigate to the repository settings, select Actions, then Runners, and follow the instructions to download, configure, and run the self-hosted runner application.

Email GitHub support to request the addition of a self-hosted runner to your repository.

Directly clone the repository to your local machine and run a specific script to automatically add it as a self-hosted runner.

#13. What is required to add a self-hosted runner to an organization on GitHub?

Organization owner access, navigate to organization settings, select Actions, then Runners, and follow the setup instructions for the self-hosted runner.

Submit a form on GitHub's website to request the GitHub team to add a self-hosted runner to your organization manually.

Public repository access within the organization and manual script execution on the server intended as a runner.

General member access with no special permissions, and utilize GitHub Action to automatically register a self-hosted runner.

#14. How can you manage access to self-hosted runners in an organization using runner groups?

Use a single default runner group for all runners and repositories

By creating runner groups which are then assigned to teams of people within an organization. These teams can then manage these groups and assign the runner groups to repositories they manage

Create runner groups to collect sets of runners, then configure access policies for repositories within the organization.

Manually assign each self-hosted runner to individual repositories without using runner groups.

#15. What steps are involved in creating a self-hosted runner group for an organization on GitHub?

Contact GitHub support to request the creation of a runner group and provide a list of repositories for access configuration.

Navigate to organization settings, select Actions, click Runner groups, create a new group, and assign a repository access policy.

Use a GitHub Actions workflow to automatically generate runner groups based on repository activity and usage patterns.

In the .github repository modify the .gitconfig file to specify runner groups and associated access policies.

#16. How do you change which repositories can access a specific runner group in an organization?

Use the GitHub CLI to execute a command that reassigns repository access to different runner groups within the organization.

Repositories automatically gain access to all runner groups without the need for manual configuration changes.

Edit the runner group's configuration file located on the server hosting the self-hosted runners to update repository access.

In organization settings, navigate to Actions, select Runner groups, choose a group, and modify the repository access settings.

#17. Which of this best defines GitHub Enterprise Policies?

Guidelines suggested by GitHub to improve collaboration and productivity across all organizations without enforcement capabilities.

Settings managed by organization owners to control aspects like repository management, team access, and security features within their GitHub organization.

Default settings applied to all new repositories within an organization, which can be overridden by the organization owners.

Policies set at the enterprise level dictate the billing and subscription details for all organizations under an enterprise account.

#18. What are enterprise policies in the context of GitHub Enterprise Cloud?

A collection of recommended practices for open-source projects hosted on GitHub, aimed at enhancing community engagement and contribution.

Security protocols that automatically scan and fix vulnerabilities in the codebases across all repositories within the enterprise account.

Individual user settings that apply only to personal accounts within the GitHub Enterprise Cloud, unrelated to organizational or enterprise governance.

Enterprise policies mandate a uniform policy across all organizations within an enterprise, thereby eliminating the option for organizations to apply their own distinct policies.

#19. What steps should organization admins follow to access audit logs of actions performed within their GitHub organization?

Navigate to the main GitHub page, use the search bar to type "Organization audit logs" and expect GitHub to automatically download the log.

Directly email GitHub support to request an audit log be sent monthly to the organization's admin email.

Check individual member profiles for a summary of their actions, compile these summaries manually, and format them for auditing.

Select profile photo > Your organizations > Settings > Archives > Logs > Audit log. Then, use the Export dropdown to export as JSON or CSV.

#20. Which of the following types of access tokens supported by GitHub? (Choose three.)

Select all that apply:

Installation Access Token for a GitHub App

Personal Access Token (PAT)

IoT Token for an IoT device

User Access Token for a GitHub App

Ephemeral Access Token for temporary access

#21. What is the primary rate limit for authenticated personal users making REST API requests to GitHub API?

5,000 requests per hour

1,000 requests per hour

60 requests per hour

15,000 requests per hour

#22. What's the difference between GitHub Apps and OAuth apps?

GitHub Apps offer granular permissions to specific repositories, while OAuth Apps request access to user data across all repositories.

OAuth Apps offer more granular permissions compared to GitHub Apps.

GitHub Apps and OAuth Apps do not differ; they provide the same level of permissions.

GitHub Apps can only access public repositories, whereas OAuth Apps can access both public and private repositories.

#23. How can GitHub Apps react to specific events, and what are some examples of these events?

GitHub Apps use a websocket connection that notifies the GitHub app of all push and pull_request events.

GitHub Apps can subscribe to events like push, pull request, and issue events through the app's configuration.

GitHub Apps work on webhooks - receiving all events from GitHub. If the GitHub App should react only on specific event, that filtering is done within the GitHub App code.

GitHub Apps subscribe to events through webhooks, which notify the app of specific actions like pull request openings or issue creations.

#24. How can enterprises track their usage of GitHub Actions?

GitHub Actions usage cannot be tracked; enterprises must estimate usage based on developer feedback.

By manually counting workflow runs and jobs in each repository at the end of each month.

By using webhooks to subscribe to information about workflow jobs and runs, and potentially using a data archiving system.

Through unlimited access to GitHub's internal analytics dashboard without any additional configuration.

#25. Who can configure IP allow lists for an enterprise on GitHub?

Enterprise owners

Organization owners

Security Managers

Organization moderators

#26. Can organization owners manage IP allow list entries inherited from the enterprise account's allow list?

Yes, they have full control over inherited entries

No, they cannot manage entries inherited from the enterprise account's allow list

Yes, but only with approval from enterprise owners

No, only GitHub support can manage inherited entries

#27. Which repository role in a GitHub organization is recommended for contributors who need to proactively manage issues and pull requests without having write access?

Maintain

Read

Write

Triage

#28. What are the repository roles available in a GitHub organization? (Choose five.)

Select all that apply:

Maintain

Triage

Write

Admin

Read

Owner

Moderator

#29. What functionality does the audit log provide to organization admins within a GitHub organization?

Audit access grants the ability to approve or reject code changes before they are merged.

It provides a temporary permission set for performing administrative actions within a repository.

It enables organization admins to directly modify repository settings and enforce branch protection rules.

The audit log allows organization admins to review actions performed by members, including details such as who performed the action, what the action was, and when it was performed, aiding in security and compliance monitoring.

#30. Which formats are available for exporting the audit log from a GitHub organization?

ZIP.

PDF and DOCX.

TXT and RTF.

JSON and CSV.

#31. How can an organization admin search the audit log for events related to webhook modifications?

By using the operation qualifier in the search query, such as operation:modify to find events where an existing resource, like a webhook, was modified.

Filtering the audit log exclusively by date range without the ability to specify event types.

Using voice commands to verbally request a search for webhook modification events.

Directly typing 'webhook modifications' into the audit log search bar.

#32. Why might webhooks be considered an efficient alternative to the audit log or API polling in certain use cases within GitHub organizations?

Webhooks provide real-time notifications to your server when specific events occur, which can be more efficient than searching the audit log or polling the API for those events.

Webhooks are the only method to receive notifications about private repository actions.

They provide a more detailed and comprehensive log of events than the audit log.

Webhooks allow organization admins to manually review and approve each event before it is logged.

Finish

Results

pass

Post Views: 10

fail

Post Views: 10

Post Views: 10