Free Online GitLab-Certified-Git-Associate Exam Mock for Best Practice

Question 1

Use the <insert_answer_here> keyword to define where a job deploys to.

Options :

A : "deployment"

B : "docker"

C : "environment"

D : "production" or "preview"

Answer: C

Question 2

'allow_failure' keyword set as 'true' in 'rules:' would:

Options :

A : Allow error level to be set in pipelines and expose related (error-level) logs.

B : Allow failures in scripts (such as Yaml Lints / shellchecks / etc.) to be automatically corrected by Gitlab' ML engine without failing the job.

C : Allow a job to fail without stopping the pipeline.

Answer: C

Question 3

Can you have pipeline activity (pipelines triggered and currently running) in project_A's Gitlab CI if you don't have any .yml file defined on the "master" or 'default' branch?

Options :

A : Yes

B : No

Answer: A

Question 4

In order to pass variables between the "before_script" and "script" parts of the same job you have to include the variables within the "variables" keyword section and not just simply have a line in the script section such as "VARIABLE_A='value'".

Options :

A : TRUE

B : FALSE

Answer: A

Question 5

You can set a job to fail after a specific amount of time, if it didn't finish running in the required timeframe.

Options :

A : False.

B :

True, but not for 'parallel' jobs - as the timeouts will split for the number of parallel jobs and possibly result in 'float' values, which are not supported here.

C : True, by the use of the 'timeout' keyword.

Answer: C

Free GitLab-Certified-Git-Associate Mock Exam – Practice Online Confidently

Buying Options: