Module 9: CI/CD and DevOps for QA — Final Assessment
This assessment covers all 19 lessons of Module 9. You need to score at least 70% (7 out of 10 correct) to pass.
The questions test your understanding of:
- CI/CD pipeline concepts and tools (Jenkins, GitHub Actions, GitLab CI)
- Docker and container-based testing
- Kubernetes for QA
- Environment management and Infrastructure as Code
- Deployment strategies (blue-green, canary)
- Monitoring and observability
- Chaos engineering and production testing
- Test orchestration and DevOps metrics
Take your time — there is no time limit. Review each question carefully before selecting your answer.
Practical Assessment: Design a CI/CD Pipeline
Beyond the quiz, demonstrate your Module 9 knowledge by completing this practical exercise:
Scenario
You are the QA Lead for a fintech application with:
- Microservices architecture (5 services)
- React frontend, Node.js APIs, PostgreSQL, Redis, RabbitMQ
- 150 E2E tests (currently taking 90 minutes on a single machine)
- Deployed on Kubernetes (AWS EKS)
- Current deployment: manual, once per sprint (every 2 weeks)
- Current testing: manual smoke tests before each release
Your goal: Design a complete CI/CD pipeline with automated testing, monitoring, and deployment strategy.
Deliverables
Pipeline Architecture: Draw or describe the complete CI/CD pipeline from code commit to production deployment, including all testing stages.
Test Strategy: How tests are organized, parallelized, and which tests run at which stage.
Environment Strategy: How many environments, what type (ephemeral, shared), and how test data is managed.
Deployment Strategy: Which deployment strategy (blue-green, canary, rolling) and why.
Monitoring Plan: What metrics to monitor, what dashboards to create, what alerts to configure.
DORA Metrics Targets: Set realistic targets for all four DORA metrics for the first 6 months.
Sample Solution
1. Pipeline Architecture
PR Created:
→ Lint + Type Check (2 min)
→ Unit Tests with coverage (5 min)
→ Affected E2E Tests (10 min, test impact analysis)
→ PR environment created (Kubernetes namespace)
→ Full E2E on PR environment (15 min, 4 shards)
→ PR Review + Manual QA on PR environment
Merge to Main:
→ Full Unit Tests (5 min)
→ Integration Tests with Docker Compose (10 min)
→ Full E2E on Staging (15 min, 6 shards)
→ Performance Tests (10 min)
→ Security Scan (5 min)
→ Quality Gate (all criteria checked)
→ Canary Deployment (1% → 10% → 50% → 100%)
→ Production Smoke Tests
→ Monitoring (24-hour observation)
2. Test Strategy
- Unit Tests: 500+ tests, Jest, run on every commit, 5 min
- Integration Tests: 50 tests, Supertest + Docker Compose (PostgreSQL, Redis, RabbitMQ), 10 min
- E2E Tests: 150 tests, Playwright, sharded across 6 runners, 15 min total
- Performance Tests: k6, critical API endpoints, run on merge to main
- PR Pipeline: Only affected tests + smoke suite (20 min total)
- Full Pipeline: All tests (30 min total with parallelization)
3. Environment Strategy
- Local: Docker Compose (all 5 services + dependencies)
- CI: Docker Compose for integration, Kubernetes for E2E
- PR Preview: Ephemeral Kubernetes namespace per PR
- Staging: Shared, deployed on merge to main
- Production: AWS EKS, multi-AZ
Test data: Synthetic seed data, no production data, each test creates/cleans its own data.
4. Deployment Strategy
Canary Deployment because:
- Fintech = high-risk (financial transactions)
- Need gradual rollout with real-time monitoring
- Automatic rollback if payment success rate drops
Phases: 1% (30 min) → 10% (2 hours) → 50% (4 hours) → 100% Rollback criteria: Error rate > 0.5%, payment failure > 0.1%, P95 > 300ms
5. Monitoring Plan
Dashboards:
- Service health (per microservice): error rate, latency, throughput
- Business metrics: payment success, transaction volume, conversion
- Infrastructure: CPU, memory, pod count, DB connections
- Pipeline: test pass rate, execution time, deployment frequency
Alerts:
- Error rate > 1% (critical)
- Payment failure rate > 0.1% (critical)
- P95 latency > 500ms (warning)
- Pod restarts > 0 (warning)
- Pipeline failure (notification)
6. DORA Metrics Targets (6 months)
| Metric | Current | 3-Month Target | 6-Month Target |
|---|---|---|---|
| Deployment Frequency | Biweekly | Weekly | Daily |
| Lead Time | 14 days | 3 days | 1 day |
| Change Failure Rate | Unknown (~30%?) | 20% | 10% |
| MTTR | Unknown | 2 hours | 30 minutes |
What Comes Next
Congratulations on completing Module 9! You now have a solid understanding of how CI/CD and DevOps practices integrate with QA. These skills are increasingly essential for modern QA engineers and will set you apart in your career.
Recommended next modules:
- Module 10: Networking and Protocols — understand the infrastructure your pipelines deploy to
- Module 12: QA Leadership — apply these DevOps concepts at the team and organizational level