A pipeline job fails. The developer opens the job log and sees the following near the end: 'Error: No such file or directory - /builds/project/scripts/deploy.sh'. The script file exists in the repository. What is the most likely cause?

The script file is not executable, so the runner cannot run it.

The runner does not have permission to read the repository files.

The job is running in a different directory than expected, so the relative path is incorrect.

The script file contains syntax errors that prevent it from being parsed.

A job fails due to a transient network error. The developer wants to re-run the job without making any code changes. What should the developer do?

Push an empty commit to trigger a new pipeline.

Edit the job configuration and run the pipeline again.

Retry the job from the pipeline interface.

Cancel the job and create a new pipeline.

A developer is monitoring a pipeline and sees that a job has been 'running' for over an hour, but the job's log has not been updated in the last 30 minutes. The job is a long-running script that normally takes 10 minutes. What should the developer do?

Check the runner's status to see if it is offline.

Wait for the job to finish, as it may be processing a large amount of data.

Cancel the job and investigate the script for a possible hang.

Retry the job to see if it completes faster.

A developer pushes a commit to a feature branch. The pipeline starts, but the 'test' job remains in a 'pending' state for several minutes. The developer checks the job details and sees the job is assigned to a runner. What is the most likely reason the job is still pending?

The pipeline is paused and will not run until manually resumed.

The runner is offline and cannot accept any jobs.

The runner is busy executing other jobs and cannot pick up this job yet.

The job has failed and is waiting for a manual retry.

GitLabCertified Fundamentals Associate

Domain 4Objective 3

Run and Monitor Pipeline Jobs GITLAB-CERTIFIED-GIT-ASSOCIATE Practice Questions (Page 4)

Part of the Basic CI/CD Pipelines domain, which makes up ~16% of our current practice bank.

23questions here

5free pages

5concepts

Questions 16–20

16application · medium
A pipeline job fails. The developer opens the job log and sees the following near the end: 'Error: No such file or directory - /builds/project/scripts/deploy.sh'. The script file exists in the repository. What is the most likely cause?
Select an answer first
17application · easy
A job fails due to a transient network error. The developer wants to re-run the job without making any code changes. What should the developer do?
Select an answer first
18foundation · easy
A job failed due to a temporary infrastructure issue. Which action can you take from the pipeline interface to run the job again without making any code changes?
Select an answer first
19expert · hard
A developer is monitoring a pipeline and sees that a job has been 'running' for over an hour, but the job's log has not been updated in the last 30 minutes. The job is a long-running script that normally takes 10 minutes. What should the developer do?
Select an answer first
20application · medium
A developer pushes a commit to a feature branch. The pipeline starts, but the 'test' job remains in a 'pending' state for several minutes. The developer checks the job details and sees the job is assigned to a runner. What is the most likely reason the job is still pending?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GITLAB-CERTIFIED-GIT-ASSOCIATE

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by GitLab. “GITLAB-CERTIFIED-GIT-ASSOCIATE” is a trademark of its owner, used for identification only.