What is the default stage for scanning jobs in GitLab?

What is the default stage for scanning jobs in GitLab?

• A. Build
• B. Test
• C. Deploy
• D. Cleanup

Answer: (B)

In GitLab CI/CD, the default stage for scanning jobs is the Test stage. This means that when you create a new CI/CD pipeline, any jobs set to run scans, such as security scans or linting jobs, are automatically assigned to the Test stage unless specified otherwise in the configuration. The Test stage is commonly used to verify the integrity and functionality of the code, which aligns perfectly with the purpose of scanning jobs that assess code quality, security vulnerabilities, and compliance. While other stages like Build, Deploy, and Cleanup serve their own specific purposes, the Test stage is particularly geared towards validating changes before they are either built or deployed. Consequently, jobs meant for inspection or verification naturally fall under this category, emphasizing its role in the software development lifecycle.

In GitLab CI/CD, the default stage for scanning jobs is the Test stage. This means that when you create a new CI/CD pipeline, any jobs set to run scans, such as security scans or linting jobs, are automatically assigned to the Test stage unless specified otherwise in the configuration. The Test stage is commonly used to verify the integrity and functionality of the code, which aligns perfectly with the purpose of scanning jobs that assess code quality, security vulnerabilities, and compliance.

While other stages like Build, Deploy, and Cleanup serve their own specific purposes, the Test stage is particularly geared towards validating changes before they are either built or deployed. Consequently, jobs meant for inspection or verification naturally fall under this category, emphasizing its role in the software development lifecycle.