Merge pull request #50646 from camihmerhar/Infomagnus-Actions-Update-Manage-GitHub-Actions-in-Enterprise

Infomagnus actions update manage GitHub actions in enterprise

Author: v-ccolin

learn-pr/github/create-custom-github-actions/knowledge-check.yml

@@ -3,7 +3,7 @@ uid: learn.github.create-custom-github-actions.knowledge-check
 title: Module assessment
 metadata:
   title: Module assessment
-  description: Check what you've learned.
+  description: Check what you learned.
   ms.date: 01/30/2025
   author: a-a-ron
   ms.author: aastewar
@@ -28,31 +28,48 @@ quiz:
     - content: "Bash script"
       isCorrect: false
       explanation: "Bash scripts would either need to be run in Docker or as a parameter to a Run step."
+
   - content: "Which keywords are required for a valid `action.yml` file?"
     choices:
-    - content: "name, runs, composite"
+    - content: "`name`, `runs`, `composite`"
       isCorrect: false
       explanation: "Composite isn't a required keyword for a valid `action.yml` file."
-    - content: "name, runs, description"
+    - content: "`name`, `runs`, `description`"
       isCorrect: true
       explanation: "These are the three required keywords for a valid `action.yml` file."
-    - content: "name, description, branding"
+    - content: "`name`, `description`, `branding`"
       isCorrect: false
       explanation: "Branding isn't a required keyword for a valid `action.yml` file."
-    - content: "name, description, composite"
+    - content: "`name`, `description`, `composite`"
       isCorrect: false
       explanation: "Composite isn't a required keyword for a valid `action.yml` file."
+
   - content: "Which workflow command would set the debug message to **This is an error message**?"
     choices:
-    - content: echo "::error::This is an error message"
+    - content: "echo::error::This is an error message"
       isCorrect: true
       explanation: "This syntax is correct for this workflow command."
-    - content: echo "error=This is an error message"
+    - content: "echo error=This is an error message"
       isCorrect: false
-      explanation: "This syntax is improper for a workflow command."
-    - content: echo "::error::message=This is an error message"
+      explanation: "This syntax is incorrect for a workflow command."
+    - content: "echo::error::message=This is an error message"
       isCorrect: false
-      explanation: "This syntax is improper for a workflow command."
-    - content: echo "::error::This is an error message::"
+      explanation: "This syntax is incorrect for a workflow command."
+    - content: "echo::error::This is an error message::"
       isCorrect: false
-      explanation: "This syntax is improper for a workflow command."
+      explanation: "This syntax is incorrect for a workflow command."
+
+  - content: "Which file is used to define a composite action?"
+    choices:
+    - content: "Dockerfile"
+      isCorrect: false
+      explanation: "Dockerfiles are used for Docker container actions, not composite actions."
+    - content: "action.yml"
+      isCorrect: true
+      explanation: "Composite actions are defined in an action.yml file, which specifies the inputs, outputs, and steps of the action."
+    - content: "workflow.yml"
+      isCorrect: false
+      explanation: "workflow.yml files define workflows, not actions."
+    - content: "package.json"
+      isCorrect: false
+      explanation: "package.json is used for JavaScript actions, not composite actions."

learn-pr/github/github-actions-automate-tasks/4-knowledge-check.yml

@@ -54,3 +54,31 @@ quiz:
     - content: "Opening an issue"
       isCorrect: false
       explanation: "Event triggers use Git references, and opening an issue produces a Git reference."
