DevOps Monitoring, Testing & Deployment Strategies Flashcards

What is the primary purpose of application monitoring in DevOps?

Answer: To track application performance and detect issues early

Application monitoring in DevOps involves continuously collecting and analyzing data on an application's health, performance, and user experience. This proactive approach helps identify bottlenecks, errors, and potential issues in real-time, allowing teams to respond quickly and maintain service reliability. Early detection of issues is key to preventing major outages.

Which deployment strategy involves gradually rolling out changes to a subset of users?

Answer: Canary deployment

Canary deployment is a strategy where a new version of an application is gradually rolled out to a small subset of users or servers first. This allows teams to monitor its performance and stability with real traffic before fully deploying it to the entire user base. This minimizes risk by isolating potential issues to a limited audience.

Why is automated testing important in CI/CD pipelines?

Answer: It ensures quality by catching bugs early

Automated testing is a cornerstone of CI/CD, as it quickly and consistently verifies code changes at various stages of the pipeline. By catching bugs and regressions early in the development cycle, it significantly reduces the cost of fixing them and ensures the delivery of high-quality software. This early detection is vital for maintaining product quality and accelerating delivery.

Which tool is commonly used for continuous monitoring in cloud environments?

Answer: AWS CloudWatch

AWS CloudWatch is a monitoring and observability service built for AWS resources and applications running on AWS. It collects and tracks metrics, collects log files, and sets alarms, providing comprehensive insights into the health and performance of cloud environments. It's an essential tool for continuous monitoring and operational visibility within AWS.

What is a benefit of blue/green deployment?

Answer: It ensures zero downtime during deployment

Blue/green deployment involves running two identical production environments: one (blue) with the current version and another (green) with the new version. Traffic is gradually shifted from the blue to the green environment. This strategy allows for immediate rollback to the blue environment if issues arise, ensuring continuous availability and zero downtime for users during the deployment process.

What is the role of integration testing in CI/CD?

Answer: To verify modules work together as expected

Integration testing in CI/CD is a crucial phase that verifies how different software modules or components interact and function together. Its primary purpose is to expose defects in the interfaces and interactions between these integrated parts. This ensures that the system works cohesively as a whole, rather than just individual units.

Which metric is used to track system reliability in monitoring?

Answer: Uptime

Uptime is a direct and fundamental metric used to track system reliability and availability. It measures the percentage of time a system or service is operational and accessible to users without interruption. High uptime indicates a stable and reliable system, which is critical for business continuity and user satisfaction.

What is rollback in deployment strategies?

Answer: Reverting to a previous version due to errors

Rollback is a deployment strategy that allows an application or system to be quickly reverted to a previously stable and functional version. This action is typically performed when a new deployment introduces critical errors, performance degradation, or unexpected issues. It serves as a safety mechanism to minimize downtime and mitigate negative impacts on users.

Which practice ensures code works in different environments?

Answer: Environment parity

Environment parity is the practice of maintaining consistent configurations and settings across all development, testing, staging, and production environments. This ensures that code behaves predictably as it moves through the deployment pipeline, minimizing the likelihood of 'works on my machine' issues or unexpected bugs appearing in later stages due to environmental differences.