CI CD Pipeline Interview Questions PDF By ScholarHat

CI CD Pipeline Interview Questions: From
Basics to Advanced
CI-CD Pipeline Interview Questions
CI/CD Pipeline Interview Questions and Answers are crucial for anyone looking to excel in
DevOps and software development roles. These questions delve into key concepts like
automation, continuous integration, continuous delivery, and the tools used to implement
these processes. Understanding CI/CD pipelines is essential for modern software
deployment
and maintenance.
Top 50+ CI/CD Pipeline Interview Questions and
Answers
Q 1. What is CI/CD?
This Interview Tutorial will help you prepare for interviews by covering everything from
foundational principles to advanced techniques in CI/CD practices.

Some of the most commonly used CI/CD tools include:
Jenkins
GitLab CI
CircleCI
Travis CI
Azure DevOps
Bamboo
GitHub Actions
The key benefits of using CI/CD pipelines are:
Automation: Reduces human errors and manual interventions.
Faster Release Cycle: Accelerates the delivery of new features and bug fixes.
Consistent Quality: Ensures code is tested and ready for production at all times.
A CI/CD pipeline automates the steps of code integration, building, testing, and deployment to
ensure continuous delivery with minimal manual intervention.
CI/CD stands for Continuous Integration and Continuous Deployment/Delivery:
Continuous Integration (CI): Automates the integration of code changes into a shared
repository.
Continuous Delivery (CD): Automates the deployment process, ensuring code is always
deployable.
Continuous Integration (CI) focuses on integrating code changes into a shared repository
frequently, while Continuous Delivery (CD) ensures that code is always in a deployable
state, ready for automatic deployment to production.
Q 3. What is a CI/CD pipeline?
Q 5. What are the common CI/CD tools?
Q 4. What are the benefits of CI/CD pipelines?
Q 2. What is the difference between Continuous Integration (CI)
and Continuous Delivery (CD)?

Q 10. What is a build artifact in CI/CD?
A build artifact is a file or set of files produced by the build process in the pipeline. This can
include compiled code, libraries, or any other necessary files that will be deployed to staging
or production environments.
Q 6. What is the purpose of Jenkins in CI/CD?
Jenkins is an open-source automation server commonly used in CI/CD pipelines. It helps
automate tasks such as code integration, testing, and deployment by running jobs and
workflows, thus improving software delivery processes.
Q 7. What is the role of version control in CI/CD?
Version control systems, such as Git, manage and track changes to the codebase. In a CI/CD
pipeline, version control ensures that code changes are consistently integrated and deployed
from a central repository, allowing teams to collaborate more effectively.
Q 9. How do you implement testing in a CI/CD pipeline?
Automated tests are integrated into the CI/CD pipeline to verify code quality and functionality.
These tests can include unit tests, integration tests, and end-to-end tests. The pipeline ensures
that the code passes all tests before moving to the next stage of deployment.
Q 11. What are the different types of CI/CD environments?
Q 8. What is the difference between Continuous Delivery and
Continuous Deployment?
Continuous Delivery ensures that code is always in a deployable state, but it requires manual
approval before deployment to production. Continuous Deployment, on the other hand,
automates the entire process, including deployment to production, without manual
intervention.
Environment Type Description

Development
Environment
Staging Environment
Production Environment
Where developers integrate and test their code frequently.
Simulates production, used for final testing before deployment.
The live environment where the final code is deployed for end
users.
Configuration management tools like Ansible, Puppet, and Chef help automate the
configuration of infrastructure and environments. These tools ensure that environments are
An artifact repository is a storage system for storing build artifacts produced during the CI/CD
pipeline process. It allows teams to manage, share, and access build artifacts such as binaries
and libraries efficiently. Popular repositories include JFrog Artifactory and Nexus Repository.
Docker allows developers to package applications into containers that can be easily deployed
and tested in any environment. In CI/CD pipelines, Docker helps ensure consistency across
different stages of development, testing, and production by using containerized environments.
Blue-green deployment is a strategy where two identical production environments (blue and
green) are maintained. The blue environment runs the current application version, while the
green environment hosts the new version. Once the green environment is ready and tested,
traffic is switched from blue to green with minimal downtime.
Q 12. What is an artifact repository?
Q 13. What is blue-green deployment?
Q 14. How does Docker integrate with CI/CD pipelines?
Q 15. What is the role of configuration management tools in
CI/CD?

