QuizzesSecrets, Environments & OIDC — Concept Check
intermediate
cicd

Secrets, Environments & OIDC — Concept Check

Questions on Secrets, Environments & OIDC. GitHub Actions Secrets store sensitive values encrypted at rest. Environments add deployment protection rules with manual approval gates. OIDC enables keyless authentication to cloud providers.

8 minutes 8 questions Pass at 70%
Time Limit
8 minutes - timer starts when you begin
Change Answers Freely
Revisit and change any answer before submitting
Full Review After Submit
Correct answers and explanations shown for every question
Auto-submit on timeout
Quiz submits automatically when time runs out

Questions in this quiz

8 questions on Secrets, Environments & OIDC — Concept Check. Work through them here, then start the quiz to answer them and see your score.

  1. 1.In a GitHub workflow, a deployment to the production environment is pending approval. What happens if one of the required reviewers rejects the deployment?

    • AThe deployment is automatically retried.
    • BThe deployment is halted and fails.
    • CThe deployment proceeds after a wait timer.
    • DThe deployment is approved by default.
  2. 2.A developer wants to use a secret in their GitHub Actions workflow but notices it appears in the logs. What might they have done wrong?

    • AUsed the secret in an 'env' block.
    • BStored the secret at the organization level.
    • CUsed the secret directly in a 'run' command.
    • DConfigured the secret with incorrect permissions.
  3. 3.You are configuring a GitHub Actions workflow with a GITHUB_TOKEN. What is the best practice for setting its permissions?

    • AUse default permissions for simplicity.
    • BSet permissions to 'permissive' by default.
    • CRestrict permissions to the minimum required.
    • DGrant all permissions to avoid issues.
  4. 4.A team uses GitHub Environments to manage deployments. What is a key benefit of using environments like 'staging' and 'production'?

    • AThey allow for different deployment scripts per environment.
    • BThey automatically deploy code without human intervention.
    • CThey provide deployment protection rules and approval gates.
    • DThey enable storing secrets in plain text for easy access.
  5. 5.A developer mistakenly believes that organization secrets are available to all repositories by default. What is the actual scope of organization secrets?

    • AAvailable to all environments within a repository.
    • BAvailable only to specified repositories in the organization.
    • CAvailable to all repositories in the organization by default.
    • DAvailable to all workflows within a repository.
  6. 6.A workflow is set to deploy to production but is stuck waiting. What could be the reason?

    • AThe required reviewers haven't approved yet.
    • BThe wait timer hasn't expired.
    • CThe deployment branch is incorrect.
    • DThe environment secrets are missing.
  7. 7.What is a potential risk of storing long-lived cloud credentials in GitHub Secrets?

    • AThey can lead to privilege escalation if compromised.
    • BThey are encrypted at rest.
    • CThey are automatically masked in logs.
    • DThey can be accessed by unauthorized users.
  8. 8.A developer sets up a GitHub Actions workflow and wants to ensure secrets are not exposed. Which practice should they follow?

    • APrint secrets to logs for debugging.
    • BUse secrets in the 'env' block of a job.
    • CStore secrets in plain text for easy access.
    • DUse floating tags for third-party actions.