Your organization has a secret that must be available to all the repositories within GitHub Actions workflows.
You need to store the secret. The solution must minimize administrative effort.
What should you do in GitHub?
The correct solution is to create an organization-level Actions secret. This minimizes administrative effort because the secret can be managed once at the organization level and made available to all repositories or selected repositories through an access policy. Option D gives the correct navigation path: organization page, Settings, Secrets and variables, then Actions. Option A would require duplicating the secret in every repository, increasing maintenance overhead and risk of inconsistent values. Option B is wrong because personal developer settings do not centrally expose a secret to all organization repositories. Option C is incomplete because the current GitHub path places Actions secrets under ''Secrets and variables,'' not just a generic ''Security > Secrets'' location. GitHub documents organization secrets and the repository access policy model for sharing them.
Which default environment variable specifies the branch or tag that triggered a workflow?
The GITHUB_REF environment variable specifies the branch or tag that triggered the workflow. It contains the full reference to the branch or tag, such as refs/heads/main for a branch or refs/tags/v1.0 for a tag.
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.
Charles Wright
1 month agoEdward Rogers
2 months agoMelissa Rivera
2 months agoDeborah Sanchez
3 months agoJessica Wilson
3 months agoGeorge Johnson
4 months agoAmanda Rodriguez
4 months agoAmanda Hall
5 months agoAmy Rodriguez
5 months agoJessica Williams
6 months agoBrian Martin
6 months agoChristopher Roberts
6 months agoMelissa King
5 months agoKenneth Nelson
6 months agoHarold Parker
6 months agoHeather Flores
6 months agoLeeann
7 months agoKip
7 months agoDetra
7 months agoTijuana
8 months agoDorsey
8 months agoAbraham
8 months agoSonia
8 months agoMartin
9 months agoPenney
9 months agoKaycee
9 months agoMarg
9 months agoJohnathon
10 months agoOlga
10 months agoJolene
10 months agoTitus
10 months agoAntonio
11 months agoJenelle
11 months agoCherrie
11 months agoElouise
11 months agoLeonard
11 months agoJulianna
12 months agoBobbye
12 months agoDesirae
1 year agoJeannine
1 year agoKatlyn
1 year agoBernadine
1 year agoLisbeth
1 year agoIra
1 year agoGilbert
1 year agoNoel
1 year agoGabriele
1 year agoGaynell
1 year ago