consistent and reproducible, reducing errors and speeding up the deployment process in CI/CD
pipelines.
Factor Continuous Integration (CI) Continuous Testing (CT)
Automates code integration into aAutomates the process of testing code
Definition
shared repository. throughout the development cycle.
Ensuring code quality by running tests at every
stage.
Focus Code integration and building.
Verifies that the new code does notVerifies that the application works as expected
Role
break the main branch. at each stage of development.
Version control is critical for CI/CD because it allows developers to track and manage changes
in the codebase. In CI/CD, version control systems like Git ensure that the most recent code
changes are automatically pulled into the pipeline for integration, testing, and deployment. This
allows the pipeline to run smoothly and ensures that all team members are working on the
latest code version.
Canary deployment is a strategy where a new version of an application is initially rolled out to a
small subset of users (the "canaries"). If the new version performs well, it is gradually rolled out
to the remaining users. This minimizes risk by ensuring that potential issues are detected early
in a smaller group.
A rollback in CI/CD refers to reverting the application or system to a previous stable version.
This is typically done when a new deployment introduces issues or bugs that affect the
application’s functionality. Rollbacks are essential in CI/CD pipelines to maintain system
stability and minimize downtime.
Q 19. What is Canary Deployment?
Q 18. What is a rollback in CI/CD pipelines?
Q 17. How does version control contribute to CI/CD?
Q 16. What are the differences between Continuous Integration
and Continuous Testing?

Q 21. What is the role of monitoring in CI/CD pipelines?
Monitoring is crucial in CI/CD pipelines to track the performance of applications at each stage
of the pipeline. It helps to identify potential issues early, such as failing tests, performance
bottlenecks, or deployment failures. Continuous monitoring ensures that the system stays
healthy and performs well, improving the overall reliability of the application.
Q 23. What are the different stages in a CI/CD pipeline?
Q 24. How does containerization improve CI/CD pipelines?
Q 22. How can you handle database changes in CI/CD pipelines?
Database changes can be managed in CI/CD pipelines by using tools like Liquibase or Flyway.
These tools automate database migrations, ensuring that any changes to the database schema
are consistent and versioned, just like code changes. The database migration process is
integrated into the pipeline, allowing for smooth deployments and minimizing the risk of
database inconsistencies.
Q 20. What is the difference between Continuous Deployment and
Continuous Delivery?
Source: Pulling the latest code from the version control system.
Build: Compiling and building the application.
Test: Automated tests are run to ensure code quality.
Deploy: Deploying the code to staging or production environments.
Monitor: Monitoring the application for errors, performance issues, and user feedback.
Factor Continuous Deployment Continuous Delivery
Automatically deploys every changeAutomatically prepares every change for
manualdeployment but requires manual approval to
Deﬁnitionto production without
intervention. push to production.
Automates the deployment from theAutomates the testing and staging processes,
Process
pipeline to production. but the ﬁnal deployment step is manual.
Higher risk as all changes areLower risk, as deployment can be controlled
immediately deployed to production.manually if necessary.
Risk

Security in CI/CD pipelines can be managed through practices like:
Static Application Security Testing (SAST): Performing security checks during the code
integration phase to catch vulnerabilities early.
Integration with Legacy Systems: Older systems may not be compatible with modern
CI/CD practices, requiring additional work for integration.
Tooling Complexity: Managing multiple tools and technologies for different stages of the
pipeline can become complex.
Test Automation: Ensuring reliable and comprehensive automated tests for different parts
of the application.
Pipeline Configuration: Setting up a CI/CD pipeline that is flexible, reliable, and scales with
the growth of the application.
Aspect Continuous Integration (CI) Continuous Deployment (CD)
CI focuses on automating theCD automates the deployment of the
integration of code changes into aintegrated code to production without
Definition
shared repository. manual intervention.
Frequent code merges are doneCode changes are deployed to production
Frequency
several times a day. as soon as they pass testing.
Automates the process of codeAutomates the entire process, from code
Automation
integration and testing. integration to production deployment.
Containerization improves CI/CD pipelines by providing consistent environments for
development, testing, and deployment. Here are the key benefits:
Eliminates environment inconsistencies by packaging applications with all dependencies.
Speeds up deployment with lightweight containers that start faster than virtual machines.
Enhances scalability by enabling container orchestration tools like Kubernetes for efficient
resource management.
Facilitates rollback with versioned container images.
Q 25. What are some common challenges in CI/CD
implementation?
Q 27. How do you manage security in CI/CD pipelines?
Q 26. What is the difference between Continuous Integration and

