Cisco®
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
Scrum
All Vendors
  2. Home
  3. Exams
  4. GitHub
  5. GitHub-Actions

Free GitHub-Actions Exam Braindumps (page: 6)

Page 5 of 19
PDF with 72 Questions

You are a developer, and your container jobs are failing on a self-hosted runner.
Which requirements must you check to ensure that the self-hosted runner is properly configured? (Choose two.)

  1. The self-hosted runner is running a Linux operating system.
  2. The self-hosted runner is running a Windows operating system.
  3. Docker is installed on the self-hosted runner.
  4. Kubernetes is installed on the self-hosted runner.
  5. The service status of Kubernetes is "active".

Answer(s): A,C

Explanation:

While Docker can run on various operating systems, Linux is often the most common and preferred OS for containerized workloads. Docker works well on Linux and is a widely-used platform for running containers.
For container jobs to run on a self-hosted runner, Docker must be installed and properly configured on the runner. Docker is required to build and run containerized workloads in a GitHub Actions workflow.



Which choices represent best practices for publishing actions so that they can be consumed reliably? (Choose two.)

  1. repo name
  2. tag
  3. commit SHA
  4. organization name
  5. default branch

Answer(s): B,C

Explanation:

Using a tag is a best practice because tags are immutable and represent a fixed version of your action. By referencing tags, consumers of your action can be assured they are using a stable and specific version of the action, which helps in avoiding issues with breaking changes. The commit SHA is another reliable way to specify a particular version of an action. By referencing a specific commit SHA, consumers can ensure they are using exactly the code that was written at that moment, avoiding the potential for changes in the future.



You need to create new workflows to deploy to an unfamiliar cloud provider.
What is the fastest and safest way to begin?

  1. Create a custom action to wrap the cloud provider's CLI.
  2. Search GitHub Marketplace for verified actions published by the cloud provider.
  3. Use the actions/jenkins-plugin action to utilize an existing Jenkins plugin for the cloud provider.
  4. Search GitHub Marketplace for actions created by GitHub.
  5. Download the CLI for the cloud provider and review the associated documentation.

Answer(s): B

Explanation:

Searching the GitHub Marketplace for verified actions published by the cloud provider is the quickest and safest approach. Many cloud providers offer verified GitHub Actions that are maintained and optimized to interact with their services. These actions typically come with the correct configurations and best practices, allowing you to get started quickly without reinventing the wheel.



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

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

Answer(s): C,D

Explanation:

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.






Post your Comments and Discuss GitHub GitHub-Actions exam with other Community members:

Exam Discussions & Posts