GitHub GITHUB-ACTIONS Online Practice Questions and Exam Preparation

GitHub GITHUB-ACTIONS Online Questions & Answers

• Question 51:

  How can GitHub Actions encrypted secrets be used in if: conditionals within a workflow job?

  A. Set the encrypted secret as a job-level environment variable and then reference the environment variable within the conditional statement.
  B. Create a job dependency that exposes the encrypted secret as a job output, which can then be leveraged in a subsequent dependent job.
  C. Use the secrets context within the conditional statement, e.g. ${{ secrets.MySuperSecret }}.
  D. Use a workflow command to expose the encrypted secret via a step's output parameter and then use the step output in the job's if: conditional.
  C. Use the secrets context within the conditional statement, e.g. ${{ secrets.MySuperSecret }}.

  ---

  GitHub Actions encrypted secrets can be accessed in workflows using thesecretscontext. You can directly reference the secret within anif:conditional using${{ secrets.MySuperSecret }}to determine whether a job or step should run based on the secret's value.

• Question 52:

  What metadata file in a custom action defines the main entry point?

  A. action.js
  B. index.js
  C. action.yml
  D. main.yml
  C. action.yml

  ---

  The action.yml file is the metadata file in a custom GitHub Action that defines the main entry point, including information such as the inputs, outputs, description, and the runs key that specifies the main entry point (e.g., a script or a Docker container).

• Question 53:

  Scheduled workflows in GitHub Actions run on the _______.

  A. latest commit and branch on which the workflow was triggered
  B. latest commit from the branch named schedule
  C. latest commit from the branch named main
  D. specified commit and branch from the workflow YAML file
  E. latest commit on the default or base branch
  A. latest commit and branch on which the workflow was triggered

  ---

  Scheduled workflows in GitHub Actions are triggered automatically at specified times defined in the on.schedule event. They always run on the latest commit of the default branch (usually main or master) unless another branch is explicitly defined in the workflow configuration. In other words, when the schedule event occurs, the workflow runs using the latest commit on the branch that triggers the workflow, typically the default branch.

• Question 54:

  Which of the following is true about using strategy.fail-fast in a matrix job?

  A. It allows failed jobs to automatically restart.
  B. It stops all in-progress jobs if one matrix job fails.
  C. It retries failed matrix combinations automatically.
  D. It disables parallel job execution.
  B. It stops all in-progress jobs if one matrix job fails.

  ---

  The fail-fast option in a matrix strategy controls whether GitHub Actions cancels all other in-progress matrix jobs if one job fails. This saves compute time and resources during testing across multiple combinations.

• Question 55:

  As a developer, you have a 10-MB data set that is required in a specific workflow. Which steps should you perform so the dataset is stored encrypted and can be decrypted during the workflow? (Choose three.)

  A. Encrypt the dataset.
  B. Leverage the actions/download-secret action in the workflow.
  C. Store the dataset in a GitHub encrypted secret.
  D. Store the encryption keys in a GitHub encrypted secret.
  E. Compress the dataset
  F. Commit the encrypted dataset to the same repository as the workflow
  G. Create a GitHub encrypted secret with the Large object option selected and upload the dataset.
  A. Encrypt the dataset.
  C. Store the dataset in a GitHub encrypted secret.
  D. Store the encryption keys in a GitHub encrypted secret.

  ---

  First, the dataset should be encrypted before being stored. This ensures that the data is protected when stored in a repository.

  The encrypted dataset can be stored in a GitHub secret, ensuring it is securely kept and not exposed publicly.

  The encryption key needed to decrypt the dataset should also be stored in a GitHub secret to maintain security during the workflow, allowing access only when needed.

• Question 56:

  Which workflow commands send information from the runner? (Choose two.)

  A. reading from environment variables
  B. setting a debug message
  C. populating variables in a Dockerfile
  D. setting output parameters
  B. setting a debug message
  D. setting output parameters

  ---

  Setting a debug message using ::debug:: command sends a message to the logs, helping with troubleshooting and providing insight into the workflow run. Setting output parameters using ::set-output sends data from a job step to subsequent steps or jobs, which can be used later in the workflow.

• Question 57:

  As a developer, you are designing a workflow and need to communicate with the runner machine to set environment variables, output values used by other actions, add debug messages to the output logs, and other tasks. Which of the following options should you use?

  A. environment variables
  B. workflow commands
  C. self-hosted runners
  D. enable debug logging
  E. composite run step
  B. workflow commands

  ---

  Workflow commands are special commands that allow you to interact with the runner, set environment variables, output values, add debug messages, and perform other tasks within the workflow. These commands are used to modify the environment or influence the behavior of the GitHub Actions runner.

• Question 58:

  As a developer, how can you identify a Docker container action on GitHub?

  A. The action's repository includes @actions/core in the root directory.
  B. The action's repository name includes the keyword "Docker."
  C. The action.yml metadata file references a Dockerfile file.
  D. The action.yml metadata file has the runs.using value set to Docker.
  D. The action.yml metadata file has the runs.using value set to Docker.

  ---

  In a Docker container action, theaction.ymlfile includes theruns.usingfield, which is set todockerto specify that the action runs inside a Docker container. This is the key indicator that the action is a Docker container action.

• Question 59:

  Which files are required for a Docker container action in addition to the source code? (Choose two.)

  A. Dockerfile
  B. Actionfile
  C. metadata.yml
  D. action.yml
  A. Dockerfile
  D. action.yml

  ---

  Dockerfile: TheDockerfileis required for Docker container actions. It defines the environment for the action, specifying the base image, dependencies, and any commands to set up the action's runtime inside the container.

  action.yml: Theaction.ymlfile is required for all GitHub Actions, including Docker container actions. It contains metadata about the action, including the inputs, outputs, and the runtime environment (which in this case is Docker, defined underruns.using).

• Question 60:

  As a developer, you want to review the step that caused a workflow failure and the failed step's build logs. First navigate to the main page of the repository on GitHub. Which section contains the step failure information?

  A. Insights
  B. Code
  C. Actions
  D. Pull requests
  E. Issues
  C. Actions

  ---

  The Actions tab on the main page of the repository is where you can find detailed information about the workflow runs, including step failures and build logs. You can review the status of each job and step within the workflow, see the failure messages, and access logs for debugging.