QA in CI/CD Pipeline CT-QDO Practice Questions (Page 2)

Questions 6–10

1. 6application · medium

   A deployment script uses a blue-green deployment strategy. After deploying the new version to the 'green' environment, the team wants to validate it before switching traffic. What is the most appropriate validation step?

   • ASwitch traffic to the green environment immediately and monitor for errors.
   • BRun a smoke test against the green environment's URL to verify the new version is functional.
   • CRun the full regression suite against the blue environment before switching.
   • DSkip validation and rely on the CI tests that ran on the build artifact.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   Which testing strategy is essential for fully automated deployments to production?

   • APerformance testing only on production
   • BManual exploratory testing before every release
   • CSecurity testing only after deployment
   • DComprehensive automated regression tests
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   In a CI pipeline, what typically triggers the execution of automated tests?

   • AThe completion of a user acceptance test cycle
   • BA scheduled time, such as every night at midnight
   • CA code commit or merge to the shared repository
   • DA manual request from the test manager
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A QA team needs to run integration tests in CI that require a specific database schema and seed data. The database is currently provisioned manually by a DBA, causing delays and inconsistent test results. Which approach provides the most reliable and fast test environment?

   • AAsk the DBA to create a new database instance for each CI run and notify the team when it is ready.
   • BRun integration tests against the production database with read-only access.
   • CCreate a Docker container with the database, schema, and seed data as part of the CI pipeline setup stage.
   • DUse a shared persistent database that the DBA updates weekly with the latest schema.
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   A team is using feature toggles to test a new feature in production with a small percentage of users. They have monitoring in place, but they are unsure how to distinguish between issues caused by the new feature and issues caused by other changes. What is the most effective practice?

   • AMonitor overall system metrics and assume any anomaly is caused by the new feature.
   • BDisable all other changes during the toggle test to isolate the new feature.
   • CRely on user feedback to identify issues with the new feature.
   • DCompare key metrics and error rates between the toggle-on and toggle-off user groups.
   Reveal Solution Discussion Select an answer first