Dynamic Application Security Testing (DAST): Scanning applications during runtime to
identify security risks in deployed environments.
Secrets Management: Using secure storage and management practices for sensitive data
such as API keys and passwords.
Access Controls: Limiting who can access different stages of the pipeline, ensuring only
authorized personnel can push to production.
Aspect Build Release
A build refers to the process of compiling andA release refers to making the build
Deﬁnitionpackaging the application code into anavailable for deployment or to end-
executable artifact. users.
Focuses on distributing the build to
production
Focuses on converting source code into a
deployable artifact.
Focus end-users
environments.
or
Occurs early in the CI/CD pipeline after codeOccurs after successful testing and
Timing
integration. before deployment.
Automated testing in CI/CD ensures that new code changes do not introduce bugs or
regressions by automatically running tests at each stage. This process includes:
Unit Tests: Testing individual components or functions of the application.
Integration Tests: Testing how different parts of the application work together.
Acceptance Tests: Validating the end-to-end functionality from the user's perspective.
Infrastructure as Code (IaC) involves managing and provisioning infrastructure through code
rather than manual processes. In CI/CD, IaC ensures that environments are consistent,
reproducible, and can be easily deployed across different stages of the pipeline. Tools like
Terraform and AWS CloudFormation are used to manage infrastructure in a CI/CD context.
Q 28. What is the purpose of automated testing in a CI/CD
pipeline?
Q 29. What is the difference between a build and a release in a
CI/CD pipeline?
Q 30. What is Infrastructure as Code (IaC), and how does it relate
to CI/CD?

Q 32: What is the role of Docker in CI/CD pipelines?
Docker helps in CI/CD pipelines by providing a lightweight, consistent, and
environment for testing, building, and deploying applications. It allows for:
Q 31. How do you handle environment variables in a CI/CD
pipeline?
Environment variables in a CI/CD pipeline are used to store sensitive data (e.g., API keys,
passwords) and configuration details. They are typically handled by:
Q 33. How do you handle database migrations in a CI/CD pipeline?
Database migrations are critical in CI/CD pipelines to ensure that changes to the database
schema are applied correctly. Best practices include:
isolated
Version Control: Storing migration scripts in the same repository as the application code.
Automated Migrations: Using tools like Flyway or Liquibase to automate schema changes
during the pipeline execution.
Environment Consistency: Ensures that the application runs the same in different
environments (development, staging, production).
Isolation: Runs applications in containers, preventing conflicts with other processes on the
system.
Portability: Docker containers can be deployed across any platform, from local machines
to cloud infrastructure.
Secure Storage: Using environment variable management tools such as Vault, AWS
Secrets Manager, or Kubernetes Secrets to securely store sensitive data.
Configuration Files: Using files like ̀`.env` for non-sensitive environment-specific variables.
Injection into Pipelines: Injecting environment variables during the pipeline execution to
customize builds and deployments.

Rollback Mechanisms: Implementing rollback scripts to revert database changes if issues
arise.
A staging environment in a CI/CD pipeline is a replica of the production environment used to
test the application before it is deployed to production. It allows for:
Final Testing: Testing new features in an environment similar to production to ensure they
work as expected.
Quality Assurance: QA teams verify that everything works smoothly before deployment.
Risk Mitigation: Ensuring that no issues are introduced into the production environment.
To ensure high availability in a CI/CD pipeline, the following practices are implemented:
Redundancy: Set up multiple build agents and servers to handle failures and prevent
downtime.
Load Balancing: Distribute workloads across multiple servers to avoid overloading any
single point.
Monitoring and Alerts: Use monitoring tools to detect issues in real time and trigger alerts
for a quick resolution.
Backup Strategies: Maintain backups of critical configurations and pipeline scripts to
recover quickly after disruptions.
Containerization, often using Docker, plays an essential role in CI/CD pipelines by providing
consistency across different environments. It ensures that the application runs the same in
all stages, from development to production. Benefits include:
Isolation: Applications run in containers with all dependencies bundled together,
preventing conflicts with other software.
Portability: Containers can be deployed consistently across different platforms, ensuring
reliable builds and tests.
Scalability: Containers allow for easy scaling of applications as demand increases.
Q 34. What is the role of a staging environment in a CI/CD
pipeline?
Q 38. What is the role of version control in CI/CD pipelines?
Q 35. How do you ensure high availability in a CI/CD pipeline?
Q 37. What is the purpose of containerization in CI/CD pipelines?

