✅ CI/CD Pipeline Interview Questions & Answers ⚙️🚀 

1️⃣ What is CI/CD?
A: CI/CD stands for Continuous Integration and Continuous Deployment/Delivery — practices that automate code integration, testing, and deployment.

2️⃣ What is Continuous Integration (CI)?
A: Developers frequently merge code into a shared repo. Each merge triggers automated builds & tests to detect issues early.

3️⃣ What is Continuous Deployment/Delivery (CD)? 
- Delivery: Code is automatically prepared for release but needs manual approval. 
- Deployment: Code is automatically pushed to production after passing tests.

4️⃣ Key Stages of a CI/CD Pipeline:
1. Code 
2. Build 
3. Test 
4. Release 
5. Deploy 
6. Monitor

5️⃣ What tools are used in CI/CD?
- CI: Jenkins, GitHub Actions, CircleCI, GitLab CI 
- CD: ArgoCD, Spinnaker, AWS CodeDeploy

6️⃣ What is a Build Pipeline?
A: A sequence of automated steps to compile, test, and prepare code for deployment.

7️⃣ What is a Webhook?
A: A trigger that starts the pipeline when new code is pushed to the repository.

8️⃣ What are Artifacts?
A: Output files generated after a build, like JARs, Docker images, etc., stored for deployment.

9️⃣ What is Rollback?
A: Reverting to the previous stable version if a deployment fails.

🔟 Why is CI/CD important? 
A: It increases code quality, reduces bugs, speeds up delivery, and ensures smoother collaboration.

💬 Tap ❤️ for more!