Cloud Engineer Quality Control & Assurance 4 — Questions and Answers
Question 1: Which testing approach verifies that a new code change has not broken existing functionality?
- Exploratory testing
- Regression testing (Correct answer)
- Alpha testing
- Penetration testing
Correct answer: Regression testing
Regression testing re-executes existing test suites after changes to confirm that previously working features remain intact.
Question 2: A cloud engineer is implementing SLOs for a service. What does an 'error budget' represent?
- The allocated cloud spend before alerts trigger
- The allowed amount of downtime or errors before the SLO is breached (Correct answer)
- The number of failed deployments permitted per sprint
- The maximum number of open bug tickets at any time
Correct answer: The allowed amount of downtime or errors before the SLO is breached
An error budget is the acceptable margin of failure derived from the SLO, giving teams flexibility to ship while maintaining reliability.
Question 3: What is 'mutation testing' used for in software quality assurance?
- Testing how the app behaves when cloud regions fail
- Evaluating the effectiveness of existing test suites by introducing small code faults (Correct answer)
- Checking if containerized services handle config mutations gracefully
- Verifying that data migrations transform records correctly
Correct answer: Evaluating the effectiveness of existing test suites by introducing small code faults
Mutation testing introduces deliberate code faults ('mutants') to verify that the test suite catches and fails on them.
Question 4: Which Kubernetes feature can enforce quality policies by blocking non-compliant pod configurations at admission time?
- Horizontal Pod Autoscaler
- Admission webhooks / OPA Gatekeeper (Correct answer)
- Persistent Volume Claims
- Network Policies
Correct answer: Admission webhooks / OPA Gatekeeper
Admission webhooks and tools like OPA Gatekeeper intercept API requests and reject resources that violate defined policies.
Question 5: In cloud infrastructure testing, what does 'infrastructure as code (IaC) testing' typically include?
- Manual review of Terraform plans only
- Linting, unit tests, and integration tests for Terraform/CloudFormation templates (Correct answer)
- Running the infrastructure in production and monitoring for errors
- Comparing infrastructure costs across providers
Correct answer: Linting, unit tests, and integration tests for Terraform/CloudFormation templates
IaC testing combines linting (tflint), policy checks (Checkov), and test frameworks (Terratest) to validate templates before deployment.
Question 6: A team wants to ensure their cloud APIs meet performance SLAs under stress. Which tool is purpose-built for API performance testing?
- Prometheus
- k6 (Correct answer)
- Terraform
- Vault
Correct answer: k6
k6 is a developer-centric load testing tool designed to script and run performance tests against APIs and cloud services.
Question 7: What is the main benefit of using 'synthetic monitoring' for cloud application quality assurance?
- It reduces infrastructure costs by simulating traffic instead of handling real users
- It proactively detects failures by running scripted transactions against production continuously (Correct answer)
- It replaces the need for log aggregation tools
- It tests code changes before they are deployed to production
Correct answer: It proactively detects failures by running scripted transactions against production continuously
Synthetic monitoring runs scripted user journeys against production endpoints on a schedule to detect outages before real users notice.
Which testing approach verifies that a new code change has not broken existing functionality?