GitHub GITHUB-ACTIONS Online Practice Questions and Exam Preparation

GitHub GITHUB-ACTIONS Online Questions & Answers

• Question 31:

  Which workflow command would output the debug message "action successfully debugged"?

  A. echo :debug::message=action successfully debugged"
  B. echo "debug-action successfully debugged"
  C. echo "::debug::action successfully debugged"
  D. echo ":debug:action successfully debugged:"
  C. echo "::debug::action successfully debugged"

  ---

  The ::debug:: syntax is used to output debug messages in GitHub Actions workflows. This command will print the message "action successfully debugged" in the debug logs when the workflow runs.

• Question 32:

  When reviewing an action for use, what file defines its available inputs and outputs?

  A. inputs.yml
  B. config.json
  C. defaults.json
  D. workflow.yml
  E. action.yml
  E. action.yml

  ---

  The action.yml file defines the inputs and outputs for a GitHub Action. This file contains metadata about the action, including the required inputs and outputs, as well as other configurations like the action's description, runs, and environment setup.

• Question 33:

  You have exactly one Windows x64 self-hosted runner, and it is configured with custom tools. Which syntax could you use in the workflow to target that runner?

  A. self-hosted: [windows-x64]
  B. runs-on: [self-hosted, windows, x64]
  C. runs-on: windows-latest
  D. self-hosted: [windows, x64]
  B. runs-on: [self-hosted, windows, x64]

  ---

  The runs-on keyword allows you to specify the operating system and other labels for the runner. By specifying self-hosted, windows, and x64, you are targeting a self-hosted Windows runner that matches these criteria, which aligns with the custom configuration of your self-hosted runner.

• Question 34:

  Which default environment variable specifies the branch or tag that triggered a workflow?

  A. GITHUB_TAG
  B. GITHUB_REF
  C. ENV_BRANCH
  D. GITHUB_BRANCH
  B. GITHUB_REF

  ---

  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.

• Question 35:

  You are reaching your organization's storage limit for GitHub artifacts and packages. What should you do to prevent the storage limit from being reached? (Choose two.)

  A. Delete artifacts from the repositories manually
  B. Disable branch protections in the repository.
  C. Use self-hosted runners for all workflow runs.
  D. Configure the artifact and log retention period.
  E. Configure the repo to use Git Large File Storage.
  A. Delete artifacts from the repositories manually
  D. Configure the artifact and log retention period.

  ---

  Deleting artifacts from repositories manually will free up storage space. Artifacts are typically stored for a limited time by default, but manual cleanup can help manage space. Configuring the artifact and log retention period allows you to control how long artifacts and logs are retained in your repository. By shortening the retention period, you can prevent unnecessary accumulation of data and manage storage more effectively.

• Question 36:

  Which workflow event is used to manually trigger a workflow run?

  A. create
  B. workflow_dispatch
  C. workflow_run
  D. status
  B. workflow_dispatch

  ---

  The workflow_dispatch event is used to manually trigger a workflow run in GitHub Actions. You can specify this event in the workflow file to allow users to manually trigger the workflow from the GitHub UI, often with optional input parameters.

• Question 37:

  Which workflow event is triggered when a pull request is updated with new commits?

  A. workflow_run
  B. push
  C. pull_request
  D. synchronize
  D. synchronize

  ---

  The synchronize event occurs whenever new commits are pushed to an existing pull request. This allows workflows to re-run checks or builds in response to updates made to the pull request branch.

• Question 38:

  Without the need to use additional infrastructure, what is the simplest and most maintainable method for configuring a workflow job to provide access to an empty PostgreSQL database?

  A. Use service containers with a Postgres database from Docker hub.
  B. Run the actions/postgres action in a parallel job.
  C. It is currently impossible to access the database with GitHub Actions.
  D. Dynamically provision and deprovision an environment.
  A. Use service containers with a Postgres database from Docker hub.

  ---

  GitHub Actions supports the use of service containers, which allows you to spin up a PostgreSQL database (or any other service) in a Docker container during your workflow. You can pull a PostgreSQL image from Docker Hub, and the container will automatically be available to your workflow job. This method requires no additional infrastructure and is easy to configure and maintain, as you simply define the container in the workflow file.

• Question 39:

  You need to trigger a workflow using the GitHub API for activity that happens outside of GitHub. Which workflow event do you use?

  A. check_suite
  B. workflow_run
  C. deployment
  D. repository_dispatch
  D. repository_dispatch

  ---

  Therepository_dispatchevent allows you to trigger a workflow in response to external activity. It is commonly used when you need to trigger a workflow from outside GitHub, such as from another system or service, by sending a request to the GitHub API. This event provides flexibility to integrate with various external systems and trigger workflows in a GitHub repository.

• Question 40:

  In which scenarios could the GITHUB_TOKEN be used? (Choose two.)

  A. to leverage a self-hosted runner
  B. to create a repository secret
  C. to publish to GitHub Packages
  D. to create issues in the repo
  E. to read from the file system on the runner
  F. to add a member to an organization
  C. to publish to GitHub Packages
  D. to create issues in the repo

  ---

  The GITHUB_TOKEN is automatically provided by GitHub in workflows and can be used to authenticate API requests to GitHub, including publishing packages to GitHub Packages. The GITHUB_TOKEN is also used to authenticate API requests for actions like creating issues, commenting, or interacting with pull requests within the same repository.