cicd_flashcards

Question 1

Term

Answer 1

Definition

Question 2

CI/CD

Answer 2

Continuous integration and continuous deployment. Automated process for testing and deploying code changes.

Question 3

Continuous Integration (CI)

Answer 3

Automatically building and testing code every time someone commits changes. Catches bugs early before they make it to production.

Question 4

Continuous Deployment (CD)

Answer 4

Automatically deploying code to production after it passes all tests. Gets features to users faster with less manual work.

Question 5

Continuous Delivery

Answer 5

Similar to continuous deployment but requires manual approval before production. Code is always ready to deploy but someone has to push the button.

Question 6

Pipeline

Answer 6

Series of automated steps that code goes through from commit to deployment. Typically includes build, test, and deploy stages.

Question 7

Build Stage

Answer 7

Compiles code, installs dependencies, and packages application. Creates deployable artifact like a zip file or container image.

Question 8

Test Stage

Answer 8

Runs automated tests to verify code works correctly. Includes unit tests, integration tests, and sometimes end-to-end tests.

Question 9

Deploy Stage

Answer 9

Pushes code to target environment like dev, staging, or production. Applies infrastructure changes and restarts services.

Question 10

Artifact

Answer 10

Packaged version of your code ready to deploy. Could be zip file, docker image, or compiled binary.

Question 11

Environment

Answer 11

Isolated instance where your application runs. Typically have dev for development, staging for testing, prod for users.

Question 12

Rollback

Answer 12

Reverting to previous version when deployment fails. Safety mechanism to undo bad changes quickly.

Question 13

Blue-Green Deployment

Answer 13

Running two identical environments where you switch traffic between them. Lets you deploy with zero downtime and easy rollback.

Question 14

Canary Deployment

Answer 14

Gradually rolling out changes to small percentage of users first. If it works, increase percentage until everyone gets new version.

Question 15

Feature Flag

Answer 15

Toggle that turns features on or off without deploying new code. Lets you deploy code but control when users see it.

Question 16

Automated Testing

Answer 16

Running tests automatically as part of pipeline. Catches bugs before they reach users.

Question 17

Unit Test

Answer 17

Tests individual functions or components in isolation. Fast and catches basic logic errors.

Question 18

Integration Test

Answer 18

Tests how different parts of system work together. Slower but catches issues between components.

Question 19

Smoke Test

Answer 19

Basic test that verifies core functionality works after deployment. Quick sanity check that nothing is completely broken.

Question 20

Deployment Trigger

Answer 20

Event that starts the pipeline. Usually a git commit or merge to specific branch.

Question 21

Approval Gate

Answer 21

Manual step where human reviews and approves before continuing. Common before production deployments.

Question 22

Webhook

Answer 22

Notification sent when event happens. Used to trigger pipelines when code is pushed.

Question 23

Infrastructure as Code (IaC)

Answer 23

Managing infrastructure using code files instead of manual configuration. Terraform is common tool for this.

Question 24

Version Control Integration

Answer 24

Pipeline automatically triggered by commits to git repository. Watches specific branches like main or develop.

Question 25

Build Artifact Repository

Answer 25

Storage location for built packages. Examples are Artifactory, Nexus, or S3.

Question 26

Container Registry

Answer 26

Storage for Docker images. Examples are ECR, Docker Hub, or Artifactory.

Question 27

Deployment Automation

Answer 27

Scripts or tools that handle deploying code without manual steps. Uses tools like AWS CodeDeploy, Jenkins, or GitHub Actions.

Question 28

Monitoring and Alerts

Answer 28

Tracking application health after deployment. Alerts team if something goes wrong.

Question 29

GitOps

Answer 29

Using git as single source of truth for infrastructure and applications. Changes to git automatically trigger deployments.

Question 30

Jenkins

Answer 30

Open source automation server for building CI/CD pipelines.

Question 31

GitHub Actions

Answer 31

CI/CD built into GitHub that runs workflows based on repository events.

Question 32

GitLab CI/CD

Answer 32

Built into GitLab with pipelines defined in yaml files.

Question 33

AWS CodePipeline

Answer 33

AWS service that orchestrates build, test, and deploy stages.

Question 34

AWS CodeBuild

Answer 34

AWS service that compiles code and runs tests.

Question 35

AWS CodeDeploy

Answer 35

AWS service that automates deployments to EC2, Lambda, or ECS.

Question 36

CircleCI

Answer 36

Cloud-based CI/CD platform with easy configuration.

Question 37

Travis CI

Answer 37

CI/CD service that integrates with GitHub.

Question 38

Terraform (in CI/CD)

Answer 38

Infrastructure as code tool used in deployment pipelines.

Question 39

Docker (in CI/CD)

Answer 39

Containerization platform used to package applications.

Question 40

Kubernetes (in CI/CD)

Answer 40

Container orchestration used for deploying and scaling applications.