diff --git a/content/questions/admin/question-067.md b/content/questions/admin/question-067.md
new file mode 100644
index 00000000..4a626496
--- /dev/null
+++ b/content/questions/admin/question-067.md
@@ -0,0 +1,12 @@
+---
+question: "Which tools can be used to remove sensitive data from a Git repository's history?"
+archetype: "questions"
+title: "Question 067"
+draft: false
+---
+
+> https://docs.github.com/en/github/authenticating-to-github/removing-sensitive-data-from-a-repository
+1. [x] git filter-repo & BFG Repo-Cleaner
+1. [ ] Git Merge & Git Rebase
+1. [ ] Git Stash & Git Checkout
+1. [ ] Git Pull & Git Fetch
diff --git a/content/questions/admin/question-068.md b/content/questions/admin/question-068.md
new file mode 100644
index 00000000..f271349a
--- /dev/null
+++ b/content/questions/admin/question-068.md
@@ -0,0 +1,12 @@
+---
+question: "What should you do before running git filter-repo or BFG Repo-Cleaner to remove sensitive data from your repository?"
+archetype: "questions"
+title: "Question 068"
+draft: false
+---
+
+> https://docs.github.com/en/github/authenticating-to-github/removing-sensitive-data-from-a-repository
+1. [x] Merge or close all open pull requests
+1. [ ] Delete the .git directory
+1. [ ] Create a new branch
+1. [ ] Push all local changes to GitHub
diff --git a/content/questions/admin/question-069.md b/content/questions/admin/question-069.md
new file mode 100644
index 00000000..1b3c26b0
--- /dev/null
+++ b/content/questions/admin/question-069.md
@@ -0,0 +1,12 @@
+---
+question: "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?"
+archetype: "questions"
+title: "Question 069"
+draft: false
+---
+
+> https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository#fully-removing-the-data-from-github
+1. [x] Contact GitHub Support to remove cached views and references
+1. [ ] Notify all users who have forked the repository
+1. [ ] Change the repository's visibility to private
+1. [ ] Rename the repository
diff --git a/content/questions/admin/question-070.md b/content/questions/admin/question-070.md
new file mode 100644
index 00000000..c2d43c47
--- /dev/null
+++ b/content/questions/admin/question-070.md
@@ -0,0 +1,12 @@
+---
+question: "Which of these practices can help avoid committing sensitive data or files to a git repository?"
+archetype: "questions"
+title: "Question 070"
+draft: false
+---
+
+> https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository#avoiding-accidental-commits-in-the-future
+1. [x] Using a visual program like GitHub Desktop to review commits
+1. [ ] Regularly changing your passwords
+1. [ ] Disabling push access to the repository
+1. [ ] Using `git add .` before all commits
diff --git a/content/questions/admin/question-071.md b/content/questions/admin/question-071.md
new file mode 100644
index 00000000..b485f61a
--- /dev/null
+++ b/content/questions/admin/question-071.md
@@ -0,0 +1,12 @@
+---
+question: "Which of these best defines GitHub Enterprise Policies?"
+archetype: "questions"
+title: "Question 071"
+draft: false
+---
+
+> https://docs.github.com/en/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise
+1. [x] Settings managed by organization owners to control aspects like repository management, team access, and security features within their GitHub organization.
+1. [ ] Policies set at the enterprise level that dictate the billing and subscription details for all organizations under an enterprise account.
+1. [ ] Guidelines suggested by GitHub to improve collaboration and productivity across all organizations without enforcement capabilities.
+1. [ ] Default settings applied to all new repositories within an organization, which cannot be modified by the organization owners.
diff --git a/content/questions/admin/question-072.md b/content/questions/admin/question-072.md
new file mode 100644
index 00000000..fb5edb2d
--- /dev/null
+++ b/content/questions/admin/question-072.md
@@ -0,0 +1,12 @@
+---
+question: "What are enterprise policies in the context of GitHub Enterprise Cloud?"
+archetype: "questions"
+title: "Question 072"
+draft: false
+---
+
+> https://docs.github.com/en/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise
+1. [x] Enterprise policies mandate a uniform policy across all organizations within an enterprise, thereby eliminating the option for organizations to apply their own distinct policies.
+1. [ ] Individual user settings that apply only to personal accounts within the GitHub Enterprise Cloud, unrelated to organizational or enterprise governance.
+1. [ ] A collection of recommended practices for open-source projects hosted on GitHub, aimed at enhancing community engagement and contribution.
+1. [ ] Security protocols that automatically scan and fix vulnerabilities in the codebases across all repositories within the enterprise account.
diff --git a/content/questions/admin/question-073.md b/content/questions/admin/question-073.md
new file mode 100644
index 00000000..a943718a
--- /dev/null
+++ b/content/questions/admin/question-073.md
@@ -0,0 +1,12 @@
+---
+question: "What steps should organization admins follow to access audit logs of actions performed within their GitHub organization?"
+archetype: "questions"
+title: "Question 073"
+draft: false
+---
+
+> https://docs.github.com/en/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization
+1. [x] Select profile photo > Your organizations > Settings > Archives > Logs > Audit log. Then, use the Export dropdown to export as JSON or CSV.
+1. [ ] Directly email GitHub support to request an audit log be sent monthly to the organization's admin email.
+1. [ ] Navigate to the main GitHub page, use the search bar to type "Organization audit logs" and expect GitHub to automatically download the log.
+1. [ ] Check individual member profiles for a summary of their actions, compile these summaries manually, and format them for auditing.
diff --git a/content/questions/admin/question-074.md b/content/questions/admin/question-074.md
new file mode 100644
index 00000000..fe37db83
--- /dev/null
+++ b/content/questions/admin/question-074.md
@@ -0,0 +1,13 @@
+---
+question: "Which of the following are types of access tokens supported by GitHub? (Choose three.)"
+archetype: "questions"
+title: "Question 074"
+draft: false
+---
+
+> https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats
+- [x] Personal Access Token (PAT)
+- [x] Installation Access Token for a GitHub App
+- [x] User Access Token for a GitHub App
+- [ ] IoT Token for an IoT device
+- [ ] Ephemeral Access Token for temporary access
diff --git a/content/questions/admin/question-075.md b/content/questions/admin/question-075.md
new file mode 100644
index 00000000..b26326a1
--- /dev/null
+++ b/content/questions/admin/question-075.md
@@ -0,0 +1,12 @@
+---
+question: "What is the primary rate limit for authenticated personal users making REST API requests to GitHub API?"
+archetype: "questions"
+title: "Question 075"
+draft: false
+---
+
+> https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28#primary-rate-limit-for-authenticated-users
+1. [x] 5,000 requests per hour
+1. [ ] 60 requests per hour
+1. [ ] 15,000 requests per hour
+1. [ ] 1,000 requests per hour
diff --git a/content/questions/admin/question-076.md b/content/questions/admin/question-076.md
new file mode 100644
index 00000000..00e303cd
--- /dev/null
+++ b/content/questions/admin/question-076.md
@@ -0,0 +1,12 @@
+---
+question: "What's the difference between GitHub Apps and OAuth apps?"
+archetype: "questions"
+title: "Question 076"
+draft: false
+---
+
+> https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/differences-between-github-apps-and-oauth-apps
+1. [x] GitHub Apps offer granular permissions to specific repositories, while OAuth Apps request access to user data across all repositories.
+1. [ ] GitHub Apps and OAuth Apps do not differ; they provide the same level of permissions.
+1. [ ] OAuth Apps offer more granular permissions compared to GitHub Apps.
+1. [ ] GitHub Apps can only access public repositories, whereas OAuth Apps can access both public and private repositories.
diff --git a/content/questions/admin/question-077.md b/content/questions/admin/question-077.md
new file mode 100644
index 00000000..14d93c78
--- /dev/null
+++ b/content/questions/admin/question-077.md
@@ -0,0 +1,12 @@
+---
+question: "How can GitHub Apps react to specific events, and what are some examples of these events?"
+archetype: "questions"
+title: "Question 077"
+draft: false
+---
+
+> https://docs.github.com/en/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps#subscribing-to-webhook-events
+1. [x] GitHub Apps subscribe to events through webhooks, which notify the app of specific actions like pull request openings or issue creations.
+1. [ ] GitHub Apps can subscribe to events like push, pull request, and issue events through the app's configuration.
+1. [ ] 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
+1. [ ] GitHub Apps use a websocket connection that notifies the GitHub app of all  `push` and `pull_request` events
diff --git a/content/questions/admin/question-078.md b/content/questions/admin/question-078.md
new file mode 100644
index 00000000..a070876d
--- /dev/null
+++ b/content/questions/admin/question-078.md
@@ -0,0 +1,12 @@
+---
+question: "How can enterprises track their usage of GitHub Actions?"
+archetype: "questions"
+title: "Question 078"
+draft: false
+---
+
+> https://docs.github.com/en/enterprise-cloud@latest/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise#tracking-usage
+1. [x] By using webhooks to subscribe to information about workflow jobs and runs, and potentially using a data archiving system.
+1. [ ] By manually counting workflow runs and jobs in each repository at the end of each month.
+1. [ ] Through unlimited access to GitHub's internal analytics dashboard without any additional configuration.
+1. [ ] GitHub Actions usage cannot be tracked; enterprises must estimate usage based on developer feedback.
diff --git a/content/questions/admin/question-079.md b/content/questions/admin/question-079.md
new file mode 100644
index 00000000..90cb2d28
--- /dev/null
+++ b/content/questions/admin/question-079.md
@@ -0,0 +1,12 @@
+---
+question: "Who can configure IP allow lists for an enterprise on GitHub?"
+archetype: "questions"
+title: "Question 079"
+draft: false
+---
+
+> https://docs.github.com/en/enterprise-cloud@latest/admin/configuration/hardening-security-for-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list
+1. [x] Enterprise owners
+1. [ ] Organization owners
+1. [ ] Security Managers
+1. [ ] Organization moderators
diff --git a/content/questions/admin/question-080.md b/content/questions/admin/question-080.md
new file mode 100644
index 00000000..231a9d9b
--- /dev/null
+++ b/content/questions/admin/question-080.md
@@ -0,0 +1,12 @@
+---
+question: "Can organization owners manage IP allow list entries inherited from the enterprise account's allow list?"
+archetype: "questions"
+title: "Question 080"
+draft: false
+---
+
+> https://docs.github.com/en/enterprise-cloud@latest/admin/configuration/hardening-security-for-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list#about-githubs-ip-allow-list
+1. [x] No, they cannot manage entries inherited from the enterprise account's allow list
+1. [ ] Yes, they have full control over inherited entries
+1. [ ] Yes, but only with approval from enterprise owners
+1. [ ] No, only GitHub support can manage inherited entries
diff --git a/content/questions/admin/question-081.md b/content/questions/admin/question-081.md
new file mode 100644
index 00000000..e58f722a
--- /dev/null
+++ b/content/questions/admin/question-081.md
@@ -0,0 +1,12 @@
+---
+question: "Which runners must you use with GitHub Actions when an IP allow list is enabled on your enterprise?"
+archetype: "questions"
+title: "Question 081"
+draft: false
+---
+
+> https://docs.github.com/en/enterprise-cloud@latest/admin/configuration/hardening-security-for-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list#using-github-actions-with-an-ip-allow-list
+1. [x] Self-hosted runners or GitHub-hosted larger runners with static IP address ranges
+1. [ ] Only GitHub-hosted standard runners
+1. [ ] Any runner without considering the IP address
+1. [ ] Only runners within the organization's network without IP restrictions
diff --git a/content/questions/admin/question-082.md b/content/questions/admin/question-082.md
new file mode 100644
index 00000000..c69546c3
--- /dev/null
+++ b/content/questions/admin/question-082.md
@@ -0,0 +1,12 @@
+---
+question: "How can you ensure your self-hosted or larger hosted runners can communicate with GitHub when using an IP allow list?"
+archetype: "questions"
+title: "Question 082"
+draft: false
+---
+
+> https://docs.github.com/en/enterprise-cloud@latest/admin/configuration/hardening-security-for-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list#using-github-actions-with-an-ip-allow-list
+1. [x] Add the IP address or IP address range of your runners to the IP allow list configured for your enterprise
+1. [ ] Disable the IP allow list for GitHub Actions runners
+1. [ ] Register the runners in Enterprise > Network security > Actions settings
+1. [ ] Use a VPN for all runners to bypass the IP allow list
diff --git a/content/questions/admin/question-083.md b/content/questions/admin/question-083.md
new file mode 100644
index 00000000..e20d6a6e
--- /dev/null
+++ b/content/questions/admin/question-083.md
@@ -0,0 +1,12 @@
+---
+question: "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?"
+archetype: "questions"
+title: "Question 083"
+draft: false
+---
+
+> https://docs.github.com/en/enterprise-cloud@latest/admin/configuration/hardening-security-for-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list#using-github-pages-with-an-ip-allow-list
+1. [x] The build runner will have access to the repository for the GitHub Pages site by default
+1. [ ] The build runner will be blocked from accessing the repository until manually added to the allow list
+1. [ ] GitHub Pages cannot be built or updated until the IP allow list is disabled
+1. [ ] You must manually trigger builds for GitHub Pages sites
diff --git a/content/questions/admin/question-084.md b/content/questions/admin/question-084.md
new file mode 100644
index 00000000..4b74bdaa
--- /dev/null
+++ b/content/questions/admin/question-084.md
@@ -0,0 +1,15 @@
+---
+question: "What are some potential abuse vectors of enabling self-hosted runners on public repositories? (Choose four.)"
+archetype: "questions"
+title: "Question 084"
+draft: false
+---
+
+> https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#self-hosted-runner-security
+- [x] Malicious programs running on the machine
+- [x] Escaping the runner sandbox environment
+- [x] Exposing network environment
+- [x] Persisting dangerous data
+- [ ] Automatic environment cleanup after job execution can cause data loss
+- [ ] Lower computational efficiency due to security measures
+- [ ] Limited integration with GitHub-hosted services
diff --git a/content/questions/admin/question-085.md b/content/questions/admin/question-085.md
new file mode 100644
index 00000000..b16b2aaf
--- /dev/null
+++ b/content/questions/admin/question-085.md
@@ -0,0 +1,12 @@
+---
+question: "How should you select appropriate runners to support your workflow's specific workloads?"
+archetype: "questions"
+title: "Question 085"
+draft: false
+---
+
+> https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#differences-between-github-hosted-and-self-hosted-runners
+1. [x] Choose self-hosted runners for customized environments or GitHub-hosted for automatic updates and clean instances.
+1. [ ] Always prefer GitHub-hosted runners for all workloads to ensure maximum security.
+1. [ ] Use only self-hosted runners, regardless of workload complexity, to minimize costs.
+1. [ ] Restrict to using GitHub-hosted runners with custom hardware configurations for better performance.
diff --git a/content/questions/admin/question-086.md b/content/questions/admin/question-086.md
new file mode 100644
index 00000000..748ec35e
--- /dev/null
+++ b/content/questions/admin/question-086.md
@@ -0,0 +1,12 @@
+---
+question: "How do you add a self-hosted runner to a GitHub repository?"
+archetype: "questions"
+title: "Question 086"
+draft: false
+---
+
+> https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners
+1. [x] Navigate to the repository settings, select Actions, then Runners, and follow the instructions to download, configure, and run the self-hosted runner application.
+1. [ ] Directly clone the repository to your local machine and run a specific script to automatically add it as a self-hosted runner.
+1. [ ] Email GitHub support to request the addition of a self-hosted runner to your repository.
+1. [ ] Use the GitHub API to send a request for adding a self-hosted runner without any manual configuration.
diff --git a/content/questions/admin/question-087.md b/content/questions/admin/question-087.md
new file mode 100644
index 00000000..d6e3fe8c
--- /dev/null
+++ b/content/questions/admin/question-087.md
@@ -0,0 +1,12 @@
+---
+question: "What is required to add a self-hosted runner to an organization on GitHub?"
+archetype: "questions"
+title: "Question 087"
+draft: false
+---
+
+> https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners
+1. [x] Organization owner access, navigate to organization settings, select Actions, then Runners, and follow the setup instructions for the self-hosted runner.
+1. [ ] General member access with no special permissions, and utilize a GitHub Action to automatically register a self-hosted runner.
+1. [ ] Public repository access within the organization and manual script execution on the server intended as a runner.
+1. [ ] Submit a form on GitHub's website to request the GitHub team to add a self-hosted runner to your organization manually.
diff --git a/content/questions/admin/question-088.md b/content/questions/admin/question-088.md
new file mode 100644
index 00000000..0f4ae445
--- /dev/null
+++ b/content/questions/admin/question-088.md
@@ -0,0 +1,12 @@
+---
+question: "How can you manage access to self-hosted runners in an organization using runner groups?"
+archetype: "questions"
+title: "Question 088"
+draft: false
+---
+
+> https://docs.github.com/en/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups
+1. [x] Create runner groups to collect sets of runners, then configure access policies for repositories within the organization.
+1. [ ] Manually assign each self-hosted runner to individual repositories without using runner groups.
+1. [ ] Use a single default runner group for all runners and repositories
+1. [ ] 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
diff --git a/content/questions/admin/question-089.md b/content/questions/admin/question-089.md
new file mode 100644
index 00000000..ac324e79
--- /dev/null
+++ b/content/questions/admin/question-089.md
@@ -0,0 +1,12 @@
+---
+question: "What steps are involved in creating a self-hosted runner group for an organization on GitHub?"
+archetype: "questions"
+title: "Question 089"
+draft: false
+---
+
+> https://docs.github.com/en/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups
+1. [x] Navigate to organization settings, select Actions, click Runner groups, create a new group, and assign a repository access policy.
+1. [ ] In the `.github` repository modify the `.gitconfig` file to specify runner groups and associated access policies.
+1. [ ] Contact GitHub support to request the creation of a runner group and provide a list of repositories for access configuration.
+1. [ ] Use a GitHub Actions workflow to automatically generate runner groups based on repository activity and usage patterns.
diff --git a/content/questions/admin/question-090.md b/content/questions/admin/question-090.md
new file mode 100644
index 00000000..00ff2fab
--- /dev/null
+++ b/content/questions/admin/question-090.md
@@ -0,0 +1,12 @@
+---
+question: "How do you change which repositories can access a specific runner group in an organization?"
+archetype: "questions"
+title: "Question 090"
+draft: false
+---
+
+> https://docs.github.com/en/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups
+1. [x] In organization settings, navigate to Actions, select Runner groups, choose a group, and modify the repository access settings.
+1. [ ] Use the GitHub CLI to execute a command that reassigns repository access to different runner groups within the organization.
+1. [ ] Edit the runner group's configuration file located on the server hosting the self-hosted runners to update repository access.
+1. [ ] Repositories automatically gain access to all runner groups without the need for manual configuration changes.
diff --git a/content/questions/admin/question-091.md b/content/questions/admin/question-091.md
new file mode 100644
index 00000000..783b90fa
--- /dev/null
+++ b/content/questions/admin/question-091.md
@@ -0,0 +1,12 @@
+---
+question: "How can you use 3rd party vaults to manage secrets for GitHub Actions?"
+archetype: "questions"
+title: "Question 091"
+draft: false
+---
+
+> https://docs.github.com/en/actions/security-guides/encrypted-secrets#storing-large-secrets
+1. [x] 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.
+1. [ ] Direct integration with 3rd party vaults is supported natively within GitHub Actions without needing any additional configuration.
+1. [ ] Third party vaults should be accessed by embedding their API keys within the workflow files and using the API or CLI of that vendor
+1. [ ] GitHub Actions does not support the use of 3rd party vaults for secret management; all secrets must be stored within GitHub.
diff --git a/content/questions/admin/question-092.md b/content/questions/admin/question-092.md
new file mode 100644
index 00000000..8b820d28
--- /dev/null
+++ b/content/questions/admin/question-092.md
@@ -0,0 +1,15 @@
+---
+question: "Which package managers and formats are supported by GitHub Packages? (Choose five.)"
+archetype: "questions"
+title: "Question 092"
+draft: false
+---
+
+> https://docs.github.com/en/packages/learn-github-packages/introduction-to-github-packages#about-github-packages
+- [x] npm for JavaScript
+- [x] RubyGems for Ruby
+- [x] Maven and Gradle for Java
+- [x] Nuget for .NET
+- [x] Docker and OCI images
+- [ ] Poetry for Python
+- [ ] Cargo for Rust
diff --git a/content/questions/admin/question-093.md b/content/questions/admin/question-093.md
new file mode 100644
index 00000000..13adea1c
--- /dev/null
+++ b/content/questions/admin/question-093.md
@@ -0,0 +1,12 @@
+---
+question: "How can one authenticate to GitHub Packages?"
+archetype: "questions"
+title: "Question 093"
+draft: false
+---
+
+> https://docs.github.com/en/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages
+1. [x] By authenticating using a PAT with appropriate scope
+1. [ ] GitHub Packages can be accessed and shared publicly without any authentication.
+1. [ ] Access to GitHub Packages is restricted to GitHub Enterprise accounts only.
+1. [ ] By using the default GitHub login without needing any special authentication tokens.
diff --git a/content/questions/admin/question-094.md b/content/questions/admin/question-094.md
new file mode 100644
index 00000000..bdc80387
--- /dev/null
+++ b/content/questions/admin/question-094.md
@@ -0,0 +1,12 @@
+---
+question: "What is required to download or publish a GitHub Package within workflows, such as with GitHub Actions or other CI/CD tools?"
+archetype: "questions"
+title: "Question 094"
+draft: false
+---
+
+> https://docs.github.com/en/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages
+1. [x] Use `GITHUB_TOKEN` for publishing packages associated with the workflow repository, and a PAT for installing packages from private repositories.
+1. [ ] GitHub Packages cannot be used in GitHub Actions workflows or any CI/CD tools.
+1. [ ] Only SSH keys are required for using GitHub Packages in workflows.
+1. [ ] Manual download and upload of packages is required for each workflow run.
diff --git a/content/questions/admin/question-095.md b/content/questions/admin/question-095.md
new file mode 100644
index 00000000..7414e0ee
--- /dev/null
+++ b/content/questions/admin/question-095.md
@@ -0,0 +1,12 @@
+---
+question: "What are the differences and use cases between GitHub Packages and releases?"
+archetype: "questions"
+title: "Question 095"
+draft: false
+---
+
+> https://docs.github.com/en/packages/learn-github-packages/introduction-to-github-packages#about-github-packages
+1. [x] 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.
+1. [ ] GitHub Packages and releases are functionally identical, with no differences in use cases.
+1. [ ] Releases are used for private software distribution, whereas GitHub Packages is exclusively for public package hosting.
+1. [ ] GitHub Packages requires external CI/CD integration for distribution, unlike releases which are fully managed within GitHub.