CI CD Interview Questions and Answers
Question - 81 : - How would you explain Docker layer caching?
Answer - 81 : -
Docker Layer Caching (DLC) is a useful feature to enable during continuous integration and continuous delivery (CI/CD) jobs in order to create reusable images that do not change each time they are run. Docker Layer Caching (DLC) is a feature that helps reduce the time it takes to run your containers by keeping track of changes to images so that they do not have to be rebuilt every time you upgrade your container.
Question - 82 : - How does GitLab caching work?
Answer - 82 : -
A cache is a set of files that a job can download before the execution, and upload after completion. The default location of the cache is the home directory of the GitLab Runner. If the distributed cache is configured, S3 works as storage. After execution, it will upload the cache back to the S3 bucket (push).
Question - 83 : - What is a GitLab registry?
Answer - 83 : -
GitLab Container Registry is a secure and private registry for Docker images. Built on open-source software and tightly integrated with GitLab, Container Registry gives every user—from solo developers to large enterprise—a single, secure interface to manage their projects, as well as all their containerized applications and services.
Question - 84 : - What are benefits of CI-CD ?
Answer - 84 : -
- Smaller code changes are simpler (more atomic) and have fewer unintended consequences.
- Fault isolation is simpler and quicker.
- Mean time to resolution (MTTR) is shorter because of the smaller code changes and quicker fault isolation.
- Testability improves due to smaller, specific changes. These smaller changes allow more accurate positive and negative tests.
- Elapsed time to detect and correct production escapes is shorter with a faster rate of release.
- The backlog of non-critical defects is lower because defects are often fixed before other feature pressures arise.
- The product improves rapidly through fast feature introduction and fast turn-around on feature changes.
- Upgrades introduce smaller units of change and are less disruptive.
- CI-CD product feature velocity is high. The high velocity improves the time spent investigating and patching defects.
- Feature toggles and blue-green deploys enable seamless, targeted introduction of new production features.
- You can introduce critical changes during non-critical (regional) hours. This non-critical hour change introduction limits the potential impact of a deployment problem.
Question - 85 : - What is CI CD process?
Answer - 85 : -
CI/CD is a method to frequently deliver apps to customers by introducing automation into the stages of app development. The main concepts attributed to CI/CD are continuous integration, continuous delivery, and continuous deployment.
Question - 86 : - How do I prepare for CI CD?
Answer - 86 : -
Definition. CI and CD stand for continuous integration and continuous delivery/continuous deployment. In very simple terms, CI is a modern software development practice in which incremental code changes are made frequently and reliably.