+  - content: "What are the two types of manual events that can trigger a GitHub Actions workflow?"
+    choices:
+    - content: "workflow_run and push_manual"
+      isCorrect: false
+      explanation: "workflow_run is an event that triggers when another workflow completes, not a manual event. repository_run is not a valid GitHub Actions event."
+    - content: "workflow_dispatch and repository_dispatch"
+      isCorrect: true
+      explanation: "GitHub Actions supports these two manual event triggers: workflow_dispatch allows manual triggering from the GitHub UI or API with customizable input parameters, and repository_dispatch enables workflows to be triggered by external systems via POST requests to the GitHub API."
+    - content: "manual_run and external_trigger"
+      isCorrect: false
+      explanation: "Neither manual_run nor external_trigger are valid GitHub Actions event types."
+    - content: "workflow_trigger and repository_webhook"
+      isCorrect: false
+      explanation: "workflow_trigger doesn't exist in GitHub Actions. While repository_webhook sounds similar to webhooks, the correct term for the external API-triggered event is repository_dispatch."
+  - content: "What is the primary benefit of using GitHub's larger hosted runners?"
+    choices:
+    - content: "They provide additional CPU and memory resources for running resource-intensive jobs."
+      isCorrect: true
+      explanation: "Larger runners offer increased CPU and memory, allowing you to run workflows that require more resources than standard runners provide."
+    - content: "GitHub's larger runners are available at no additional cost beyond standard runners."
+      isCorrect: false
+      explanation: "Larger runners incur additional costs based on their usage, unlike standard runners which may be included in your plan."
+    - content: "Larger runners come with completely different pre-installed tools compared to standard runners."
+      isCorrect: false
+      explanation: "These larger runners maintain compatibility with existing workflows by including the same preinstalled tools as standard `ubuntu-latest` runners."
+    - content: "Repository-level policies cannot be configured to control access to larger runners."
+      isCorrect: false
+      explanation: "To control access to larger runners, you can configure repository or organization-level policies, helping you manage costs and access effectively."

learn-pr/github/github-actions-ci/4-knowledge-check.yml

@@ -64,3 +64,19 @@ quiz:
     - content: "5"
       isCorrect: false
       explanation: "Each operating system is paired with each version of Node for a total of 6 builds."
+  - content: "How can you pass data between jobs in a GitHub Actions workflow?"
+    choices:
+    - content: "By using the `needs` keyword"
+      isCorrect: false
+      explanation: "The `needs` keyword specifies the order in which jobs run, but it doesn't pass data between jobs."
+    - content: "By using the `outputs` keyword"
+      isCorrect: true
+      explanation: "The `outputs` keyword allows you to pass data between jobs in a GitHub Actions workflow."
+    - content: "By using the `env` keyword"
+      isCorrect: false
+      explanation: "The `env` keyword sets environment variables for a job, but it doesn't pass data between jobs."
+    - content: "By using the `secrets` keyword"
+      isCorrect: false
+      explanation: "The `secrets` keyword allows you to access secrets in a job, but it doesn't pass data between jobs."
+     
+   

learn-pr/github/manage-github-actions-enterprise/knowledge-check.yml

@@ -3,7 +3,7 @@ uid: learn.github.manage-github-actions-enterprise.knowledge-check
 title: Module assessment
 metadata:
   title: Module assessment
-  description: Check what you've learned.
+  description: Check what you learned.
   ms.date: 11/21/2024
   author: a-a-ron
   ms.author: aastewar
@@ -14,21 +14,6 @@ content: |
 quiz:
   title: Check your knowledge
   questions:
-    - content: "Which of the following is a feature unique to GitHub Enterprise Cloud (GHEC)?"
-      choices:
-        - content: "Requires on-premises deployment and infrastructure management"
-          isCorrect: false
-          explanation: "Incorrect. This describes GitHub Enterprise Server (GHES), not GHEC. GHEC is hosted and managed by GitHub in the cloud."
-        - content: "Provides centralized user management with identity provider integration"
-          isCorrect: true
-          explanation: "GHEC supports centralized user management and integrates with identity providers using SAML (for SSO) and SCIM (for user provisioning), which is a key feature of cloud-hosted enterprise solutions."
-        - content: "Must be installed and maintained by the organization's IT team"
-          isCorrect: false
-          explanation: "Incorrect. GHEC is maintained by GitHub and requires no installation or infrastructure management by the organization."
-        - content: "Operates entirely within a private cloud environment"
-          isCorrect: false
-          explanation: "Incorrect. GHEC operates in GitHub’s public cloud infrastructure, not a private cloud."
-
     - content: "What actions can you take at enterprise level to manage the use of GitHub Actions in your enterprise instance?"
       choices:
         - content: "Create workflow templates"
