Custom environment variables can be defined at multiple levels within a workflow file including:
(Each answer presents a complete solution. Choose three.)

• A.top level.
• B.step level.
• C.default level.
• D.runner level.
• E.job level.
• F.stage level.

Comment: *

Name: *

Email: *

Verification: *

Which GitHub Actions capability prevents secrets from appearing in workflow logs?

• A.Manual approval for secret log output
• B.GitHub Audit Log
• C.Default secret masking in logs
• D.Encrypted secrets written to logs

Comment: *

Name: *

Email: *

Verification: *

What repository visibility is required for a GitHub Action to be listed on GitHub Marketplace?

• A.Verified creator status
• B.Metadata in a subfolder
• C.Public repository
• D.Use GitHub Container Registry

Comment: *

Name: *

Email: *

Verification: *

Which of the following scenarios requires a developer to explicitly use the GITHUB_TOKEN or github.token secret within a workflow? (Choose two.)

• A.passing the GITHUB_TOKEN secret to an action that requires a token as an input
• B.making an authenticated GitHub API request
• C.checking out source code with the actions/checkout@v3 action
• D.assigning non-default permissions to the GITHUB_TOKEN

Comment: *

Name: *

Email: *

Verification: *

Which step is using the dbserver environment variable correctly?

• A.steps:
  - name: Hello world
  run: echo $dbserver
  variables:
  dbserver: orgserver1
• B.steps:
  - name: Hello world
  run: echo $dbserver
  env:
  - name: dbserver
  value: orgserver1
• C.steps:
  - name: Hello world
  run: echo $dbserver
  environment:
  dbserver: orgserver1
• D.steps:
  - name: Hello world
  run: echo $dbserver
  env:
  dbserver: orgserver1

Comment: *

Name: *

Email: *

Verification: *