Balance answer lengths to prevent longest-answer-is-correct pattern

questions/en/actions/question-077.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/actions/hosting-your-own-runners/mana
 ---
 
 - [x] A self-hosted runner is a system that you deploy and manage to execute jobs from GitHub Actions on GitHub.com
-- [ ] A self-hosted runner is a system to upload code to a private server
-- [ ] A self-hosted runner is a system to be able to create workloads automatically
-- [ ] A self-hosted runner is a system to manage pull requests from users of the organization
+- [ ] A self-hosted runner is a system to upload code to a private server outside of GitHub's infrastructure
+- [ ] A self-hosted runner is a system to be able to create workloads automatically for your organization
+- [ ] A self-hosted runner is a system to manage pull requests from users of the organization on GitHub

questions/en/actions/question-085.md

@@ -3,7 +3,7 @@ question: "What is the purpose of the `with` keyword in a GitHub Actions workflo
 documentation: "https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepswith"
 ---
 
-- [ ] To define environment variables
+- [ ] To define environment variables for steps
 - [x] To specify input parameters for an action
-- [ ] To set up dependencies
-- [ ] To trigger another workflow
+- [ ] To set up dependencies between jobs
+- [ ] To trigger another workflow in the repo

questions/en/actions/question-088.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/enterprise-cloud@latest/actions/using
 ---
 
 - [x] Allows defining multiple job configurations to run in parallel
-- [ ] Sets environment variables for the job
-- [ ] Triggers workflows based on a schedule
-- [ ] Defines secrets for the workflow
+- [ ] Sets environment variables for the job across all steps
+- [ ] Triggers workflows based on a cron schedule expression
+- [ ] Defines secrets for the workflow at the job level

questions/en/actions/question-097.md

@@ -3,7 +3,7 @@ question: "How does the `actions/cache` action in GitHub Actions handle a cache
 documentation: "https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#managing-caches"
 ---
 
-- [ ] by requiring manual intervention to create a new cache
-- [ ] by searching for a cache in other repositories
+- [ ] by requiring manual intervention to create a new cache entry
+- [ ] by searching for a cache in other repositories in the org
 - [x] by automatically creating a new cache if the job is completed successfully
-- [ ] by terminating the workflow if a cache miss occurs
+- [ ] by terminating the workflow if a cache miss occurs on the key

questions/en/actions/question-099.md

@@ -3,7 +3,7 @@ question: "What is the recommended approach for storing secrets larger than 48 K
 documentation: "https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#limits-for-secrets"
 ---
 
-- [ ] avoid storing large secrets entirely to ensure security
-- [ ] secrets larger than 48 KB cannot be stored
+- [ ] avoid storing large secrets entirely to ensure security of the workflow
+- [ ] secrets larger than 48 KB cannot be stored in GitHub Actions at all
 - [x] encrypt and store secrets in the repository but keep the decryption passphrase as a secret
-- [ ] store large secrets directly as repository secrets to avoid limitations
+- [ ] store large secrets directly as repository secrets to avoid any limitations

questions/en/actions/question-106.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/actions/using-workflows/caching-depen
 ---
 
 - [x] provide alternative keys to use in case of a cache miss
-- [ ] indicate whether a cache hit occurred
-- [ ] specify the location of the cached files
-- [ ] enable cross-OS cache functionality
+- [ ] indicate whether a cache hit occurred on the primary key
+- [ ] specify the location of the cached files on the runner
+- [ ] enable cross-OS cache functionality between runners

questions/en/actions/question-114.md

