GitHub GITHUB-ACTIONS Online Practice Questions and Exam Preparation

GitHub GITHUB-ACTIONS Online Questions & Answers

• Question 61:

  Which scopes are available to define custom environment variables within a workflow file? (Choose three.)

  A. the entire workflow, by using env at the top level of the workflow file
  B. all jobs being run on a single Actions runner, by using runner.env at the top of the workflow file
  C. the entire stage, by using env at the top of the defined build stage
  D. within the run attribute of a job step
  E. the contents of a job within a workflow, by using jobs..env
  F. a specific step within a job, by using jobs..steps[*].env
  A. the entire workflow, by using env at the top level of the workflow file
  D. within the run attribute of a job step
  F. a specific step within a job, by using jobs..steps[*].env

  ---

  You can define environment variables for the entire workflow by using the env key at the top level of the workflow file. These environment variables will be available to all jobs and steps within the workflow.

  Environment variables can also be set within the run attribute of a job step, and these variables will be scoped only to that specific step.

  You can set environment variables for specific steps within a job by using jobs..steps[*].env, which allows you to define variables that will only be available to that step.

• Question 62:

  As a developer, you need to create a custom action written in Python. Which action type should you choose?

  A. JavaScript action
  B. composite run step
  C. Python action
  D. Docker container action
  D. Docker container action

  ---

  ADocker container actionis ideal for custom actions that require specific environments or dependencies, such as Python. By creating a Docker container, you can define the environment with the necessary Python version and dependencies, and your Python code can run inside that container.

• Question 63:

  As a developer, which workflow steps should you perform to publish an image to the GitHub Container Registry? (Choose three.)

  A. Use the actions/setup-docker action
  B. Authenticate to the GitHub Container Registry.
  C. Build the container image.
  D. Push the image to the GitHub Container Registry
  E. Pull the image from the GitHub Container Registry.
  A. Use the actions/setup-docker action
  B. Authenticate to the GitHub Container Registry.
  D. Push the image to the GitHub Container Registry

• Question 64:

  What are the advantages of using a matrix strategy in a job definition? (Choose two.)

  A. It can test code in multiple versions of a programming language.
  B. It can decrease the costs for running multiple combinations of programming language/operating systems.
  C. It can run up to 512 jobs per workflow run.
  D. It can test code in multiple operating systems.
  A. It can test code in multiple versions of a programming language.
  D. It can test code in multiple operating systems.

  ---

  A matrix strategy allows you to define different versions of a programming language (or any other environment setting) and run tests on each version simultaneously. This is particularly useful for testing code compatibility across different versions of a language. A matrix strategy can also be used to test code on multiple operating systems (e.g., Windows, macOS, Linux) by defining these operating systems as matrix variables. This enables cross-platform testing within the same workflow.

• Question 65:

  Which statement is true regarding permissions assigned to the GITHUB_TOKEN?

  A. It always has full repository and organization access.
  B. It inherits permissions based on the workflow's author.
  C. It has default read/write access but can be restricted using permissions:.
  D. It cannot be modified by users.
  C. It has default read/write access but can be restricted using permissions:.

  ---

  By default, the GITHUB_TOKEN has read/write permissions to the repository. However, these can be adjusted using the permissions: key in the workflow YAML file to adhere to the principle of least privilege.

• Question 66:

  When using a Docker container action, what is the purpose of the post keyword in the action.yml file?

  A. Defines a fallback Docker image.
  B. Specifies cleanup steps that run after the main script.
  C. Declares post-deployment configuration options.
  D. Defines entrypoint arguments.
  B. Specifies cleanup steps that run after the main script.

  ---

  The post key defines a script that executes after the main entrypoint script in a Docker container action. It's commonly used for cleanup operations, log collection, or resource deallocation once the main process completes.

• Question 67:

  You need to manually re-run a failed job from a completed workflow run. Where can this action be performed?

  A. From the Pull Requests tab
  B. From the Actions tab, selecting the failed workflow run
  C. From the Repository Settings page
  D. From the GitHub API only
  B. From the Actions tab, selecting the failed workflow run

  ---

  Developers can manually re-run individual jobs or entire workflows directly from the Actions tab by selecting a specific run. GitHub provides buttons such as "Re-run all jobs" and "Re-run failed jobs" for convenience.

• Question 68:

  You installed specific software on a Linux self-hosted runner. You have users with workflows that need to be able to select the runner based on the identified custom software. Which steps should you perform to prepare the runner and your users to run these workflows? (Choose two.)

  A. Create the group custom-software-on-linux and move the runner into the group.
  B. Inform users to identify the runner based on the group.
  C. Add the label custom-software to the runner.
  D. Configure the webhook and network to enable GitHub to trigger workflow.
  E. Add the label linux to the runner.
  B. Inform users to identify the runner based on the group.
  C. Add the label custom-software to the runner.

  ---

  Once the runner is properly configured and labeled, users should be informed to select the specific runner by identifying the label or group name when defining the runner in their workflows.

  Adding a custom label (likecustom-software) to the runner makes it easier for users to select the runner in their workflows by using theruns-onkey, which allows them to choose this specific runner based on its label.

• Question 69:

  Which of the following statements are true regarding the use of GitHub Actions on a GitHub Enterprise Server instance? (Choose three.)

  A. Use of GitHub Actions on GitHub Enterprise Server requires a persistent internet connection
  B. Actions created by GitHub are automatically available and cannot be disabled
  C. Most GitHub authored actions are automatically bundled for use on GitHub Enterprise Server
  D. Third party actions can be used on GitHub Enterprise Server by configuring GitHub Connect
  E. Actions must be defined in the .github repository
  F. Third party actions can be manually synchronized for use on GitHub Enterprise Server
  A. Use of GitHub Actions on GitHub Enterprise Server requires a persistent internet connection
  D. Third party actions can be used on GitHub Enterprise Server by configuring GitHub Connect
  F. Third party actions can be manually synchronized for use on GitHub Enterprise Server

  ---

  GitHub Actions on GitHub Enterprise Server often requires an internet connection, especially for accessing actions from the GitHub Marketplace or third-party actions unless they are manually synced to the server.

  To use third-party actions on GitHub Enterprise Server, GitHub Connect can be used to establish a connection between the server and GitHub.com, enabling access to third-party actions.

  Third-party actions can also be manually synchronized to the GitHub Enterprise Server, making them available for use in workflows.

• Question 70:

  GitHub-hosted runners support which capabilities? (Choose two.)

  A. automatic patching of both the runner and the underlying OS
  B. automatic file-system caching between workflow runs
  C. support for Linux, Windows, and mac
  D. support for a variety of Linux variations including CentOS, Fedora, and Debian
  E. requiring a payment mechanism (e.g., credit card) to use for private repositories
  C. support for Linux, Windows, and mac
  D. support for a variety of Linux variations including CentOS, Fedora, and Debian

  ---

  GitHub-hosted runners automatically handle patching, meaning they will be kept up to date with the latest security updates and software patches for both the runner environment and the underlying operating system. GitHub-hosted runners support Linux, Windows, and macOS, giving you flexibility to run workflows on different operating systems without needing to manage your own self-hosted runners.