GitHub GITHUB-ACTIONS Online Practice Questions and Exam Preparation

GitHub GITHUB-ACTIONS Online Questions & Answers

• Question 21:

  You are a developer working on developing reusable workflows for your organization. What keyword should be included as part of the reusable workflow event triggers?

  A. check_run
  B. workflow_run
  C. workflow_call
  D. pull_request
  C. workflow_call

  ---

  The workflow_call event is used to trigger a reusable workflow from another workflow. This allows you to create workflows that can be reused in multiple places within your organization, enabling better modularity and reducing duplication.

• Question 22:

  As a developer, you need to integrate a GitHub Actions workflow with a third-party code quality provider that uses the Checks API. How should you trigger a follow-up workflow?

  A. Add the workflow_run webhook event as a trigger for the workflow for the code quality integration name
  B. Add the check_run webhook event as a trigger for the workflow when the code quality integration is completed
  C. Add the pull_request webhook event as a trigger for the workflow when the code quality integration is synchronized
  D. Add the deployment webhook event as a trigger for the workflow when the code quality integration is completed
  B. Add the check_run webhook event as a trigger for the workflow when the code quality integration is completed

  ---

  Thecheck_runevent is triggered when a check (such as a code quality check) completes, including when the status of a check changes. By adding this event as a trigger, you can initiate a follow-up workflow when the code quality integration finishes its checks.

• Question 23:

  What will the output be for the following event trigger block in a workflow?

  

  A. It throws a workflow syntax error, pointing to the types definition in issue_comment event.
  B. It throws a workflow syntax error, pointing to the types definition in issues event.
  C. It runs the workflow when an issue is edited or when an issue comment created.
  D. It runs the workflow when an issue or issue comment in the workflow's repository is created or modified.
  E. It runs the workflow when an issue is created or edited, or when an issue or pull request comment is created.
  C. It runs the workflow when an issue is edited or when an issue comment created.

  ---

  The provided event trigger block specifies two types of events:

  For issues: the workflow triggers on opened or edited issues.

  For issue_comment: the workflow triggers when an issue comment is created.

  This configuration ensures the workflow will run when either an issue is opened or edited, or an issue comment is created.

• Question 24:

  How many jobs will result from the following matrix configuration?

  

  A. 3 jobs
  B. 4 jobs
  C. 5 jobs
  D. 6 jobs
  D. 6 jobs

  ---

  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 and animal: owl; color: pink and animal: magpie).

• Question 25:

  Which default GitHub environment variable indicates the name of the person or app that initiated a workflow?

  A. ENV_ACTOR
  B. GITHUB_WORKFLOW_ACTOR
  C. GITHUB_ACTOR
  D. GITHUB_USER
  C. GITHUB_ACTOR

  ---

  The GITHUB_ACTOR environment variable indicates the name of the person or app that initiated the workflow. This variable is automatically provided by GitHub in the workflow and can be used to identify the user or application triggering the workflow.

• Question 26:

  As a DevOps engineer, you are trying to leverage an organization secret in a repo. The value received in the workflow is not the same as that set in the secret. What is the most likely reason for the difference?

  A. There is a different value specified at the rego level.
  B. There is a different value specified at the workflow level.
  C. The Codespace secret doesn't match the expected value.
  D. The Encrypt Secret setting was not configured for the secret.
  E. There is a different value specified at the enterprise level.
  A. There is a different value specified at the rego level.

  ---

  GitHub secrets are defined at different levels: organization, repository, and sometimes at the workflow level. If a secret is defined at both the organization level and the repository level, the repository-level secret will take precedence. So, if the value of the secret differs between these levels, the workflow will use the value from the repository level instead of the organization level.

• Question 27:

  Which default GitHub environment variable indicates the owner and repository name?

  A. REPOSITORY NAME
  B. GITHUB REPOSITORY
  C. ENV REPOSITORY
  D. GITHUB WORKFLOW REPO
  A. REPOSITORY NAME

  ---

  The GITHUB_REPOSITORY environment variable contains the owner and repository name in the format owner/repository. It is automatically provided by GitHub Actions and can be used to reference the repository in workflows.

• Question 28:

  What is the minimal syntax for declaring an output named foo for an action?

  

  A. outputs: foo: description: Some value
  B. outputs: -key: foo description: Some value
  C. outputs: foo: value: Some value
  D. outputs: -key: foo value: Some value
  C. outputs: foo: value: Some value

  ---

  The correct minimal syntax for declaring an output in GitHub Actions is by using thefookey underoutputs, and associating it with avalue(in this case,Some value). This is the simplest form to define an output in a workflow or action.

• Question 29:

  What does the jobs..timeout-minutes keyword control?

  A. The total runtime of all jobs combined.
  B. The time GitHub waits before automatically cancelling the job.
  C. The duration for which a workflow can stay queued.
  D. The time limit for each individual step within a job.
  B. The time GitHub waits before automatically cancelling the job.

  ---

  The timeout-minutes keyword defines how long a specific job can run before GitHub automatically cancels it. This prevents runaway workflows and helps manage CI/CD resource usage effectively.

• Question 30:

  When creating and managing custom actions in an enterprise setting, which of the following is considered a best practice?

  A. creating a separate repository for each action so that the version can be managed independently
  B. creating a separate branch in application repositories that only contains the actions
  C. creating a single repository for all custom actions so that the versions for each action are all the same
  D. including custom actions that other teams need to reference in the same repository as application code
  A. creating a separate repository for each action so that the version can be managed independently

  ---

  Creating a separate repository for each custom action allows you to manage the versioning independently for each action. This approach provides flexibility, as each action can be updated, tested, and versioned separately, avoiding potential conflicts or dependencies between different actions.