Factor Continuous Integration (CI) Continuous Testing (CT)
CT ensures that the software
is
continuously tested, running automated
tests at each stage to verify functionality
and quality.
Focuses on testing the functionality and
quality of the code throughout the entire
development cycle.
CI automates the integration of code
into the shared repository and runs
tests to check for integration issues.
Definition
Focuses on merging and integrating
code with automated testing.
Focus
Automates code integration andAutomates the process of running tests
Automation
testing processes. continuously across the codebase.
Version control systems, like Git, play a critical role in CI/CD pipelines by providing a central
place to store and track code changes. These systems enable:
Code History: Track and manage changes made to the codebase, making it easier to debug
and resolve issues.
Collaboration: Multiple developers can work on the same project simultaneously without
overwriting each other's work.
Automated Pipelines: CI/CD tools can automatically pull the latest code changes from
version control systems to trigger builds and deployments.
Automated testing is vital in CI/CD pipelines as it helps identify issues early in the development
process. Key benefits of automated testing include:
Early Detection: Automated tests quickly catch bugs or issues introduced by new changes,
reducing the time spent on manual testing.
Faster Feedback: Developers receive immediate feedback on their code, improving code
quality and reducing errors.
Efficiency: Automated tests run faster than manual testing, allowing for frequent and
thorough checks without slowing down the development process.
Q 41. How does CI/CD impact software quality?
Q 40. What is the significance of automated testing in CI/CD
pipelines?
Continuous Testing?

Factor Monolithic Architecture
Monolithic applications are deployedMicroservices
Microservices Architecture
are deployed as
Deploymentas a single unit, which can complicateindependent services, allowing for more
deployment and scaling.
Testing is often done on the entireEach
application at once, making it slowerindependently,
flexible and scalable deployment.
be
microservice can tested
testing
Testing improving
and more complex. efficiency and speed.
Scaling a monolithic applicationMicroservices allow for scaling individual
typically requires scaling the entireservices independently, providing better
Scaling
application. resource optimization.
Pipeline as Code refers to the practice of defining and managing CI/CD pipelines through code.
This is typically done using configuration files like YAML or JSON, which describe the steps and
processes in the pipeline. Benefits include:
Versioning: Pipelines can be versioned alongside application code, enabling easy rollback
to previous pipeline versions.
Consistency: Pipelines as code ensure the same pipeline configuration is used across
different environments.
Automation: Allows for automatic pipeline setup, reducing manual configuration and
ensuring consistency.
CI/CD positively impacts software quality by enabling rapid and frequent testing of new code
changes. Key ways it improves software quality include:
Automated Testing: Frequent automated tests ensure that issues are caught early,
reducing defects in production.
Frequent Releases: Smaller, frequent releases help catch bugs and errors earlier in the
development process, reducing the risk of large-scale failures.
Code Reviews: Integration of automated code reviews in CI processes ensures that high-
quality code is pushed to production.
Q 42. What is a Pipeline as Code?
Q 44. What is the role of a CI/CD pipeline in DevOps?
Q 43. What are the differences between monolithic and
microservices architectures in CI/CD pipelines?