@@ -12,6 +12,6 @@ jobs:
                 os: [ubuntu-latest, windows-latest]
 ```
 - [x] reference variables through the `matrix` context with syntax like`matrix.version` and `matrix.os`
-- [ ] by using the `matrix.property` syntax
-- [ ] by using the `context` keyword within the job configuration
-- [ ] by accessing the variables directly with the syntax `version` and `os`
+- [ ] by using the `matrix.property` syntax to access all values as a single object
+- [ ] by using the `context` keyword within the job configuration to look up values
+- [ ] by accessing the variables directly with the syntax `version` and `os` in expressions

questions/en/admin/question-009.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/actions/security-guides/security-hard
 ---
 
 - [x] Benefits include automation of workflows and enhanced functionality; risks include potential security vulnerabilities and dependency on third-party services.
-- [ ] Benefits are limited to user interface improvements; risks include high costs and increased system complexity.
-- [ ] The only benefit is the ease of installation; risks involve complete access to codebase and data.
-- [ ] 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 without meaningful gains.
+- [ ] The only benefit is the ease of installation; risks involve complete access to your entire codebase and all organization data.
+- [ ] Benefits include official support from GitHub for all apps; risks include limited functionality and lack of customization options.

questions/en/admin/question-011.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/enterprise-cloud@latest/authenticatio
 ---
 
 - [x] 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.
-- [ ] 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.
-- [ ] 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 credentials for each individual organization within the enterprise, managed independently by each org admin.
+- [ ] Enabling SAML SSO for all organizations limits repository access to internal collaborators only, preventing any external contributions from outside collaborators or guests.
+- [ ] There is no difference in the implementation of SAML SSO between a single organization and all organizations in an enterprise account; both use the same configuration.

questions/en/admin/question-015.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/organizations/keeping-your-organizati
 ---
 
 - [x] In the organization's settings, under `Security`, select `Authentication security`, and then choose `Require two-factor authentication for everyone in your organization`.
-- [ ] Go to the organization's page, click on `Members`, and individually set up 2FA for each member.
-- [ ] In your organization's settings, under `Billing`, select `Require two-factor authentication for billing managers only`.
-- [ ] 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 through their profile settings.
+- [ ] In your organization's settings, under `Billing`, select `Require two-factor authentication for billing managers only` to secure finances.
+- [ ] Send an email to all organization members asking them to manually enable 2FA on their accounts through their own settings.

questions/en/admin/question-018.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/enterprise-cloud@latest/admin/identit
 ---
 
 - [x] User accounts are provisioned by the enterprise's IdP, with access provided to GitHub Enterprise Cloud.
-- [ ] User accounts are created manually by each user on GitHub.com.
-- [ ] User accounts are provisioned by GitHub without any input from the enterprise's IdP.
-- [ ] User accounts are automatically generated based on public email addresses.
+- [ ] User accounts are created manually by each user on GitHub.com through the standard signup flow.
+- [ ] User accounts are provisioned by GitHub without any input from the enterprise's IdP or admins.
+- [ ] User accounts are automatically generated based on public email addresses found in commits.

questions/en/admin/question-021.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/enterprise-cloud@latest/admin/identit
 ---
 
 - [x] Managed users are not allowed to contribute to public resources, and they need a separate personal account for this purpose.
-- [ ] Managed users can freely contribute to public resources and external enterprises without restrictions.
-- [ ] Managed users must request special permission from GitHub to contribute to external resources.
-- [ ] Contributions to external resources are automatically managed by the enterprise's IdP.
+- [ ] Managed users can freely contribute to public resources and external enterprises without any restrictions.
+- [ ] Managed users must request special permission from GitHub support to contribute to external resources.
+- [ ] Contributions to external resources are automatically managed by the enterprise's IdP without user action.

questions/en/admin/question-022.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/enterprise-cloud@latest/organizations
 ---
 
 - [x] 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 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 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.
-- [ ] 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 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, including theming, notification preferences, and personal dashboard configuration for each individual user account within the platform.
+- [ ] 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 stored data and user information within GitHub's infrastructure without integrating with any external systems or third-party identity providers for authentication.
+- [ ] SCIM is a GitHub-specific tool used for enhancing the network performance of GitHub servers. It works by managing internet bandwidth and traffic routing within the GitHub ecosystem, ensuring optimal performance and low latency for all users accessing repositories, actions, and packages across different geographic regions.

questions/en/admin/question-023.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/enterprise-cloud@latest/organizations
 ---
 
 - [x] 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.
-- [ ] 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 is an automated process that allows users to manage their public profiles and repositories through a GitHub-specific interface, without any dependency on external identity providers or SSO.
+- [ ] Team synchronization is used for internal data security and user information management within GitHub, while SCIM is an interface for user profile and repository customization that operates independently of team membership.
+- [ ] Both team synchronization and SCIM in GitHub are used for the same user provisioning services, inviting non-members to join organizations, managing public profiles, and customizing repository access based on contribution history.

questions/en/admin/question-027.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/enterprise-cloud@latest/admin/overvie
 ---
 
 - [x] To provide administrators with a single point of visibility and management across multiple organizations
-- [ ] To provide individual users with unlimited private repositories
-- [ ] To offer free access to GitHub Enterprise Server
-- [ ] To allow users to manage their public and private contributions separately
+- [ ] To provide individual users with unlimited private repositories regardless of their plan
+- [ ] To offer free access to GitHub Enterprise Server for all organization members
+- [ ] To allow users to manage their public and private contributions separately from teams

questions/en/admin/question-031.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/enterprise-server@latest/admin/overvi
 ---
 
 - [x] On-premises data center or to a public cloud service (e.g., AWS, GCP, Azure)
-- [ ] Exclusively to private cloud environments
-- [ ] Only on GitHub-managed servers
-- [ ] Directly onto personal computing devices
+- [ ] Exclusively to private cloud environments managed by GitHub's team
+- [ ] Only on GitHub-managed servers in their proprietary data centers
+- [ ] Directly onto personal computing devices such as laptops or desktops

questions/en/admin/question-032.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/enterprise-server@latest/admin/overvi
 ---
 
 - [x] Runs on your infrastructure and governed by access and security controls you define
-- [ ] Unlimited public and private repositories on GitHub.com
-- [ ] Free access to GitHub Actions and GitHub Packages
-- [ ] Automatic deployment to any cloud service provider
+- [ ] Unlimited public and private repositories on GitHub.com without storage limits
+- [ ] Free access to GitHub Actions and GitHub Packages with unlimited minutes
+- [ ] Automatic deployment to any cloud service provider with zero configuration

questions/en/admin/question-033.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/enterprise-server@latest/admin/overvi
 ---
 
 - [x] Via browser, administrative SSH access, and REST or GraphQL APIs
-- [ ] Only through direct access to the server's console
-- [ ] Via GitHub.com's web interface exclusively
-- [ ] Through third-party management tools only
+- [ ] Only through direct access to the server's physical console
+- [ ] Via GitHub.com's web interface exclusively without local access
+- [ ] Through third-party management tools only with special plugins

questions/en/admin/question-039.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/organizations/managing-user-access-to
 ---
 
 - [x] In the `Access` section of the organization's settings, select `Member privileges`, then under `Base permissions`, choose a permissions level and confirm the change.
-- [ ] Default permissions are automatically determined by GitHub based on the organization's activity and cannot be manually set.
-- [ ] By individually setting permissions for each new member as they are added to the organization, with no default level available.
-- [ ] Default permissions for new members are set through a GitHub API call specifying the desired base permission level for the organization.
+- [ ] Default permissions are automatically determined by GitHub based on the organization's activity and cannot be manually set or overridden by admins.
+- [ ] By individually setting permissions for each new member as they are added to the organization, with no default level available for configuration.
+- [ ] Default permissions for new members are set through a GitHub API call specifying the desired base permission level for the organization's repositories.

questions/en/admin/question-040.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/enterprise-cloud@latest/admin/identit
 ---
 
 - [x] 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 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 backs up GitHub organization data to Microsoft Entra ID servers, providing an additional layer of data redundancy.
+- [ ] It enables GitHub to serve as an identity provider for Microsoft Entra ID, streamlining user authentication processes and managing login flows across enterprise applications.
+- [ ] It automatically converts Microsoft Entra ID group memberships into corresponding GitHub repositories, facilitating resource allocation and project organization.
+- [ ] It backs up GitHub organization data to Microsoft Entra ID servers, providing an additional layer of data redundancy and disaster recovery capabilities.

questions/en/admin/question-041.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/organizations/collaborating-with-grou
 ---
 
 - [x] To allow businesses and open-source projects to collaborate across many projects at once with advanced security and administrative features.
-- [ ] To provide individual users with personal space to host their private projects.
-- [ ] To serve as a backup service for code repositories.
-- [ ] To offer a platform for personal blogging and website hosting.
+- [ ] To provide individual users with personal space to host their private projects, separate from any team or collaborative work.
+- [ ] To serve as a backup service for code repositories, ensuring data redundancy and disaster recovery across multiple regions.
+- [ ] To offer a platform for personal blogging and website hosting, allowing members to publish content under the organization's domain.

questions/en/admin/question-043.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/organizations/collaborating-with-grou
 ---
 
 - [x] By creating nested teams that reflect the group's structure, with cascading access permissions.
-- [ ] Through the use of single sign-on (SSO) for all members exclusively.
-- [ ] By granting all members owner-level permissions.
-- [ ] Limiting repository creation to organization owners only.
+- [ ] Through the use of single sign-on (SSO) for all members exclusively without teams.
+- [ ] By granting all members owner-level permissions across the entire organization.
+- [ ] Limiting repository creation to organization owners only without delegating access.

questions/en/admin/question-044.md

@@ -4,7 +4,7 @@ documentation: "https://docs.github.com/en/get-started/learning-about-github/abo
 ---
 
 - [x] Any GitHub Enterprise plan with a GHAS license
-- [ ] GitHub Enterprise Cloud
-- [ ] GitHub Enterprise Server
-- [ ] GitHub Pro
-- [ ] GitHub Team
+- [ ] GitHub Enterprise Cloud without additional licenses
+- [ ] GitHub Enterprise Server without additional licenses
+- [ ] GitHub Pro for individual developers
+- [ ] GitHub Team for small organizations

questions/en/admin/question-045.md

@@ -4,6 +4,6 @@ documentation: "https://docs.github.com/en/enterprise-cloud@latest/admin/overvie
 ---
 
 - [x] It allows owners to centrally manage policy and billing for multiple organizations.
-- [ ] It provides unlimited private repositories for individual users.
-- [ ] It offers a free domain for hosting the organization's website.
-- [ ] It automatically enrolls the organization in a premium support plan.
+- [ ] It provides unlimited private repositories for individual users in the enterprise.
+- [ ] It offers a free custom domain for hosting the organization's website pages.
+- [ ] It automatically enrolls the organization in a premium support plan for free.