GH-200 Practice Questions

A.  

running more than the three concurrent workflows supported by GitHub-hosted runners

B.  

exceeding 50,000 monthly minutes of build time

C.  

using Docker containers as part of the workflow

D.  

using specialized hardware configurations required for workflows

E.  

performing builds on macOS

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.

A.  

repo name

B.  

tag

C.  

commit SHA

D.  

organization name

E.  

default branch

A.  

echo :debug::message=action successfully debugged "

B.  

echo " debug-action successfully debugged "

C.  

echo " ::debug::action successfully debugged "

D.  

echo " :debug:action successfully debugged: "

A.  

runs:

using: " composite "

steps:

- run: $GITHUB_ACTION_PATH/script.sh

directory: ${{ inputs.dir }}

shell: bash

B.  

runs:

using: " composite "

directory: ${{ inputs.dir }}

steps:

- run: $GITHUB_ACTION_PATH/script.sh

shell: bash

C.  

runs:

using: " composite "

working-directory: ${{ inputs.dir }}

steps:

- run: $GITHUB_ACTION_PATH/script.sh

shell: bash

D.  

runs:

using: " composite "

steps:

- run: $GITHUB_ACTION_PATH/script.sh

working-directory: ${{ inputs.dir }}

shell: bash

A.  

runs-on: [self-hosted, linux-xlarge]

B.  

runs-on: - self-hosted - ubuntu-latest

C.  

runs-on: [self-hosted, runner1]

D.  

runs-on: self-hosted

A.  

with: python

B.  

shell: bash

C.  

working-directory: .github/python

D.  

shell: python

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.

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. < job_id > .env

F.  

a specific step within a job, by using jobs. < job_id > .steps[*].env

A.  

jobs:

deploy:

if: github.ref_name == ' feature-branch '

runs-on: ubuntu-latest

steps:

- uses: actions/checkout@v3

B.  

jobs:

deploy:

if: github.ref.name == ' feature-branch '

runs-on: ubuntu-latest

steps:

- uses: actions/checkout@v3

C.  

jobs:

deploy:

if: github.branch_name == ' feature-branch '

runs-on: ubuntu-latest

steps:

- uses: actions/checkout@v3

D.  

jobs:

deploy:

if: github.branch.name == ' feature-branch '

runs-on: ubuntu-latest

steps:

- uses: actions/checkout@v3