GitLab-Certified-CI-CD-Associate Exam: Absolutely Free Online Practice

Question 1
- A team wants to configure GitLab Group Runners for multiple projects but needs to ensure that only specific types of jobs run on them while other jobs should execute on shared GitLab-hosted runners. What is the best way to achieve this?
  A : Configure job-level tags in .gitlab-ci.yml to match the group runner’s tags and define specific jobs to use it.
  
  B : Assign runner tags at the instance level and let projects override them in .gitlab-ci.yml.
  
  C : Configure the group runner as locked so that only default pipeline jobs can use it.
  
  D : Disable shared runners at the group level to force all jobs to run on the group runner.
  
  Answer: A
Question 2
- You want to integrate Coverage-guided Fuzz Testing into your GitLab CI/CD pipeline to identify security vulnerabilities. What steps should you take to properly configure Coverage-guided Fuzz Testing?
  A : Add a fuzz_test job in the .gitlab-ci.yml file and include security/fuzz-testing template.
  
  B : Use the before_script section to run fuzz tests before any other job in the pipeline.
  
  C : Install a third-party fuzz testing tool on your CI runners and configure it to run during the pipeline.
  
  D : Write a custom script to perform fuzz testing and integrate it into the build stage of the pipeline.
  
  Answer: A
Question 3
- You want to integrate License Scanning into your GitLab CI/CD pipeline to automatically check for compliance with your organization’s licensing policies. What steps should you take to properly configure License Scanning?
  A : Use the license-check job before deployment to ensure compliance with licensing policies.
  
  B : Configure a webhook to trigger a license scan after every commit.
  
  C : Add a license_scan job in the .gitlab-ci.yml file and include security/license-scanning template.
  
  D : Install a third-party license scanning tool on your CI runners and configure it to run during the pipeline.
  
  Answer: C
Question 4
- You need to optimize a GitLab CI/CD pipeline to include caching to speed up subsequent pipeline runs, and also ensure that artifacts from the build stage are available to the deployment stage. Which two configurations should you use in the .gitlab-ci.yml file?
  A : Define artifacts in the build stage and specify the paths and when to be used.
  
  B : Use the dependencies keyword to define job dependencies.
  
  C : Set up a before_script section to manually handle caching and artifact creation.
  
  D : Use the cache keyword to define paths to be cached between jobs.
  
  E : Combine all stages into a single job to avoid the need for caching and artifact sharing.
  
  Answer: A,D
Question 5
- Your team is working on a GitLab project that handles sensitive user data. To prevent accidental exposure of secrets like API keys and passwords, you need to enable Secret Detection in your CI/CD pipeline. Which of the following steps is NOT required to set up Secret Detection in GitLab?
  A : Review and act on the findings from the Secret Detection reports.
  
  B : Add the Secret Detection template to your .gitlab-ci.yml file.
  
  C : Configure a secret scanning tool outside of GitLab to run alongside the pipeline.
  
  D : Ensure that GitLab Runners have access to the necessary Docker images for Secret Detection.
  
  Answer: C

Free Gitlab GitLab-Certified-CI-CD-Associate Exam Questions

Absolute Free GitLab-Certified-CI-CD-Associate Exam Practice for Comprehensive Preparation