CICD Automation and Deployment Strategies Flashcards
AWS DevOps Engineer Professional DOP-C02 Flashcards

| Front | Back |
| How can monitoring improve CI/CD pipelines | Detects issues quickly and ensures the deployed application is operating as expected |
| How does pipeline optimization improve CI/CD | Reduces pipeline latency, increases reliability, and speeds up delivery times |
| How is AWS Elastic Beanstalk used in CI/CD | Manages applications and their environments with built-in scaling and deployment automation |
| What are deployment pipelines hazards | Examples include configuration drift, failed rollbacks, and insufficient testing |
| What are pre-deployment checks | Automated validations to ensure readiness of code and infrastructure prior to deployment |
| What are the key benefits of IaC | Consistency, repeatability, and easier version control of infrastructure |
| What is a Build Pipeline | A sequence of automated steps to compile, test, and prepare code for deployment |
| What is a deployment pattern | A defined strategy for rolling out software changes to production environments |
| What is a feature flag in deployment strategies | A technique used to enable or disable functionality without deploying new code |
| What is a pipeline stage in CI/CD | A distinct phase in the build, test, or deployment process of a CI/CD pipeline |
| What is a self-healing system in deployment strategies | Systems that automatically recover from failures without human intervention |
| What is A/B Testing in deployment strategies | Deploying two versions of an application to test which one performs better |
| What is Artifact in CI/CD | A file or set of files created during the build process that is used in later stages |
| What is Blue-Green Deployment | Maintaining two environments, one active and one idle, and switching traffic seamlessly to reduce downtime |
| What is Canary Deployment | Gradually rolling out changes to a subset of servers or users before full deployment |
| What is Chaos Engineering in CI/CD | The practice of intentionally introducing faults to improve system resilience |
| What is Continuous Deployment (CD) | The automated process of deploying code changes to production after passing all stages in the pipeline |
| What is Continuous Integration (CI) | The practice of merging code changes into a shared repository frequently and automatically testing them |
| What is immutable infrastructure | Infrastructure that cannot be changed once deployed, ensuring consistency and reliability |
| What is Infrastructure as Code (IaC) | Managing and provisioning infrastructure using code rather than manual processes |
| What is Rollback in deployment strategies | Reverting to a previous version of code if the current deployment causes issues |
| What is the advantage of using GitOps for CI/CD | Uses Git as the single source of truth for CI/CD operations, ensuring consistency and auditability |
| What is the advantage of using serverless technologies in CI/CD | Reduces management overhead and scales automatically, fitting dynamic workloads |
| What is the benefit of parallel execution in pipelines | Makes pipelines faster by running multiple tasks simultaneously |
| What is the difference between Continuous Delivery and Continuous Deployment | Continuous Delivery requires manual approval for production deployment, while Continuous Deployment is fully automated |
| What is the difference between on-demand scaling and auto-scaling | On-demand scaling requires manual intervention; auto-scaling occurs automatically based on triggers |
| What is the difference between push-based and pull-based deployments | Push-based pushes updates to target systems; pull-based lets the target system fetch updates |
| What is the main benefit of CI/CD | Faster delivery of features while maintaining code quality and stability |
| What is the purpose of automated tests in CI/CD pipelines | To ensure code quality and functionality before deployment |
| What is the purpose of AWS CodeBuild | Building and testing source code projects for CI/CD pipelines |
| What is the purpose of code linting in CI/CD | Ensures code quality by identifying syntax errors and enforcing style guidelines |
| What is the purpose of environment variables in CI/CD | A way to inject configuration settings specific to an environment without changing code |
| What is the purpose of unit tests in CI/CD | To validate the smallest parts of the codebase in isolation |
| What is the role of caching in CI/CD optimization | Speeds up build and test phases by reusing previously processed data |
| What is the role of containerization in CI/CD | Provides a consistent environment for applications by packaging all dependencies |
| What is the use of AWS CodeDeploy | Automates the deployment of applications to instances, containers, or serverless functions |
| Which AWS service is commonly used for CI/CD pipelines | AWS CodePipeline |
| Why is version control essential for CI/CD | Ensures collaboration, tracking changes, and allows rollback if issues arise |
About the Flashcards
Flashcards for the AWS DevOps Engineer Professional exam present concise questions and answers on CI/CD fundamentals and pipeline mechanics. The deck covers build pipelines, artifacts, pipeline stages, automated and unit testing, code linting, and version control, plus common AWS tooling used in pipelines such as AWS CodePipeline, CodeBuild, CodeDeploy, and Elastic Beanstalk.
Focused on terminology, concepts, and key ideas, these cards review deployment patterns (canary, blue-green, A/B testing), feature flags and environment variables, Infrastructure as Code and immutable infrastructure, containerization and serverless models, rollback and self-healing strategies, plus pipeline optimization, caching, parallel execution, scaling modes, GitOps and chaos engineering for resilience.
Topics covered in this flashcard deck:
- CI/CD fundamentals
- Build and pipeline stages
- Deployment strategies
- AWS CI/CD services
- Testing and automation
- Infrastructure as Code