Cloud Engineer Quality Control & Assurance 5 — Questions and Answers
Question 1: Which practice ensures that secrets and credentials are never hardcoded in application source code, supporting cloud security QA?
- Storing secrets in environment variable comments
- Using a secrets manager such as AWS Secrets Manager or HashiCorp Vault (Correct answer)
- Encoding secrets in Base64 and committing to the repository
- Rotating secrets only after a breach is detected
Correct answer: Using a secrets manager such as AWS Secrets Manager or HashiCorp Vault
Secrets managers store, rotate, and audit access to credentials at runtime, keeping them out of source code entirely.
Question 2: A cloud QA engineer wants to validate Terraform changes without applying them. Which command provides a plan for review?
- terraform validate
- terraform plan (Correct answer)
- terraform apply --dry-run
- terraform fmt
Correct answer: terraform plan
`terraform plan` generates an execution plan showing what changes Terraform will make without modifying any resources.
Question 3: What is the purpose of 'observability' as a quality assurance principle in cloud systems?
- To reduce the number of monitoring agents running on servers
- To understand internal system state from external outputs like logs, metrics, and traces (Correct answer)
- To enforce access control policies across cloud services
- To automate rollback when an error rate threshold is exceeded
Correct answer: To understand internal system state from external outputs like logs, metrics, and traces
Observability enables engineers to diagnose and understand system behavior in production using the three pillars: logs, metrics, and traces.
Question 4: Which CI/CD quality practice involves running security vulnerability scans on container images before deployment?
- Blue/green image validation
- Container image scanning with tools like Trivy or Snyk (Correct answer)
- Smoke testing container registry endpoints
- Running OWASP ZAP on the container build host
Correct answer: Container image scanning with tools like Trivy or Snyk
Container image scanning tools like Trivy detect known CVEs in OS packages and application dependencies before images reach production.
Question 5: A cloud team implements automated rollback when a deployment causes error rate to exceed 5%. What type of quality control does this represent?
- Proactive compliance auditing
- Automated remediation based on observability signals (Correct answer)
- Manual change management review
- Static code analysis enforcement
Correct answer: Automated remediation based on observability signals
Automated rollback triggered by error rate thresholds is a self-healing quality control mechanism driven by real-time observability data.
Question 6: What is 'test environment parity' and why is it important in cloud QA?
- Ensuring all developers run the same IDE version
- Keeping staging and production environments as identical as possible to reduce environment-specific bugs (Correct answer)
- Synchronizing test case counts across teams
- Matching cloud provider billing tiers between environments
Correct answer: Keeping staging and production environments as identical as possible to reduce environment-specific bugs
Environment parity minimizes the risk of bugs that only appear in production by making staging configurations mirror production as closely as possible.
Question 7: Which SRE concept defines the maximum acceptable time that a system can be unavailable per year and directly informs QA objectives?
- Recovery Point Objective (RPO)
- Service Level Objective (SLO) (Correct answer)
- Mean Time Between Failures (MTBF)
- Recovery Time Objective (RTO)
Correct answer: Service Level Objective (SLO)
SLOs define specific measurable targets for reliability (e.g., 99.9% uptime) that QA processes and error budgets are designed to protect.
Which practice ensures that secrets and credentials are never hardcoded in application source code, supporting cloud security QA?