@@ -48,65 +33,109 @@ quiz:
           explanation: "Correct. Custom labels can be used when you need to run jobs on runners that have specific capabilities."
         - content: "Add proxy configurations to your runners after they start."
           isCorrect: false
-          explanation: "Incorrect. If you need a self-hosted runner to communicate with GitHub via a proxy server, you must add all proxy configurations to your runner before starting it."
+          explanation: "Incorrect. You must add all proxy configurations to your runner before starting it."
         - content: "Add the IP address or IP address range of your runners at repository level."
           isCorrect: false
-          explanation: "Incorrect. If your organization has configured an IP allowlist, you must add the IP address or IP address range of your self-hosted runners to the IP allowlist. IP allowlists are found in an organization's Settings."
+          explanation: "Incorrect. This action is managed at the organization level in IP allowlists."
 
     - content: "What are encrypted secrets?"
       choices:
-        - content: "Encrypted secrets are authentication tokens you can generate in your account settings."
+        - content: "Authentication tokens you can generate in your account settings."
           isCorrect: false
-          explanation: "Incorrect. The authentication tokens you can create in your account settings are personal access tokens (PATs)."
-        - content: "Encrypted secrets are the equivalent of SSH keys in GitHub."
+          explanation: "Incorrect. This definition matches personal access tokens (PATs)."
+        - content: "The equivalent of SSH keys in GitHub."
           isCorrect: false
-          explanation: "Incorrect. SSH keys are also called SSH keys in GitHub."
-        - content: "Encrypted secrets are encrypted environment variables you can create to store sensitive information."
+          explanation: "Incorrect. SSH keys are separate and named accordingly."
+        - content: "Encrypted environment variables for storing sensitive information."
           isCorrect: true
-          explanation: "Correct. Once created, encrypted secrets become available for use in your workflows and actions at the level at which they were created (organization or repository)."
+          explanation: "Correct. You can securely scope them by repository, organization, or environment."
 
-    - content: What is a key benefit of using **reusable workflows** in GitHub Actions?
+    - content: "Which credential type poses the greatest security risk if used in GitHub Actions?"
       choices:
-        - content: Prevents any external contributors from running workflows
+        - content: "Repository deploy keys"
           isCorrect: false
-          explanation: Reusable workflows improve standardization, but they do not automatically block external contributors. Security settings must be configured separately.
-        - content: Reduces redundancy and maintenance overhead
+          explanation: "Incorrect. These credentials are scoped and safer for single-repo use."
+        - content: "Personal access token (classic)"
           isCorrect: true
-          explanation: Reusable workflows help avoid repetitive configuration across multiple repositories, reducing maintenance effort.
-        - content: Can only be used in the same repository where they are defined
+          explanation: "Correct. These credentials have broad access, making them riskier."
+        - content: "GitHub App tokens"
           isCorrect: false
-          explanation: Reusable workflows can be referenced from a different repository, allowing broader reuse.
-        - content: Automatically restricts all workflows to internal users
+          explanation: "Incorrect. These credentials are more granular and preferred for security."
+        - content: "GITHUB_TOKEN"
           isCorrect: false
-          explanation: GitHub does not enforce internal-only workflow execution unless explicitly configured.
+          explanation: "Incorrect. It is scoped and managed automatically."
 
-    - content: What is a primary benefit of using **GitHub-hosted runners** instead of self-hosted runners?
+    - content: "Which feature enforces that tests pass before code can be merged?"
       choices:
-        - content: Full control over hardware and software configuration
+        - content: "Organization secrets"
           isCorrect: false