A rollback strategy is crucial for quickly reverting to a stable version of the application in case
of deployment failure. Key elements of a rollback strategy include:
In a rolling deployment, new versions of an application are gradually rolled out to production
servers, replacing old versions one server at a time. This method minimizes downtime and
allows for:
Gradual Rollout: Traffic is split between old and new versions to reduce risk.
Minimal Disruption: It avoids complete downtime by ensuring the application remains
available during deployment.
Easy Rollback: If issues arise, only a small portion of the application is affected, simplifying
rollback.
A CI/CD pipeline plays a crucial role in DevOps by automating the processes of integrating
code and deploying it to production. This automation improves:
Collaboration: It fosters collaboration between developers and operations teams by
streamlining workflows.
Efficiency: Automated testing and deployment reduce manual intervention and accelerate
delivery cycles.
Quality: Continuous testing ensures that code is of high quality and free of errors before
being deployed.
A canary deployment is a release strategy where a new version of an application is rolled out to
a small subset of users before a full-scale deployment. It allows teams to monitor the behavior
and performance of the new release in a real-world environment.
In CI/CD pipelines, canary deployments are automated to gradually increase traffic to the new
version while monitoring for errors or performance issues. If problems are detected, the rollout
can be stopped or reverted.
Q 47. What is the purpose of a rollback strategy in a CI/CD
pipeline?
Q 45. How does a rolling deployment work in a CI/CD pipeline?
Q 46. What is the purpose of a canary deployment, and how is it
used in CI/CD pipelines?

Automation: Rollbacks should be automated to reduce human error and downtime.
Backup Mechanism: Ensure that previous versions of the application are readily available
for quick restoration.
Clear Rollback Criteria: Define specific failure criteria to trigger a rollback, such as a failed
test or a crash in production.
Jenkins is a popular open-source automation server that facilitates the building, testing, and
deployment of code. Some of its key benefits in CI/CD pipelines are:
Automation: Jenkins automates repetitive tasks such as code integration, testing, and
deployment.
Scalability: Jenkins can scale to handle large and complex projects with multiple pipelines
running concurrently.
Plugins: Jenkins supports a wide range of plugins that integrate with different tools for
version control, build tools and deployment processes.
A canary release is a deployment strategy where the new version of an application is first
released to a small subset of users (the "canaries"). The goal is to detect any issues in the
new release before they affect all users. Key benefits include:
Early Detection: Problems can be identified and resolved quickly without impacting the
entire user base.
Controlled Rollout: Only a small percentage of users receive the new version initially,
reducing the risk of large-scale failures.
Gradual Scaling: If the release is successful, it can be gradually rolled out to more users.
Q 48. What is a canary release in CI/CD?
Q 50. How does feature toggling work in a CI/CD pipeline?
Q 49. What are the key benefits of using Jenkins in a CI/CD
pipeline?

Factor
Definition
Deployment
Frequency
Automation
Level
A CI/CD pipeline plays an essential role in automating the integration and delivery processes in
software development. It allows for:
Efficient Code Integration: Continuous integration ensures that code changes are
automatically merged into the shared repository without conflicts.
Automated Testing: Automated tests are triggered during integration to detect bugs and
ensure code quality.
Frequent Delivery: Continuous delivery automates the deployment of code to staging or
production, ensuring faster releases.
Continuous Integration (CI) Continuous Deployment (CD)
CI involves the frequent merging ofCD automates the entire process of code
code into a shared repository,deployment to production without manual
followed by automated testing tointervention, making code available to end
ensure code integrity.
Code is integrated regularly, but
happen
users continuously.
Code is deployed to production frequently,
often several times a day.
deployment
immediately.
Automates code integration andAutomates code deployment and release
may not
testing. to production.
Feature toggling (also known as feature flags) allows you to enable or disable certain features
of an application without deploying new code. This can be useful for:
Testing Features:This enables you to test features in production with real users without
fully exposing them to everyone.
Gradual Rollouts: Allows you to gradually roll out features to users in different stages,
reducing risk.
Quick Rollback: If an issue occurs, you can disable the feature without needing to roll back
the entire deployment.
Q 51. What is the role of a CI/CD pipeline in software
development?
Q 53. How can you handle secrets securely in a CI/CD pipeline?

