|
Certkingdom's preparation material includes the most excellent features, prepared by the same dedicated experts who have come together to offer an integrated solution. We provide the most excellent and simple method to pass your certification exams on the first attempt "GUARANTEED"
Whether you want to improve your skills, expertise or career growth, with Certkingdom's training and certification resources help you achieve your goals. Our exams files feature hands-on tasks and real-world scenarios; in just a matter of days, you'll be more productive and embracing new technology standards. Our online resources and events enable you to focus on learning just what you want on your timeframe. You get access to every exams files and there continuously update our study materials; these exam updates are supplied free of charge to our valued customers. Get the best GH-200 exam Training; as you study from our exam-files "Best Materials Great Results"
GH-200 Exam + Online / Offline and Android Testing Engine & 4500+ other exams included
$50 - $25 (you save $25)
Buy Now
Exam Design
Audience Profile
This exam is designed for DevOps engineers, software developers, and IT professionals with intermediate-level experience in GitHub Actions, including workflow creation, automation, and CI/CD pipeline management.
Skills Measured
NOTE: The bullets that follow each of the skills measured are intended to illustrate how we are assessing that skill. Related topics may be covered in the exam.
NOTE: Most questions cover features that are general availability (GA). The exam may contain questions on Preview features if those features are commonly used.
Domain 1: Author and maintain workflows (40%)
Work with events that trigger workflows
Configure workflows to run for one or more events
Configure workflows to run for scheduled events
Configure workflows to run for manual events
Configure workflows to run for webhook events (e.g., check_run, check_suite, deployment, etc.)
Demonstrate a GitHub event to trigger a workflow based on a practical use case
Use the components of a workflow
Identify the correct syntax for workflow jobs (e.g., indentation and encapsulation of parts of the workflow)
Use job steps for actions and shell commands
Use conditional keywords for steps
Describe how actions, workflows, jobs, steps, runs, and the marketplace work together
Identify scenarios suited for using GitHub-hosted and self-hosted runners
Implement workflow commands as a run step to communicate with the runner
Demonstrate the use of dependent jobs
Use encrypted secrets and environment variables as part of a workflow
Use encrypted secrets to store sensitive information
Identify the available default environment variables during the construction of the workflow
Identify the location to set custom environment variables in a workflow
Identify when to use the GITHUB_TOKEN secret
Demonstrate how to use workflow commands to set environment variables
Create a workflow for a particular purpose
Add a script to a workflow
Demonstrate how to publish to GitHub Packages using a workflow
Demonstrate how to publish to GitHub Container Registry using a workflow
Use database and service containers in a GitHub Actions workflow
Use labels to route workflows to specific runners
Use CodeQL as a step in a workflow
Demonstrate how to publish a component as a GitHub release using GitHub Actions
Deploy a release to a cloud provider using a GitHub Actions workflow
Domain 2: Consume workflows (20%)
Interpret the effects of a workflow
Identify the event that triggered a workflow from its effects in a repository, issue, or pull request
Describe a workflow’s effects from reading its configuration file
Diagnose a failed workflow run (e.g., using a workflow run history and its logs, determine why a workflow run may have failed)
Identify ways to access the workflow logs from the user interface
Identify ways to access the workflow logs from GitHub’s REST API
Enable step debug logging in a workflow
Demonstrate how to use default environment variables in a workflow
Demonstrate the correct syntax for passing custom environment variables in a workflow step
Manage workflow runs
Configure caching of workflow dependencies
Identify steps to pass data between jobs in a workflow
Remove workflow artifacts from GitHub
Add a workflow status badge
Add environment protections
Define a matrix of different job configurations
Implement workflow approval gates
Locate a workflow, its logs, and artifacts
Describe where to locate a workflow in a repository
Explain the difference between disabling and deleting of workflows
Demonstrate how to download workflow artifacts from the user interface
Describe how to use an organization’s templated workflow
Domain 3: Author and maintain actions (25%)
Use available action types
Identify the type of action required for a given problem (e.g., JavaScript, Docker container, run step)
Demonstrate how to troubleshoot JavaScript actions
Demonstrate how to troubleshoot Docker container actions
Describe the components of an action
Identify the files and directory structure needed to create an action
Identify the metadata and syntax needed to create an action
Implement workflow commands within an action to communicate with the runner (Note: this includes exit codes)
Domain 4: Manage GitHub Actions in the enterprise (15%)
Distribute actions and workflows to the enterprise
Explain reuse templates for actions and workflows
Define an approach for managing and leveraging reusable components (e.g., repos for storage, naming conventions for files/folders, and plans for ongoing maintenance)
Define how to distribute actions for an enterprise
Define how to control access to actions within the enterprise
Configure organizational use policies for GitHub Actions
Manage runners for the enterprise
Describe the effects of configuring IP allow lists on GitHub-hosted and self-hosted runners
Describe how to select appropriate runners to support workloads (e.g., using a self-hosted versus GitHub-hosted runner, choosing supported operating systems)
Explain the difference between GitHub-hosted and self-hosted runners
Configure self-hosted runners for enterprise use (e.g., including proxies, labels, networking)
Demonstrate how to manage self-hosted runners using groups (e.g., managing access, moving runners into and between groups)
Demonstrate how to monitor, troubleshoot, and update self-hosted runners
Manage encrypted secrets in the enterprise
Identify the scope of encrypted secrets
Demonstrate how to access encrypted secrets within actions and workflows
Explain how to manage organization-level encrypted secrets
Explain how to manage repository-level encrypted secrets
Sample Question and Answers
QUESTION 1
As a developer, you want to run a workflow from the Actions tab in GitHub. Which YAML snippet
should you use to match the interface in this image?
A)
B)
C)
D)
A. Option A
B. Option B
C. Option C
D. Option D
Answer: C
Explanation:
The first image shows a workflow trigger with an option for the test suite, and the chosen YAML
configuration matches this interface. Specifically, the test suite input is defined with type: choice and
includes the option value: functional, which aligns with the visible UI elements in the first image.
QUESTION 2
How many jobs will result from the following matrix configuration?
A. 3 jobs
B. 4 jobs
C. 5 jobs
D. 6 jobs
Answer: D
Explanation:
The matrix configuration specifies two variables: color and animal. The color variable has 2 values
(green and pink), and the animal variable has 2 values (owl and magpie). This would result in 4
combinations (2 color values ã— 2 animal values). Additionally, the include section introduces two
more combinations (color: blue and animal: owl; color: pink and animal: magpie).
QUESTION 3
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.
Answer: A, B, D
Explanation:
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.
QUESTION 4
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.
Answer: A, C, D
Explanation:
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 5
Which statement is true about using default environment variables?
A. The environment variables can be read in workflows using the ENV: variable_name syntax.
B. The environment variables created should be prefixed with GITHUB_ to ensure they can be accessed in workflows
C. The environment variables can be set in the defaults: sections of the workflow
D. The GITHUB_WORKSPACE environment variable should be used to access files from within the runner.
Answer: D
Explanation:
GITHUB_WORKSPACE is a default environment variable in GitHub Actions that points to the directory
on the runner where your repository is checked out. This variable allows you to access files within
your repository during the workflow.