--- title: "CI/CD: Pipeline Automation Essentials" description: "Test your knowledge of CI/CD fundamentals with a quiz covering continuous integration, continuous delivery, pipelines, deployment strategies, automated testing, Infrastructure as Code, and DevOps best practices." author: "Mohammad Abu Mattar" canonical: https://mkabumattar.com/quizzes/post/cicd-pipeline-essentials-quiz --- # CI/CD: Pipeline Automation Essentials Welcome to the CI/CD Basics Quiz! This quiz covers fundamental continuous integration and continuous delivery concepts, pipeline automation, and modern DevOps best practices. Each question is multiple-choice, and you'll find hints to help you along the way. Good luck! ## Questions ### 1. What is the primary goal of Continuous Integration (CI)? - Automating the review of manual documentation - Automating the build and testing of code changes - Automating the customer billing and sales cycle - Automating the encryption of local source files **Hint:** Think about merging code frequently. ### 2. What is a "Pipeline" in CI/CD? - A hardware interface for server cooling systems - A sequence of automated stages for code delivery - A database structure for storing user credentials - A communication channel for developer chat logs **Hint:** A sequence of automated steps. ### 3. What is the difference between Continuous Delivery and Continuous Deployment? - Continuous Delivery involves only local builds - Continuous Delivery requires manual release approval - Continuous Deployment is restricted to hardware - Continuous Deployment occurs before the build stage **Hint:** One requires a human "Go" button. ### 4. What is a "Build Artifact"? - An outdated version of the project source code - A package ready for testing or deployment - A logical error found during the testing phase - A code comment used to document functionality **Hint:** The output of the build stage. ### 5. What does "Shift Left" mean in CI/CD? - Migrating code assets to a secondary backup server - Moving testing and security to earlier stages - Applying stylistic formatting to the source code - Reverting a repository to a previous stable state **Hint:** Moving tasks earlier in the process. ### 6. What is a "Runner" (or Agent) in a CI system? - A software architect who designs the pipeline - The environment that executes the pipeline jobs - A performance metric for measuring build speed - A specialized script for rotating API passwords **Hint:** The machine that does the work. ### 7. What is "YAML" used for in CI/CD? - Defining the application core business logic - Configuring pipeline stages and execution steps - Storing encrypted database connection strings - Compiling high-level code into machine binaries **Hint:** The configuration format. ### 8. What is a "Trigger" in a pipeline? - A maintenance script that purges build logs - An event that initiates a pipeline execution - A global variable used for arithmetic logic - A system alert sent to an on-call engineer **Hint:** The event that starts the engine. ### 9. What is the purpose of the "Testing" stage in a CI pipeline? - Optimizing the visual layout of the code - Validating code behavior and preventing regressions - Increasing the duration of the deployment cycle - Renaming local variables for improved security **Hint:** Validation. ### 10. What is "Infrastructure as Code" (IaC)? - Documenting network diagrams in a text file - Provisioning infrastructure via configuration files - Programming logic for structural engineering - The physical cabling within a data center **Hint:** Managing servers with files. ### 11. What is a "Staging Environment"? - A localized sandbox for individual developers - A production-mirror for final release validation - A storage server for historical database logs - A workstation used for designing user interfaces **Hint:** The dress rehearsal. ### 12. What is "Blue-Green Deployment"? - Updating the graphical theme of an application - Running two environments to minimize downtime - Reducing the power consumption of server racks - Resolving merge conflicts between two branches **Hint:** Two identical environments. ### 13. What is a "Canary Deployment"? - A deployment limited to legacy mobile devices - Phasing a release to a small subset of users - A deployment scheduled during low-traffic hours - A process for identifying unused container images **Hint:** Testing on a small group of users. ### 14. What is "Static Code Analysis" (Linting)? - Measuring execution time on a production server - Analyzing source code without executing it - Optimizing the file size of compiled binaries - Creating a backup of the main source branch **Hint:** Checking code without running it. ### 15. What is a "Secret" in a CI pipeline? - An unreleased feature hidden from the end user - Encrypted data injected during the build process - A repository branch that is hidden from public view - A dedicated server for private developer testing **Hint:** Passwords and API keys. ### 16. What is "Dockerization"? - Updating the Docker engine on a local machine - Packaging an application and its environment - Clearing unused network volumes and images - Virtualizing a full operating system for testing **Hint:** Putting the app in a container. ### 17. What is a "Webhook" in CI/CD? - An online documentation portal for web APIs - An automated HTTP callback triggered by an event - A hardware device used for network security - A method for downloading large binary files **Hint:** A notification sent from Git to the CI server. ### 18. What is "Environment Parity"? - The distribution of work across multiple teams - Consistency between Dev, Staging, and Production - The load-balancing of traffic across server clusters - A mathematical check for data transmission errors **Hint:** Making everything look the same. ### 19. What does "Rollback" mean? - Deleting the entire Git repository history - Reverting to the last known stable application version - Rotating the physical disks in a server rack - Optimizing the code for faster execution speeds **Hint:** Going back to the previous version. ### 20. What is "Orchestration" in CI/CD? - A collaborative code-writing session for teams - Automated management of complex systems - Generating documentation from source code comments - A list of static IP addresses for build servers **Hint:** Managing multiple containers/tasks. ### 21. What is "Parallelism" in a pipeline? - Redundant coding of features by two developers - Executing multiple jobs simultaneously - A software bug that creates an infinite loop - Encrypting data across multiple storage drives **Hint:** Doing many things at once. ### 22. What is a "Self-hosted Runner"? - A script that executes only on local laptops - A CI agent managed on private infrastructure - A server that functions without network access - A developer who manages their own deployments **Hint:** Using your own server for CI. ### 23. What is "Continuous Monitoring"? - Manually observing build logs in the console - Tracking application health and performance - Restricting user access to production environments - Upgrading the physical monitor of a workstation **Hint:** Watching the app in production. ### 24. What is a "Pull Request Build"? - A build scheduled for monthly maintenance - A pipeline triggered by proposed code changes - A manual command used to download repositories - A physical construction project for data centers **Hint:** Testing code before it is merged. ### 25. What is "GitOps"? - A method for taking notes using Git commits - Using Git as the source of truth for infrastructure - A customized hardware keyboard for Git commands - The process of deleting a repository history **Hint:** Git as the single source of truth for infrastructure. ### 26. What is "Dependency Scanning"? - Analyzing which teams depend on a specific API - Checking third-party libraries for vulnerabilities - Updating all local libraries to the latest version - A medical diagnostic for identifying system lag **Hint:** Checking your libraries for vulnerabilities. ### 27. What is "Manual Approval" in a pipeline? - The act of manually typing the application code - A human intervention gate in the pipeline - A debugging process for finding manual errors - An authentication password for starting a server **Hint:** A human must click the button. ### 28. What is a "Hotfix"? - A server cooling repair for overheating hardware - An emergency repair for a critical production bug - A bug caused by high-temperature data centers - A method for purging old code from the repository **Hint:** A fast fix for a production bug. ### 29. What is "Fail Fast"? - A critical system crash during high-traffic events - Stopping a pipeline immediately upon any failure - Optimizing the code to run as fast as possible - A racing term for high-speed hardware failures **Hint:** Stopping the pipeline immediately on error. ### 30. What is "DevSecOps"? - A specialized team of external security auditors - Integrating security into every pipeline stage - A sophisticated computer virus or malware type - A method for hiding code from other developers **Hint:** Integrating security into DevOps.