GitHub GITHUB-ACTIONS Online Practice Questions and Exam Preparation

GitHub GITHUB-ACTIONS Online Questions & Answers

• Question 11:

  What can be used to set a failed status of an action from its code?

  A. @actions/github toolkit
  B. JavaScript dist/ folder
  C. Dockerfile CMD
  D. a non-zero exit code
  E. output variable
  F. composite run step
  D. a non-zero exit code

  ---

  A non-zero exit code is used to set the status of an action to "failed" in GitHub Actions. When the action's script or code exits with a non-zero status, it indicates failure, and GitHub will mark the action as failed.

• Question 12:

  As a developer, you need to use GitHub Actions to deploy a microservice that requires runtime access to a secure token. This token is used by a variety of other microservices managed by different teams in different repos. To minimize management overhead and ensure the token is secure, which mechanisms should you use to store and access the token? (Choose two.)

  A. Store the token in a configuration file in a private repository. Use GitHub Actions to deploy the configuration file to the runtime environment.
  B. Store the token as a GitHub encrypted secret in the same repo as the code. Create a reusable custom GitHub Action to access the token by the microservice at runtime.
  C. Use a corporate non-GitHub secret store (e.g., HashiCorp Vault) to store the token. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.
  D. Store the token as a GitHub encrypted secret in the same repo as the code. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.
  E. Store the token as an organizational-level encrypted secret in GitHub. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.
  C. Use a corporate non-GitHub secret store (e.g., HashiCorp Vault) to store the token. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.
  E. Store the token as an organizational-level encrypted secret in GitHub. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.

  ---

  Using a corporate secret store like HashiCorp Vault provides a secure, centralized location for sensitive information. GitHub Actions can then retrieve and store the token securely during deployment by setting it as an environment variable, ensuring the token remains secure and accessible at runtime.

  Storing the token as an organizational-level encrypted secret in GitHub ensures it is accessible across multiple repositories, minimizing management overhead. GitHub Actions can then use this secret during deployment by setting it as an environment variable, allowing the microservice to access it securely at runtime.

• Question 13:

  Which of the following is the best way for an enterprise to prevent certain marketplace actions from running?

  A. Create a list of the actions that are restricted from being used as an enterprise policy. Every other action can be run.
  B. It is not possible; if an action is in the marketplace, its use cannot be restricted.
  C. Create a list that is maintained as a . yml file in a . github repository specified in the enterprise. Only these actions can be run.
  D. Create a list of the actions that are allowed to run as an enterprise policy. Only these actions can be run.
  D. Create a list of the actions that are allowed to run as an enterprise policy. Only these actions can be run.

  ---

  The best way for an enterprise to control which GitHub Actions run is by creating a list of approved actions as an enterprise policy. This approach restricts workflows to only use the actions that are explicitly allowed, ensuring security and compliance within the organization.

• Question 14:

  What are the two types of environment protection rules you can configure? (Choose two.)

  A. required reviewers
  B. branch protections
  C. wait timer
  D. artifact storage
  A. required reviewers
  C. wait timer

  ---

  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.

• Question 15:

  As a developer, your Actions workflow often reuses the same outputs or downloaded dependencies from one run to another. To cache dependencies for a job, you are using the GitHub cache action. Which input parameters are required for this action? (Choose two.)

  A. dependency: the name and version of a package to cache or restore
  B. key: the key created when saving a cache and the key used to search for a cache
  C. cache-hit: the copy action key used with restore parameter to restore the data from the cache
  D. path: the file path on the runner to cache or restore
  E. ref: the ref name of the branch to access and restore a cache created
  F. restore-keys: the copy action key used with cache parameter to cache the data
  B. key: the key created when saving a cache and the key used to search for a cache
  D. path: the file path on the runner to cache or restore

  ---

  The key is required because it uniquely identifies the cache. It is used to store and retrieve cached data. When creating or restoring a cache, you need to define a key that will be used to identify the cache. The path is the file path on the runner that you want to cache. This is where the cached files or dependencies are located and should be specified to tell GitHub where to store or retrieve the cache from.

• Question 16:

  What happens if a required secret referenced in a workflow is missing?

  A. The workflow skips the step silently.
  B. GitHub sets the secret's value to an empty string.
  C. The workflow fails immediately with an error.
  D. GitHub issues a warning but continues execution.
  C. The workflow fails immediately with an error.

  ---

  When a workflow references a secret that does not exist, the run fails with an error. GitHub enforces this strict behavior to prevent silent failures and maintain security integrity within workflows.

• Question 17:

  Your organization needs to simplify reusing and maintaining automation in your GitHub Enterprise Cloud. Which components can be directly reused across all repositories in an organization? (Choose three.)

  A. self-hosted runners
  B. actions stored m private repositories in the organization
  C. encrypted secrets
  D. custom Docker actions stored in GitHub Container Registry
  E. actions stored in an organizational partition in the GitHub Marketplace
  F. workflow templates
  B. actions stored m private repositories in the organization
  C. encrypted secrets
  F. workflow templates

  ---

  Actions stored in private repositories within the organization can be reused across all repositories by referencing them in workflows. This ensures a centralized way of maintaining custom actions.

  Encrypted secrets can be accessed across repositories in the same organization, making it easy to store sensitive data (like API keys or tokens) securely while allowing multiple workflows to access them.

  Workflow templates allow you to create reusable templates for workflows that can be shared across repositories within the organization. This makes it easier to standardize processes and automate them across multiple projects.

• Question 18:

  Which GitHub Actions command can mask sensitive data from appearing in logs?

  A. ::secure::
  B. ::hide::
  C. ::add-mask::
  D. ::secret::
  C. ::add-mask::

  ---

  The ::add-mask:: workflow command hides sensitive values (such as passwords or tokens) from appearing in logs. Once masked, these values will be replaced with asterisks (***) to maintain confidentiality.

• Question 19:

  Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. In which scenarios would temporarily disabling a workflow be most useful? (Choose two.)

  A. A workflow sends requests to a service that is down.
  B. A workflow error produces too many, or wrong, requests, impacting external services negatively.
  C. A workflow is configured to run on self-hosted runners
  D. A workflow needs to be changed from running on a schedule to a manual trigger
  E. A runner needs to have diagnostic logging enabled.
  A. A workflow sends requests to a service that is down.
  B. A workflow error produces too many, or wrong, requests, impacting external services negatively.

  ---

  If a workflow depends on an external service that is down, disabling the workflow temporarily will prevent it from running and sending requests to the service, thus avoiding failed requests or unnecessary retries. If a workflow is causing a negative impact on external services by generating too many requests or incorrect data due to a bug, temporarily disabling the workflow will stop this behavior while the issue is fixed.

• Question 20:

  As a DevOps engineer, you are developing a container action. You need to execute a cleanup script after completing the main script execution. Which code block should be used to define the cleanup script?

  

  A. Option A
  B. Option B
  C. Option C
  D. Option D
  A. Option A

  ---

  The correct syntax for specifying a cleanup script to be run after the main entry point is executed in a Docker- based GitHub Action is to use thepostkey. This ensures thatcleanup.shruns after the main script (main.sh) has completed.