You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/github/manage-github-actions-enterprise/knowledge-check.yml
+49-46Lines changed: 49 additions & 46 deletions
Original file line number
Diff line number
Diff line change
@@ -15,49 +15,52 @@ quiz:
15
15
title: Check your knowledge
16
16
questions:
17
17
- content: "Which of the following is a feature unique to GitHub Enterprise Cloud (GHEC)?"
18
-
choices:
19
-
- content: "Requires on-premises deployment and infrastructure management"
20
-
isCorrect: false
21
-
explanation: "Incorrect. This describes GitHub Enterprise Server (GHES), not GHEC. GHEC is hosted and managed by GitHub in the cloud."
22
-
- content: "Provides centralized user management with identity provider integration"
23
-
isCorrect: true
24
-
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."
25
-
- content: "Must be installed and maintained by the organization's IT team"
26
-
isCorrect: false
27
-
explanation: "Incorrect. GHEC is maintained by GitHub and requires no installation or infrastructure management by the organization."
28
-
- content: "Operates entirely within a private cloud environment"
29
-
isCorrect: false
30
-
explanation: "Incorrect. GHEC operates in GitHub’s public cloud infrastructure, not a private cloud."
31
-
- content: "What actions can you take at enterprise level to manage the use of GitHub Actions in your enterprise instance?"
32
-
choices:
33
-
- content: "Create workflow templates"
34
-
isCorrect: false
35
-
explanation: "Incorrect. Workflow templates are created at organizational level."
36
-
- content: "Configure a GitHub Actions use policy"
37
-
isCorrect: true
38
-
explanation: "Correct. GitHub Actions use policies enable you to restrict access to GitHub Actions to specific organizations in your instance."
39
-
- content: "Manually sync public actions in Enterprise Cloud"
40
-
isCorrect: false
41
-
explanation: "Incorrect. Public actions are automatically synced in Enterprise Cloud. Only with Enterprise Server do you have the possibility to manually sync public actions instead of automatically."
42
-
- content: "What actions can you take to configure self-hosted runners for your enterprise use?"
43
-
choices:
44
-
- content: "Create and add custom labels to your runners"
45
-
isCorrect: true
46
-
explanation: "Correct. Custom labels can be used when you need to run jobs on runners that have specific capabilities."
47
-
- content: "Add proxy configurations to your runners after they start."
48
-
isCorrect: false
49
-
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."
50
-
- content: "Add the IP address or IP address range of your runners at repository level."
51
-
isCorrect: false
52
-
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."
53
-
- content: "What are encrypted secrets?"
54
-
choices:
55
-
- content: "Encrypted secrets are authentication tokens you can generate in your account settings."
56
-
isCorrect: false
57
-
explanation: "Incorrect. The authentication tokens you can create in your account settings are personal access tokens (PATs)."
58
-
- content: "Encrypted secrets are the equivalent of SSH keys in GitHub."
59
-
isCorrect: false
60
-
explanation: "Incorrect. SSH keys are also called SSH keys in GitHub."
61
-
- content: "Encrypted secrets are encrypted environment variables you can create to store sensitive information."
62
-
isCorrect: true
63
-
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)."
18
+
choices:
19
+
- content: "Requires on-premises deployment and infrastructure management"
20
+
isCorrect: false
21
+
explanation: "Incorrect. This describes GitHub Enterprise Server (GHES), not GHEC. GHEC is hosted and managed by GitHub in the cloud."
22
+
- content: "Provides centralized user management with identity provider integration"
23
+
isCorrect: true
24
+
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."
25
+
- content: "Must be installed and maintained by the organization's IT team"
26
+
isCorrect: false
27
+
explanation: "Incorrect. GHEC is maintained by GitHub and requires no installation or infrastructure management by the organization."
28
+
- content: "Operates entirely within a private cloud environment"
29
+
isCorrect: false
30
+
explanation: "Incorrect. GHEC operates in GitHub’s public cloud infrastructure, not a private cloud."
31
+
32
+
- content: "What actions can you take at enterprise level to manage the use of GitHub Actions in your enterprise instance?"
33
+
choices:
34
+
- content: "Create workflow templates"
35
+
isCorrect: false
36
+
explanation: "Incorrect. Workflow templates are created at organizational level."
37
+
- content: "Configure a GitHub Actions use policy"
38
+
isCorrect: true
39
+
explanation: "Correct. GitHub Actions use policies enable you to restrict access to GitHub Actions to specific organizations in your instance."
40
+
- content: "Manually sync public actions in Enterprise Cloud"
41
+
isCorrect: false
42
+
explanation: "Incorrect. Public actions are automatically synced in Enterprise Cloud. Only with Enterprise Server do you have the possibility to manually sync public actions instead of automatically."
43
+
44
+
- content: "What actions can you take to configure self-hosted runners for your enterprise use?"
45
+
choices:
46
+
- content: "Create and add custom labels to your runners"
47
+
isCorrect: true
48
+
explanation: "Correct. Custom labels can be used when you need to run jobs on runners that have specific capabilities."
49
+
- content: "Add proxy configurations to your runners after they start."
50
+
isCorrect: false
51
+
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."
52
+
- content: "Add the IP address or IP address range of your runners at repository level."
53
+
isCorrect: false
54
+
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."
55
+
56
+
- content: "What are encrypted secrets?"
57
+
choices:
58
+
- content: "Encrypted secrets are authentication tokens you can generate in your account settings."
59
+
isCorrect: false
60
+
explanation: "Incorrect. The authentication tokens you can create in your account settings are personal access tokens (PATs)."
61
+
- content: "Encrypted secrets are the equivalent of SSH keys in GitHub."
62
+
isCorrect: false
63
+
explanation: "Incorrect. SSH keys are also called SSH keys in GitHub."
64
+
- content: "Encrypted secrets are encrypted environment variables you can create to store sensitive information."
65
+
isCorrect: true
66
+
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)."
0 commit comments