CI CD Interview Questions and Answers
Question - 71 : - Could you explain the process of deployment?
Answer - 71 : -
The deployment process flow consists of 5 steps:
- Planning
- Development
- Testing
- Deploying
- Monitoring
Question - 72 : - What is the difference between build and deploy?
Answer - 72 : -
Build and deploy are testing terms with important meanings in the IT field. “Build” means consolidating and combining a set of executable code for testing. “Deploy” means injecting that set of executable code into a particular software environment to test it.
Question - 73 : - How would you define the GitLab workflow?
Answer - 73 : -
The Flow process incorporates a pre-prod branch to fix bugs before merging changes back to main (typically from dev) before going to production. Each team can have as many pre-prod branches as needed — for example, from main to test, from test to acceptance, and from acceptance to production.
Question - 74 : - Can you elaborate on the release flow?
Answer - 74 : -
Flow is a trunk-based development approach in which the master branch is deployed and developed. Branches are created off the master branch when there are special needs, but the branches do not serve as deployment targets. Here a pull request merges a branch back into the master branch.
Question - 75 : - What is the most important deployment step?
Answer - 75 : -
Systematic communication is an important element of deployment management. Without communication, many problems can arise, including scheduling conflicts and misunderstandings about the scope of a deployment. Post-deployment check-ins with decision-makers can help your team arrive at timely and accurate decisions, allowing you to avoid many common deployment issues.
Question - 76 : - What are artifacts in GitLab CI?
Answer - 76 : -
In GitLab 12.4, files and directories from internal and private projects can be previewed when access control is enabled using GitLab Pages. Jobs can output an archive of all the files and directories that are generated as part of the job run in a .zip file. This output is known as a job artifact, which can be downloaded using the GitLab UI or API.
Question - 77 : - Could you explain what are deployment artifacts?
Answer - 77 : -
A deployment artifact, also known as an “archive file,” is the file generated by a build that contains all the information required to deploy the application to runtime. This type of file is created in the design phase and then handed off to the run-time environment.
Question - 78 : - Where are artifacts stored in GitLab CI?
Answer - 78 : -
The artifacts are stored in /home/git/gitlab/shared/artifacts by default. In order to keep them backed up regularly, you should save the file and restart GitLab.
Question - 79 : - What is cache dependency?
Answer - 79 : -
Cache dependencies enable the system to expire cached items when related objects are modified automatically. The system uses dummy cache keys, or cache items with no data that represent one or more other objects, to create dependencies between cached data and other objects.
Question - 80 : - What do you know about the dependency proxy?
Answer - 80 : -
GitLab provides a local cache called the Dependency Proxy for frequently-accessed upstream images. The Dependency Proxy can act as a pull-through cache in the case of CI/CD by receiving a request from your build server and returning the requested image from the registry.