To handle secrets securely in a CI/CD pipeline, you can follow these best practices:
Secret Management Tools: Use tools like HashiCorp Vault, AWS Secrets Manager, or Azure
Key Vault to store and retrieve sensitive information securely.
Environment Variables: Store secrets in encrypted environment variables and access them
during pipeline execution.
Access Control: Restrict access to secrets based on roles and permissions to prevent
unauthorized usage.
Avoid Hardcoding: Never hardcode secrets in code or configuration files to reduce security
risks.
YAML is widely used in CI/CD pipelines for defining workflows, configurations, and deployment
steps. It provides a human-readable syntax to configure pipeline jobs, making it easy to manage
and automate tasks such as builds, tests, and deployments.
A multi-branch pipeline in Jenkins is a type of pipeline that automatically creates a new
pipeline for each branch in the repository. Benefits include:
Automatic Branch Detection: Jenkins automatically detects branches and creates a
separate pipeline for each, which simplifies managing multiple branches.
Customized Pipelines: Different branches can have customized build and deployment
processes, depending on the code’s requirements.
Efficient Parallel Builds: Each branch can run independently, enabling parallel execution of
builds and tests.
Parallel execution in CI/CD pipelines allows multiple tests or tasks to run simultaneously,
significantly speeding up the process. It provides:
Efficiency: Tests and build processes are run concurrently rather than sequentially,
reducing pipeline execution time.
Scalability: Parallel execution allows for scaling the testing and building process to handle
large applications and complex workflows.
Faster Feedback: Developers receive faster results and can address issues more promptly.
Q 55. What is a multi-branch pipeline in Jenkins?
Q 56. What is the role of YAML in CI/CD pipelines?
Q 54. How does parallel execution work in CI/CD pipelines?

Q 58. How do you ensure security in CI/CD pipelines?
Security in CI/CD pipelines is crucial to prevent vulnerabilities from being introduced into the
codebase or the deployment process. Key strategies include:
Q 57. What are feature flags, and how are they implemented in a
CI/CD pipeline??
Feature flags, also known as feature toggles, are a mechanism that allows teams to enable or
disable specific features in a codebase without deploying new code.
Q 59. What is the difference between a build pipeline and a release
pipeline?
Integrate a feature flag management tool like LaunchDarkly or Firebase Remote Config into
your project.
Wrap the new feature code with conditional statements controlled by the feature flag.
Configure the feature flag in the management tool to define which users or environments
can access the feature.
Enable gradual rollout to test the feature with specific user groups before full deployment.
Monitor feature performance and user feedback, then adjust the flag as needed.
Turn off or remove the flag after confirming the feature is stable and fully deployed.
Automated Security Scanning: Integrate security tools to automatically scan for
vulnerabilities in the code during the build or testing stages.
Code Reviews: Conduct code reviews and peer checks to catch security flaws before they
reach production.
Access Control: Implement strong access control policies to limit who can trigger builds or
deployments, preventing unauthorized access.
Factor Build Pipeline Release Pipeline
A build pipeline focuses onA release pipeline is concerned with
Definitioncompiling code, running tests, anddeploying the build artifacts to staging or
creating deployable artifacts. production environments.
Focuses on ensuring that the code isFocuses on delivering the code to end-users
Focus
integrated, compiled, and tested. by deploying it to the relevant environments.
FrequencyBuild pipelines are typically triggeredRelease pipelines are triggered when the
with each code commit to ensure thecode is ready for production deployment,

code is functional.
Further Read Articles: HTML Multiple Choice
Questions and Answers TCS Angular Interview
Questions and Answers Microsoft Interview
Questions and Answers Google Interview
Questions and Answers
often after successful testing.
To optimize CI/CD pipeline performance, the following practices can be adopted:
Parallel Execution: Run tests and build jobs in parallel to reduce overall pipeline execution
time.
Caching: Use caching mechanisms to avoid rebuilding or re-downloading dependencies
repeatedly.
Pipeline Segmentation: Divide pipelines into smaller stages to focus on specific tasks and
troubleshoot more easily.
Regular Maintenance: Remove unused jobs and update tools to avoid unnecessary
overhead.
Efficient Testing: Run only relevant test cases based on recent code changes instead of
running the entire test suite.
In conclusion, CI/CD pipeline interview questions test your understanding of automation in
development and deployment processes. Mastery of these concepts is crucial for optimizing
workflows and improving software quality. Being well-prepared for CI/CD pipeline interview
questions ensures you're ready to handle real-world challenges in DevOps roles and helps
accelerate development cycles.
Dear learners, join our Tech Trendy Masterclasses to help you learn and immerse yourself in
the latest trending technologies and upgrade your tech skills with the latest skills trends,
design, and practices.
Q 60. What are the best practices for optimizing CI/CD pipeline
performance?
Conclusion

CI CD Pipeline Interview Questions PDF By ScholarHat

More Related Content

Similar to CI CD Pipeline Interview Questions PDF By ScholarHat (20)

More from Scholarhat (20)

Recently uploaded (20)

CI CD Pipeline Interview Questions PDF By ScholarHat