GitHub Actions Secrets and Environment Variables

1. What is the purpose of the GITHUB_ENV file in GitHub Actions?

To persist environment variables across steps in a job

To store workflow configuration

To define GitHub API authentication

To configure runner specifications

2. Organization-level secrets override repository-level secrets with the same name.

True

False

3. You can use conditional logic to access secrets only when specific conditions are met.

True

False

4. Secrets can be rotated or updated by editing their values in the GitHub UI.

True

False

5. Environment variables defined at the workflow level are accessible in all jobs.

True

False

6. GitHub Actions automatically masks values matching a secret pattern in logs.

True

False

7. What scope would you use for a secret needed by multiple repositories in an organization?

Organization-level secret

Repository-level secret

Environment-level secret

Runner-level secret

8. How do you pass a secret to a Docker container in a workflow?

Using the --env flag with the secret reference

Adding it to the Dockerfile

Committing it to the repository

Storing it in docker-compose.yml

9. What is a best practice when using secrets in GitHub Actions workflows?

Avoid logging or echoing secrets

Store secrets in the repository README

Use secrets for all variables regardless of sensitivity

Commit secrets to version control

10. Can you access secrets from outside the GitHub Actions workflow context?

No, secrets are only available within GitHub Actions

Yes, through the GitHub REST API

Yes, if you have repository admin access

Only in public repositories

11. What is the primary purpose of GitHub Actions secrets?

To store sensitive data like API keys and tokens securely

To document workflow steps for readability

To cache dependencies between workflow runs

To define the runner operating system

12. Which command-line tool can be used to set environment variables in a GitHub Actions shell step?

Echo "VAR=value" >> $GITHUB_ENV

Export VAR=value

Set VAR=value

Declare VAR=value

13. What happens to secrets when they are printed in logs?

GitHub automatically masks them

They appear in plaintext

They are encrypted in logs

They are deleted from logs

14. At which levels can you define environment variables in a workflow?

Workflow, job, and step levels

Only at the workflow level

Only at the step level

Runner and container levels only

15. What syntax is used to reference an environment variable in a workflow?

${{ env.VARIABLE_NAME }}

${{ secrets.VARIABLE_NAME }}

${{ github.env.VARIABLE_NAME }}

${{ runner.VARIABLE_NAME }}

16. How do environment variables differ from secrets in GitHub Actions?

Secrets are encrypted; environment variables are plaintext

Environment variables are faster to access

Secrets can only be used in scripts

Environment variables require organization approval

17. What is the maximum size limit for a GitHub Actions secret?

256 bytes

1 KB

64 KB

1 MB

18. Can you modify a secret after it has been created in GitHub?

Yes, by editing the secret value directly

No, you must delete and recreate it

Only if you have admin permissions

Only within 24 hours of creation

19. What scope level is available when creating a GitHub Actions secret?

Repository, environment, and organization

Global and local only

Workflow and step level only

Runner and container level

20. How do you reference a secret named API_KEY in a GitHub Actions workflow?

${{ secrets.API_KEY }}

${{ env.API_KEY }}

${{ github.API_KEY }}

${{ inputs.API_KEY }}

GitHub Actions Secrets and Environment Variables Quiz

1. What is the purpose of the GITHUB_ENV file in GitHub Actions?

2.

What first name or nickname would you like us to use?

2. Organization-level secrets override repository-level secrets with the same name.

3. You can use conditional logic to access secrets only when specific conditions are met.

4. Secrets can be rotated or updated by editing their values in the GitHub UI.

5. Environment variables defined at the workflow level are accessible in all jobs.

6. GitHub Actions automatically masks values matching a secret pattern in logs.

7. What scope would you use for a secret needed by multiple repositories in an organization?

8. How do you pass a secret to a Docker container in a workflow?

9. What is a best practice when using secrets in GitHub Actions workflows?

10. Can you access secrets from outside the GitHub Actions workflow context?

11. What is the primary purpose of GitHub Actions secrets?

12. Which command-line tool can be used to set environment variables in a GitHub Actions shell step?

13. What happens to secrets when they are printed in logs?

14. At which levels can you define environment variables in a workflow?

15. What syntax is used to reference an environment variable in a workflow?

16. How do environment variables differ from secrets in GitHub Actions?

17. What is the maximum size limit for a GitHub Actions secret?

18. Can you modify a secret after it has been created in GitHub?

19. What scope level is available when creating a GitHub Actions secret?

20. How do you reference a secret named API_KEY in a GitHub Actions workflow?