Deployment and DevOps Flashcards
What is a CI/CD pipeline, and why is it important in modern software development?
A CI/CD (Continuous Integration/Continuous Deployment) pipeline automates the process of building, testing, and deploying software. It helps maintain code quality, accelerates development cycles, and ensures faster and more reliable releases.
Explain the difference between Continuous Integration and Continuous Deployment.
Continuous Integration (CI) involves frequently merging code changes into a shared repository, followed by automated testing to catch integration issues. Continuous Deployment (CD) takes CI a step further by automatically deploying code to production environments after passing automated tests.
What are the key components of a CI/CD pipeline?
A typical CI/CD pipeline consists of source code repositories, build automation, testing, deployment automation, and monitoring.
How does a version control system like Git play a role in CI/CD?
Git helps manage source code versions and facilitates collaborative development. It allows developers to work on different branches, merge changes, and trigger CI/CD processes upon code commits.
What is Jenkins, and how does it relate to CI/CD?
Jenkins is an open-source automation server that helps automate various stages of the CI/CD pipeline, including building, testing, and deployment.
How would you handle flaky tests in your CI/CD pipeline?
Flaky tests are unreliable tests that sometimes pass and sometimes fail without changes to the code. They should be investigated and fixed or excluded to ensure the pipeline’s accuracy.
Can you describe the steps involved in a typical CI/CD pipeline?
A standard CI/CD pipeline includes stages such as code checkout, build, automated testing, artifact generation, deployment to staging, further testing, and deployment to production.
What is the purpose of a post-deployment validation step in a CI/CD pipeline?
Post-deployment validation ensures that the newly deployed code functions as expected in the production environment by running additional tests and checks.
How can you optimize a CI/CD pipeline for faster feedback to developers?
Pipeline optimization can involve parallelizing tasks, using caching, optimizing build scripts, and using tools that provide rapid feedback on test results.
Explain Blue-Green Deployment and how it reduces downtime during releases.
Blue-Green Deployment involves maintaining two identical environments: one for the currently live version (Blue) and the other for the new release (Green). Switching the router’s traffic from Blue to Green minimizes downtime.
What is Docker, and how does it help in the context of deployment and DevOps?
Docker is a platform that allows you to package applications and their dependencies into containers, ensuring consistent environments across development, testing, and production
How is a Docker container different from a virtual machine?
Docker containers share the host operating system’s kernel, making them lightweight and resource-efficient compared to virtual machines, which require a full OS for each instance.
Explain the Docker image and Docker container relationship.
A Docker image is a snapshot of a file system and runtime environment, while a Docker container is a running instance of an image.
What is a Dockerfile, and how is it used?
A Dockerfile is a text file that contains instructions for building a Docker image. It specifies the base image, application code, dependencies, and configuration.
How do you handle sensitive information like passwords in Docker containers?
Sensitive information should be stored as environment variables or in Docker secrets to prevent exposure within the container or image.
What are Docker volumes, and why are they important?
Docker volumes provide a way to persist and share data between containers and the host machine, ensuring data durability and separation from container lifecycles.
Explain how orchestration tools like Kubernetes complement Docker containers.
Kubernetes manages the deployment, scaling, and management of containerized applications, making it easier to handle large, distributed systems of Docker containers.
What is Docker Compose, and when would you use it?
Docker Compose is a tool for defining and running multi-container Docker applications. It’s helpful for local development and testing environments.
Describe the process of containerizing a .NET application using Docker.
Containerizing a .NET application involves creating a Dockerfile, specifying the base image (e.g., .NET runtime), copying application files, setting environment variables, and building the Docker image.
What is the “Docker Hub,” and how does it relate to Docker?
Docker Hub is a cloud-based repository for Docker images. Developers can upload, share, and pull Docker images from Docker Hub.
How does feature toggling (feature flags) contribute to a more controlled deployment process?
Feature toggles allow you to enable or disable specific features in production, enabling gradual rollouts, A/B testing, and quick feature rollback if needed.
What is a rolling deployment, and how does it work?
A rolling deployment gradually replaces instances of the old application with new ones, ensuring a smooth transition and minimal disruption.
Describe the process of implementing a zero-downtime deployment strategy.
Zero-downtime deployment involves deploying new versions of an application without causing any service disruption. Strategies like Blue-Green or Canary deployments are commonly used.
When might you choose a monolithic deployment strategy over a microservices-based strategy?
Monolithic deployment might be preferred for smaller applications with limited complexity and when the development team size is small.
What is an immutable infrastructure, and how does it relate to deployment strategies?
An immutable infrastructure treats servers and resources as disposable entities. Instead of modifying existing servers, new ones are created with each change, enhancing consistency and reliability.
How can you ensure database schema changes are deployed smoothly alongside application changes?
Using database migration scripts, versioning, and testing can help ensure smooth database schema changes during deployments.
Explain the concept of continuous monitoring and how it relates to deployment strategies.
Continuous monitoring involves tracking application performance, health, and key metrics after deployment to promptly detect issues and ensure the success of deployment strategies.
What are the primary benefits of embracing DevOps practices in software development?
DevOps practices lead to faster development cycles, higher code quality, increased collaboration between teams, and improved software delivery.
How do you ensure security is maintained in a CI/CD pipeline?
Security practices include code analysis tools, vulnerability scans, encryption of sensitive data, and adhering to security best practices in every stage of the pipeline
Describe a situation where an automated deployment failed, and how did you troubleshoot and resolve the issue
Share a real or hypothetical scenario where a deployment failure occurred, explaining the steps you took to identify the issue and bring the system back to a functional state.
What are “Infrastructure as Code” (IaC) principles, and why are they important in modern DevOps practices?
Infrastructure as Code involves managing and provisioning infrastructure using code, which brings consistency, versioning, and reproducibility to infrastructure deployment.
How would you approach the deployment of a highly available application that spans multiple regions?
This involves setting up redundancy, load balancing, data replication, and monitoring across multiple regions to ensure high availability and fault tolerance.
What is the purpose of a post-mortem or retrospective after a deployment, and how does it contribute to the improvement of future deployments?
A post-mortem identifies what went wrong, what went well, and actionable insights for continuous improvement, helping prevent similar issues in the future.
Can you explain the concept of “Shift-Left” in the context of DevOps and testing?
“Shift-Left” refers to moving testing and quality assurance activities earlier in the software development lifecycle to catch issues before they become more costly to fix.
How would you handle a situation where a production deployment caused a critical performance issue in the application?
Approach the problem by identifying the root cause, rolling back if necessary, and conducting a thorough investigation to ensure the issue is resolved before proceeding.
What are some strategies for handling database schema changes in a microservices architecture with multiple, independently deployable services?
Implementing versioned API contracts, database migration scripts per service, and coordination between services can help manage database schema changes.
How do you balance the need for frequent releases with the stability and reliability of a production environment?
Use deployment strategies like feature flags, canary releases, and thorough automated testing to ensure that frequent releases don’t compromise production stability.