-          explanation: Full control is a feature of self-hosted runners.
-        - content: Ability to access internal/private networks
+          explanation: "Incorrect. They handle credentials, not enforcement of tests."
+        - content: "Repository rule sets"
+          isCorrect: true
+          explanation: "Correct. Rule sets can enforce status checks before merges."
+        - content: "Workflow templates"
+          isCorrect: false
+          explanation: "Incorrect. These aid reuse, not enforcement."
+        - content: "Runner groups"
+          isCorrect: false
+          explanation: "Incorrect. They help manage runners, not enforce rules."
+
+    - content: "Which of the following is unique to GitHub Enterprise Cloud (GHEC)?"
+      choices:
+        - content: "Requires on-premises infrastructure"
           isCorrect: false
-          explanation: GitHub-hosted runners do not have direct access to internal networks.
-        - content: Automatic updates for the OS and preinstalled packages
+          explanation: "Incorrect. That describes GitHub Enterprise Server."
+        - content: "Centralized user management with identity provider integration"
           isCorrect: true
-          explanation: GitHub-hosted runners are automatically updated by GitHub, including OS patches and preinstalled tools.
-        - content: Custom installation of non-standard software
+          explanation: "Correct. GHEC integrates with identity providers using SAML (Security Assertion Markup Language)."
+        - content: "IT teams must install it."
+          isCorrect: false
+          explanation: "Incorrect. GitHub hosts and manages GHEC."
+        - content: "Runs in a private cloud"
           isCorrect: false
-          explanation: Custom installation is supported with self-hosted runners, not GitHub-hosted ones.
+          explanation: "Incorrect. GHEC runs on GitHub’s public cloud."
 
-    - content: What is the best practice when managing **encrypted secrets** in GitHub Actions?
+    - content: "What is a key benefit of using reusable workflows?"
       choices:
-        - content: Print secrets in workflow logs to assist with debugging
+        - content: "Blocks external contributors automatically"
           isCorrect: false
-          explanation: Secrets should never be exposed in logs.
-        - content: Use the same secret across all repositories for consistency
+          explanation: "Incorrect. Security must be separately configured."
+        - content: "Reduces redundancy and maintenance overhead"
+          isCorrect: true
+          explanation: "Correct. Reusable workflows simplify workflow reuse."
+        - content: "Only usable in the same repository"
+          isCorrect: false
+          explanation: "Incorrect. They can be reused across repositories."
+        - content: "Restricts workflows to internal users"
+          isCorrect: false
+          explanation: "Incorrect. This behaviour is configurable, not default."
+
+    - content: "What is a benefit of using GitHub-hosted runners?"
+      choices:
+        - content: "Full control over hardware"
+          isCorrect: false
+          explanation: "Incorrect. That benefit is for self-hosted runners."
+        - content: "Internal network access"
           isCorrect: false
-          explanation: Sharing the same secret increases security risk and violates the principle of least privilege.
-        - content: Limit access by defining secrets at the lowest necessary level
+          explanation: "Incorrect. GitHub-hosted runners do not have this benefit."
+        - content: "Automatic OS and package updates"
           isCorrect: true
-          explanation: Scoping secrets appropriately minimizes exposure and enhances security.
-        - content: Store secrets in the GitHub Actions log archive
+          explanation: "Correct. GitHub maintains hosted runner environments."
+        - content: "Install custom software"
           isCorrect: false
-          explanation: Storing secrets in logs is unsafe and not a recommended practice.
+          explanation: "Incorrect. That feature is supported on self-hosted runners."
 
+    - content: "What is a best practice for managing encrypted secrets?"
+      choices:
+        - content: "Print them in logs for debugging"
+          isCorrect: false
+          explanation: "Incorrect. Never expose secrets in logs."
+        - content: "Reuse the same secret across all repos"
+          isCorrect: false
+          explanation: "Incorrect. This increases risk."
+        - content: "Scope secrets to the lowest level needed"
+          isCorrect: true
+          explanation: "Correct. This limits exposure."
+        - content: "Store secrets in archived workflow logs"
+          isCorrect: false
+          explanation: "Incorrect. That approach is a security vulnerability."