What is a valid scenario regarding environment secrets?
Environment secrets are scoped to GitHub Actions environments and can be protected by environment protection rules. If an environment requires reviewers, a job that references that environment cannot access its environment secrets until the required approval is granted. This makes option A correct. Option B is incorrect because environment secrets are made available to jobs that reference the protected environment, not selectively to only one specific step by default. Option C is not the purpose of environment secrets; they are not specifically for connecting to GitHub Enterprise Server. Option D is also incorrect because GitHub environment secrets do not automatically pull from Azure Key Vault without additional integration or custom workflow logic. This topic covers environment protection, secrets, and deployment governance.
================
What are the two types of environment protection rules you can configure? (Choose two.)
Required reviewers is a protection rule where you can specify that certain individuals or teams must review and approve the workflow run before it can proceed. This is used to enforce approvals before certain steps or environments are accessed.
Wait timer is a protection rule that introduces a delay before a workflow can proceed to the next stage. This is useful for adding time-based constraints to the deployment process or ensuring that certain conditions are met before a workflow continues.
As a DevOps engineer, you are developing workflows to build an application. You have a requirement to create the build targeting multiple node versions. Which code block should you use to define the workflow?
The correct GitHub Actions syntax for running a job across multiple Node.js versions is strategy.matrix. The matrix values are referenced at runtime through the matrix context, so node-version: ${{ matrix.node-ver }} is correct. Option A defines the matrix correctly but references it incorrectly through strategy.node-ver; matrix values are not accessed through the strategy context. Option C uses matrix-strategy, which is not a valid GitHub Actions workflow key. Option D reverses the structure by putting strategy under matrix, which is invalid. This question tests matrix strategy syntax, dynamic job configuration, and using matrix values as inputs to actions such as actions/setup-node. GitHub defines jobs.<job_id>.strategy.matrix as the proper matrix mechanism.
What is a role of GitHub Marketplace when using GitHub Actions?
GitHub Marketplace is used to discover, share, and publish reusable automation, including GitHub Actions created by GitHub, vendors, and the community. Option C best describes this role. Marketplace does not exist only for billing, so option B is too narrow and incorrect. Option A is also wrong because Marketplace does not merely restrict third-party actions to public repositories; action usage is governed by repository, organization, or enterprise Actions policies. Option D is false because Marketplace does not bypass repository permissions or automatically deploy workflows into repositories. In exam terms, Marketplace is part of the automation reuse and action discovery domain: developers use it to find trusted or verified actions rather than building every integration manually. GitHub documents Marketplace as a place to publish and share actions with the community.
As a developer, how can you identify a Docker container action on GitHub?
In a Docker container action, the action.yml file includes the runs.using field, which is set to docker to specify that the action runs inside a Docker container. This is the key indicator that the action is a Docker container action.
Charles Wright
13 days agoEdward Rogers
26 days agoMelissa Rivera
1 month agoDeborah Sanchez
2 months agoJessica Wilson
3 months agoGeorge Johnson
3 months agoAmanda Rodriguez
4 months agoAmanda Hall
4 months agoAmy Rodriguez
5 months agoJessica Williams
5 months agoBrian Martin
5 months agoChristopher Roberts
5 months agoMelissa King
5 months agoKenneth Nelson
5 months agoHarold Parker
5 months agoHeather Flores
5 months agoLeeann
6 months agoKip
6 months agoDetra
6 months agoTijuana
7 months agoDorsey
7 months agoAbraham
7 months agoSonia
8 months agoMartin
8 months agoPenney
8 months agoKaycee
8 months agoMarg
9 months agoJohnathon
9 months agoOlga
9 months agoJolene
9 months agoTitus
9 months agoAntonio
10 months agoJenelle
10 months agoCherrie
10 months agoElouise
10 months agoLeonard
11 months agoJulianna
11 months agoBobbye
11 months agoDesirae
11 months agoJeannine
12 months agoKatlyn
12 months agoBernadine
1 year agoLisbeth
1 year agoIra
1 year agoGilbert
1 year agoNoel
1 year agoGabriele
1 year agoGaynell
1 year ago