Test your knowledge of CI/CD and DevOps for QA. 10 questions covering pipelines, Docker, Kubernetes, deployment strategies, monitoring, and DevOps metrics.
Quick Answer
Module 9 Assessment covers essential QA skills — after this lesson you can demonstrate comprehensive understanding of CI/CD concepts and pipeline design.
— Yuri Kan, Senior QA Lead
What You Will Learn
Demonstrate comprehensive understanding of CI/CD concepts and pipeline design
Apply Docker, Kubernetes, and IaC knowledge to testing scenarios
Evaluate deployment strategies, monitoring approaches, and DevOps metrics
Table of Contents
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.
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
Knowledge Check
1. What is the primary difference between Continuous Delivery and Continuous Deployment?
Continuous Delivery ensures code is always deployable but requires manual approval. Continuous Deployment automates the full path to production — every change that passes the pipeline goes live automatically.
2. In a Jenkins pipeline, what is the purpose of the 'post { always }' block?
The post { always } block runs after the pipeline regardless of success or failure. This is critical for QA — test reports and artifacts must be archived even (especially) when tests fail.
3. Which GitHub Actions feature is most useful for cross-browser testing?
Matrix strategy creates multiple job runs from variable combinations (e.g., 3 browsers x 2 OS = 6 parallel jobs). With fail-fast: false, all combinations run even if one fails.
4. What does 'docker compose down -v' do that 'docker compose down' does not?
The -v flag removes named volumes. Without it, test data in volumes persists between runs, potentially causing test pollution. Always use -v for test environments to ensure clean state.
5. In Kubernetes, how should QA tests connect to an application?
Kubernetes Services provide stable endpoints (DNS names and IP addresses) that route to healthy pods. Pod IPs change when pods restart. Tests must connect via Services for reliability.
6. What is the main risk of using production data in test environments?
Using real production data in non-production environments violates privacy laws and risks exposing personal information. Test environments should use synthetic or properly anonymized data.
7. In a canary deployment, what should trigger an automatic rollback?
Automatic rollback should trigger when monitored metrics cross predefined thresholds (e.g., error rate > 1%, P95 latency > 500ms). These criteria must be defined before deployment, not during an incident.
8. What are the three pillars of observability?
The three pillars are Logs (what happened), Metrics (how the system is performing over time), and Traces (how a request flows through services). Together they provide comprehensive system visibility.
9. How does test sharding reduce execution time?
Sharding divides tests among N machines running in parallel. A 60-minute suite on 4 machines takes approximately 15 minutes. The speedup is nearly linear when shards are balanced by duration.
10. Which DORA metric is most directly influenced by QA?
While QA influences all DORA metrics, Change Failure Rate is the most direct. Better automated testing, quality gates, and pre-deployment validation directly reduce the percentage of deployments that cause production issues.
Frequently Asked Questions
What is module 9 assessment?
Module 9 Assessment is a key concept in CI/CD and DevOps for QA. This lesson teaches you to demonstrate comprehensive understanding of CI/CD concepts and pipeline design, providing practical skills you can apply immediately in your testing work.
How do I apply module 9 assessment in real projects?
Start by practicing the core techniques covered in this lesson. Specifically, you should apply Docker, Kubernetes, and IaC knowledge to testing scenarios. Apply these skills in your current project to see immediate results.
Why is module 9 assessment important for QA engineers?
Module 9 Assessment is a core skill that employers look for in QA professionals. It directly impacts test coverage, defect detection, and team efficiency. Mastering it strengthens your CI/CD and DevOps for QA capabilities and makes you more effective at delivering quality software.
What should I know before learning module 9 assessment?
You should have a basic understanding of software testing fundamentals. Familiarity with cicd quiz will help, but the lesson includes review sections for key prerequisites.
How does module 9 assessment help my QA career?
Knowledge of module 9 assessment is frequently listed in QA job descriptions and interview questions. It demonstrates expertise in cicd quiz, module 9 exam and shows you can contribute to quality assurance at a professional level. Senior roles especially value this competency.