GitHub Admin updates after taking the full practice test (#443)

FidelusAleksander · web-flow · commit 5cc649c18c71 · 2025-12-05T20:04:42.000+01:00
diff --git a/content/en/questions/admin/question-002.md b/content/en/questions/admin/question-002.md
@@ -1,11 +1,11 @@
 ---
 title: "Question 002"
-question: "What is the GitHub dependency graph?"
+question: "What is the GitHub Dependabot dependency graph?"
 ---
 
 
 > https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph
 1. [x] It is a representation of a repository's dependencies and dependents.
-1. [ ] There is no such thing as the GitHub dependency graph.
+1. [ ] There is no such thing as the dependency graph.
 1. [ ] It is a tool that automatically proposes version updates to dependencies in a repository.
 1. [ ] It is a GitHub maintained list of known vulnerabilities in open source software packages.
diff --git a/content/en/questions/admin/question-006.md b/content/en/questions/admin/question-006.md
@@ -7,4 +7,4 @@ title: "Question 006"
 - [x] 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`.
 - [x] Generate and download a support bundle directly to your local machine via SSH using the `ghe-support-bundle -o > support-bundle.tgz` CLI command.
 - [ ] 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.
-- [ ] 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.
+- [ ] Click your profile, then `Enterprises`. In the enterprise account sidebar, select `Settings` and under `License`, click `Generate a support bundle`. This will create and download the bundle.
diff --git a/content/en/questions/admin/question-008.md b/content/en/questions/admin/question-008.md
@@ -5,6 +5,6 @@ title: "Question 008"
 
 > https://docs.github.com/en/apps/using-github-apps/installing-a-github-app-from-github-marketplace-for-your-organizations
 1. [x] Browse GitHub Marketplace, select the app, choose a plan, select the organization, and then review and install the app.
-1. [ ] Contact GitHub support to manually install the app, then configure it via email instructions.
-1. [ ] Download the app from an external site and manually upload it to your GitHub organization's repositories.
-1. [ ] Install the app directly from the organization's dashboard without selecting any specific plan.
+1. [ ] Navigate to organization settings, select "Installed apps", then manually add the app's client ID to install it.
+1. [ ] Install the app using the GitHub CLI with the `gh app install` command, specifying the organization name.
+1. [ ] Clone the app's repository and run the installation script locally to register it with your organization.
diff --git a/content/en/questions/admin/question-009.md b/content/en/questions/admin/question-009.md
@@ -3,6 +3,8 @@ question: "What are the benefits and risks of using apps and actions from the Gi
 title: "Question 009"
 ---
 
+> https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions
+
 1. [x] Benefits include automation of workflows and enhanced functionality; risks include potential security vulnerabilities and dependency on third-party services.
 1. [ ] Benefits are limited to user interface improvements; risks include high costs and increased system complexity.
 1. [ ] The only benefit is the ease of installation; risks involve complete access to codebase and data.
diff --git a/content/en/questions/admin/question-013.md b/content/en/questions/admin/question-013.md
@@ -4,7 +4,7 @@ title: "Question 013"
 ---
 
 > https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization#enabling-and-testing-saml-single-sign-on-for-your-organization
-1. [x] Navigate to `Your organizations`, choose `Settings`, click on `Authentication security`, select `Enable SAML authentication`, configure IdP settings, test SAML configuration, and enforce SAML SSO.
-1. [ ] Go to `Organization Settings`, select `Security`, choose `SAML Authentication`, enter IdP information, perform a test of the SAML configuration, and enforce SAML SSO.
-1. [ ] 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.
-1. [ ] Access `Organization Settings`, click `Security`, enable `SAML SSO`, add IdP URL, test the configuration, and opt to enforce SAML SSO upon successful testing.
+1. [x] Navigate to your organization `Settings`, click on `Authentication security`, select `Enable SAML authentication`, configure IdP settings, test SAML configuration, and enforce SAML SSO.
+1. [ ] From `Enterprise account settings`, open `Security`, enable SAML SSO and enforce for all organizations; then configure the IdP. (This manages enterprise-wide SSO, not a single org.)
+1. [ ] In the organization, go to `Settings` → `Member privileges`, enable `SAML SSO`, add IdP metadata, and enforce without testing. (SAML is configured under `Authentication security`, and testing is required.)
+1. [ ] Open the repository’s `Settings`, choose `Security`, enable `SAML SSO`, configure the IdP, and enforce. (SAML SSO is set at the organization level, not per repository.)
diff --git a/content/en/questions/admin/question-014.md b/content/en/questions/admin/question-014.md
@@ -8,3 +8,4 @@ title: "Question 014"
 1. [ ] Active Directory Federation Services (AD FS)
 1. [ ] Microsoft Entra ID
 1. [ ] Shibboleth
+1. [ ] Okta
diff --git a/content/en/questions/admin/question-019.md b/content/en/questions/admin/question-019.md
@@ -1,10 +1,10 @@
 ---
-question: "What is required for a user to authenticate with an Enterprise Managed Users account?"
+question: "What is required for a user to authenticate with an Enterprise Managed User account?"
 title: "Question 019"
 ---
 
 > https://docs.github.com/en/enterprise-cloud@latest/admin/identity-and-access-management/understanding-iam-for-enterprises/about-enterprise-managed-users#authenticating-with-a-managed-user-account
-1. [x] Users must authenticate on the enterprise's IdP to access resources on GitHub.com.
+1. [x] Users must authenticate on the company's IdP to access resources on GitHub.com.
 1. [ ] Users authenticate through a public GitHub login page without any enterprise interference.
 1. [ ] Authentication is bypassed for enterprise managed users for ease of access.
 1. [ ] Users provide a special GitHub-managed authentication token.
diff --git a/content/en/questions/admin/question-024.md b/content/en/questions/admin/question-024.md
@@ -1,5 +1,5 @@
 ---
-question: "What are valid authentication methods available in GitHub? (choose six.)"
+question: "What are valid authentication methods available in GitHub? (Choose six.)"
 title: "Question 024"
 ---
 
@@ -8,7 +8,7 @@ title: "Question 024"
 - [x] Personal access token (PAT)
 - [x] SSH KEY
 - [x] SAML SSO for enterprise accounts
-- [x] Passkey authentication (opt-in beta for passwordless login)
+- [x] Passkey authentication
 - [x] OAuth tokens for third-party app integrations
 - [ ] QR code system linked to a mobile device
 - [ ] Authentication via social media accounts like Facebook or Google
diff --git a/content/en/questions/admin/question-025.md b/content/en/questions/admin/question-025.md
@@ -4,7 +4,7 @@ title: "Question 025"
 ---
 
 > https://docs.github.com/en/enterprise-cloud@latest/admin/overview/about-github-for-enterprises#about-deployment-options
-1. [x] GitHub Enterprise Cloud is hosted by GitHub, while GitHub Enterprise Server is hosted on your own servers
+1. [x] GitHub Enterprise Cloud is hosted by GitHub, while GitHub Enterprise Server is hosted on your own servers or a cloud provider.
 1. [ ] GitHub Enterprise Cloud is hosted on your servers, while GitHub Enterprise Server is hosted by GitHub
 1. [ ] GitHub Enterprise Cloud offers only public repositories, while GitHub Enterprise Server offers private repositories
 1. [ ] GitHub Enterprise Cloud is designed for individual use, while GitHub Enterprise Server is for organizations
diff --git a/content/en/questions/admin/question-026.md b/content/en/questions/admin/question-026.md
@@ -10,4 +10,3 @@ title: "Question 026"
 - [x] Ability to restrict email notifications to verified domains
 - [ ] Free public repositories for all users
 - [ ] Unlimited private repositories for individual users
-- [ ] Automatic code review for every push
diff --git a/content/en/questions/admin/question-043.md b/content/en/questions/admin/question-043.md
@@ -4,7 +4,7 @@ title: "Question 043"
 ---
 
 > https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/about-organizations#about-organizations
-1. [x] By creating nested teams that reflect the group's structure, with cascading access permissions and mentions.
+1. [x] By creating nested teams that reflect the group's structure, with cascading access permissions.
 1. [ ] Through the use of single sign-on (SSO) for all members exclusively.
 1. [ ] By granting all members owner-level permissions.
 1. [ ] Limiting repository creation to organization owners only.
diff --git a/content/en/questions/admin/question-044.md b/content/en/questions/admin/question-044.md
@@ -3,6 +3,7 @@ question: "Which GitHub plan allows to use secret scanning in private repositori
 title: "Question 044"
 ---
 
+> https://docs.github.com/en/get-started/learning-about-github/about-github-advanced-security
 1. [x] Any GitHub Enterprise plan with a GHAS license
 1. [ ] GitHub Enterprise Cloud
 1. [ ] GitHub Enterprise Server
diff --git a/content/en/questions/admin/question-047.md b/content/en/questions/admin/question-047.md
@@ -1,10 +1,17 @@
 ---
-question: "Which of the following are recognized roles within a GitHub organization?"
+question: "Which of the following are NOT recognized roles within a GitHub organization? (Choose three.)"
 title: "Question 047"
 ---
 
 > https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#about-organization-roles
-1. [x] Organization owners, Organization members, Organization moderators, Billing managers, Security managers, GitHub App managers, Outside collaborators
-1. [ ] Project managers, Contributors, Observers, External consultants
-1. [ ] System administrators, Database managers, IT support, External auditors
-1. [ ] Lead developers, Junior developers, Senior developers, Project owners
+
+- [ ] Organization owners
+- [ ] Organization members
+- [ ] Organization moderators
+- [ ] Billing managers
+- [ ] Security Managers
+- [ ] Outside Collaborators
+- [ ] GitHub App managers
+- [x] Project managers
+- [x] External Contributors
+- [x] Project Codeowners
diff --git a/content/en/questions/admin/question-048.md b/content/en/questions/admin/question-048.md
@@ -6,5 +6,6 @@ title: "Question 048"
 > https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization
 1. [x] Owner
 1. [ ] Member
+1. [ ] Admin
 1. [ ] Billing manager
 1. [ ] Outside collaborator
diff --git a/content/en/questions/admin/question-052.md b/content/en/questions/admin/question-052.md
@@ -4,7 +4,7 @@ title: "Question 052"
 ---
 
 > https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization
-1. [x] By navigating to the organization's settings, selecting `Members`,and then adjusting the member's role from the list.
+1. [x] By navigating to the `People` tab in the Organization and adjusting the member's role from the list.
 1. [ ] Members can change their own roles within the organization settings.
 1. [ ] By deleting and re-inviting the member with the desired role.
 1. [ ] Role changes within an organization are not possible; a new organization must be created.
diff --git a/content/en/questions/admin/question-067.md b/content/en/questions/admin/question-067.md
@@ -5,6 +5,6 @@ title: "Question 067"
 
 > 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
+1. [ ] git revert & git reset --hard
+1. [ ] git clean & git prune
+1. [ ] git gc & git reflog expire
diff --git a/content/en/questions/admin/question-069.md b/content/en/questions/admin/question-069.md
@@ -1,5 +1,5 @@
 ---
-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?"
+question: "After sensitive data is removed from a repository's history using `git-filter-repo` and pushed to GitHub, what is a necessary step to fully remove the data from GitHub?"
 title: "Question 069"
 ---
 
diff --git a/content/en/questions/admin/question-070.md b/content/en/questions/admin/question-070.md
@@ -4,7 +4,8 @@ title: "Question 070"
 ---
 
 > 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. [x] Adding sensitive files or patterns to a `.gitignore` file
 1. [ ] Regularly changing your passwords
 1. [ ] Disabling push access to the repository
 1. [ ] Using `git add .` before all commits
+1. [ ] Disabling all `.gitignore` rules to ensure every file is tracked
diff --git a/content/en/questions/admin/question-071.md b/content/en/questions/admin/question-071.md
@@ -4,7 +4,7 @@ title: "Question 071"
 ---
 
 > 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. [x] Settings managed by enterprise owners to control aspects like repository management, team access, and security features within their GitHub organizations.
 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 can be overridden by the organization owners.
diff --git a/content/en/questions/admin/question-072.md b/content/en/questions/admin/question-072.md
@@ -4,7 +4,7 @@ title: "Question 072"
 ---
 
 > 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. [x] Enterprise policies mandate a uniform policy across all organizations within an enterprise.
 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/en/questions/admin/question-073.md b/content/en/questions/admin/question-073.md
@@ -4,7 +4,7 @@ title: "Question 073"
 ---
 
 > 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. [x] Go to the Organization settings > Archive > 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/en/questions/admin/question-077.md b/content/en/questions/admin/question-077.md
@@ -5,6 +5,6 @@ title: "Question 077"
 
 > 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
+1. [ ] GitHub Apps use polling to periodically check for new events on GitHub.
+1. [ ] GitHub Apps receive all events by default and must filter them in the app's code.
+1. [ ] GitHub Apps use a WebSocket connection to receive real-time notifications of all repository events.
diff --git a/content/en/questions/admin/question-082.md b/content/en/questions/admin/question-082.md
@@ -1,5 +1,5 @@
 ---
-question: "How can you ensure your self-hosted or larger hosted runners can communicate with GitHub when using an IP allow list?"
+question: "How can you ensure your self-hosted or larger GitHub hosted runners can communicate with GitHub when using an IP allow list?"
 title: "Question 082"
 ---
 
diff --git a/content/en/questions/admin/question-091.md b/content/en/questions/admin/question-091.md
@@ -6,7 +6,7 @@ title: "Question 091"
 > https://developer.hashicorp.com/vault/docs/platform/github-actions
 > https://bitwarden.com/help/github-actions-integration/
 > https://docs.keeper.io/en/keeperpam/secrets-manager/integrations/github-actions
-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. [x] Store secrets in the 3rd party vault and authenticate from your workflow (via the vendor action/CLI) using access credentials stored as GitHub Actions secrets to retrieve them at runtime.
 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/cspell.json b/cspell.json
@@ -23,6 +23,7 @@
     "sarifs",
     "GHAS",
     "SCIM",
+    "reflog",
     "Keycloak",
     "Entra",
     "passwordless",
