Free Preparation Discussions
MENU
GitHub-Actions Exam Questions
- Topic 1: Automate development tasks by using GitHub Actions: This section of the exam measures the skills of DevOps Engineers and covers the fundamentals of GitHub Actions. It focuses on understanding action types, planning automation workflows, and creating container actions. One skill to be measured is creating workflows triggered by repository events.
- Topic 2: Build continuous integration (CI) workflows by using GitHub Actions: This section of the exam measures the skills of Software Engineers and covers essential features for building robust CI workflows. It emphasizes building and testing projects, debugging failed tests, and customizing workflows. A skill to be measured is troubleshooting CI pipelines using GitHub Actions logs.
- Topic 3: Leverage GitHub Actions to publish to GitHub Packages: This section of the exam measures the skills of Software Engineers and Package Managers and covers the use of GitHub Actions for publishing to GitHub Packages. It focuses on setting up CI workflows for package publishing and authentication. One skill to be measured is configuring workflows to publish to package registries.
- Topic 4: Create and publish custom GitHub actions: This section of the exam measures the skills of Software Engineers and covers the creation and publication of custom GitHub actions.
- Topic 5: Build and deploy applications to Azure by using GitHub Actions: This section of the exam covers deploying applications to Azure using GitHub Actions. It focuses on continuous delivery workflows, environment protections, and Azure resource management.
- Topic 6: Manage GitHub Actions in the enterprise: This section of the exam measures the skills of GitHub Managers and covers managing GitHub Actions at the enterprise level. It emphasizes tools for action and workflow management, runner configurations, and encrypted secrets usage. A skill to be measured is customizing self-hosted runners for enterprise use cases.
Free GitHub GitHub-Actions Exam Actual Questions
Note: Premium Questions for GitHub-Actions were last updated On Jan. 21, 2025 (see below)
Which scopes are available to define custom environment variables within a workflow file? (Choose three.)
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.<job_id>.steps[*].env, which allows you to define variables that will only be available to that step.
As a developer, how can you identify a Docker container action on GitHub?
In a Docker container action, the action.yml file includes the runs.using field, which is set to docker to specify that the action runs inside a Docker container. This is the key indicator that the action is a Docker container action.
Which files are required for a Docker container action in addition to the source code? (Choose two.)
Dockerfile: The Dockerfile is 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: The action.yml file 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 under runs.using).
As a DevOps engineer developing a JavaScript action, you need to include annotations to pass warning messages to workflow runners. Which code snippet can you use to implement an annotation in your Actions?
As a DevOps engineer developing a JavaScript action, you need to include annotations to pass warning messages to workflow runners. Which code snippet can you use to implement an annotation in your Actions?
The core.warning() function from the @actions/core package is used to create a warning message in the workflow logs. This is an annotation type that informs users about issues that don't require failing the build but still need attention.
As a developer, your self-hosted runner sometimes looses connection while running jobs. How should you troubleshoot the issue affecting your self-hosted runner?
When troubleshooting a self-hosted runner, you can access the _diag folder located in the self-hosted runner's installation directory. This folder contains diagnostic logs that can help you identify the root cause of issues, such as connection problems.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Isreal
4 days agoEladia
6 days agoLinwood
21 days agoCarry
22 days ago