I85PREP
⌘ K
Continuous Testing Foundation study materials
Continuous Testing Foundation study resources

Continuous Testing Foundation practice questions

One question at a time. Build your Continuous Testing Foundation understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1DevOps Continuous Testing Concepts, Terminology, and Benefits

In DevOps continuous testing, what does the term 'shift left' most precisely describe?

  1. Running all performance tests only in production after release
  2. Delegating all testing responsibility to a separate QA department
  3. Moving testing and quality activities earlier into the delivery lifecycle Correct answer.
  4. Replacing automated tests with manual exploratory testing

Explanation

Shift left means performing testing and quality-assurance activities as early as possible, such as during requirements and coding, so defects are found when they are cheapest to fix. It is a principle about timing and feedback, not about removing automation or centralizing testers.

Question 2DevOps Continuous Testing Concepts, Terminology, and Benefits

Which statement best captures the primary business benefit of continuous testing in a DevOps pipeline?

  1. It provides fast, continuous feedback on release risk so teams can decide to deploy with confidence Correct answer.
  2. It eliminates the need for regression testing once automation coverage is high
  3. It removes the requirement for any manual approval before release
  4. It guarantees zero production defects after every deployment

Explanation

Continuous testing supplies rapid, ongoing feedback about quality and risk throughout the pipeline, enabling informed go/no-go decisions. It reduces risk and shortens feedback loops but cannot guarantee zero defects or make regression testing unnecessary.

Question 3DevOps Continuous Testing Concepts, Terminology, and Benefits

A team runs an automated test suite on every commit and blocks the merge when tests fail. Which continuous testing concept does this behavior illustrate?

  1. Exploratory testing charters
  2. Service virtualization of third parties
  3. Quality gates in the continuous integration pipeline Correct answer.
  4. Test data masking for production copies

Explanation

A quality gate is a pipeline checkpoint that evaluates test results and halts progression, such as a merge, when criteria are not met. Running tests per commit and blocking the merge is the classic continuous integration quality gate.

Question 4DevOps Continuous Testing Concepts, Terminology, and Benefits

What is the key distinction between continuous testing and traditional testing performed at the end of a project?

  1. Traditional testing always produces fewer defects than continuous testing
  2. Continuous testing uses only manual testers while traditional testing uses automation
  3. Continuous testing is interwoven throughout delivery and provides ongoing feedback, whereas traditional testing is a late, discrete phase Correct answer.
  4. Continuous testing ignores functional requirements and focuses only on performance

Explanation

Continuous testing is embedded across the delivery lifecycle, giving feedback at every stage, whereas traditional end-of-project testing occurs as a separate late phase. This timing difference is the defining distinction, not the tools or staffing used.

Question 5DevOps Continuous Testing Concepts, Terminology, and Benefits

In continuous testing terminology, what is a 'test environment' expected to provide?

  1. A copy of the production database shared by all teams without controls
  2. A single developer laptop used for all test execution
  3. A document describing test cases in natural language
  4. A stable, reproducible configuration in which tests execute with controlled dependencies and data Correct answer.

Explanation

A test environment is the configured infrastructure, dependencies, and data that allow tests to run reliably and repeatably. Stability and reproducibility are essential so results reflect the code rather than environmental drift.

Question 6DevOps Continuous Testing Concepts, Terminology, and Benefits

Which practice most directly supports the continuous testing goal of fast feedback on code changes?

  1. Deferring all testing to a dedicated hardening sprint
  2. Automating a fast, prioritized smoke and unit test suite that runs on every commit Correct answer.
  3. Running the full multi-hour regression suite once per quarter
  4. Manually reviewing each commit before any test runs

Explanation

Fast feedback requires automated tests that run quickly and frequently, typically a prioritized smoke and unit layer triggered on each commit. Deferring or gating tests behind slow manual steps lengthens the feedback loop.

Question 7DevOps Continuous Testing Concepts, Terminology, and Benefits

What does the 'test pyramid' advise about the distribution of automated tests?

  1. Many fast unit tests at the base, fewer service or integration tests, and the fewest slow end-to-end tests at the top Correct answer.
  2. Most tests should be end-to-end UI tests, with few unit tests
  3. Equal numbers of unit, integration, and UI tests across all layers
  4. Only end-to-end tests should be automated

Explanation

The test pyramid recommends a broad base of fast, cheap unit tests, a smaller middle layer of integration or service tests, and a thin top layer of slow end-to-end tests. This balance keeps feedback fast and maintenance costs manageable.

Question 8DevOps Continuous Testing Concepts, Terminology, and Benefits

Which metric is most directly associated with the continuous testing feedback loop?

  1. The number of meetings held per sprint
  2. The total number of testers on the team
  3. The count of documents produced per release
  4. The time from committing code to receiving automated test results Correct answer.

Explanation

Feedback-loop time, often called lead time for test feedback, measures how quickly a change receives automated test results. Shorter times indicate a healthier continuous testing process.

Question 9DevOps Continuous Testing Concepts, Terminology, and Benefits

A pipeline runs unit tests on commit, integration tests on merge to main, and full end-to-end tests before production release. Which continuous testing principle does this staged execution best illustrate?

  1. Test orchestration across pipeline stages with increasing scope and cost Correct answer.
  2. Manual regression testing before each commit
  3. Test data masking for regulatory compliance
  4. Exploratory testing by business analysts

Explanation

Staged execution places fast, narrow tests early and slower, broader tests later, which is test orchestration aligned with the pipeline. It optimizes feedback speed while reserving expensive suites for later gates.

Question 10DevOps Continuous Testing Concepts, Terminology, and Benefits

Why is service virtualization valuable in a continuous testing pipeline?

  1. It simulates dependent systems that are unavailable, costly, or hard to control so tests can run reliably Correct answer.
  2. It automatically fixes defects found by the tests
  3. It replaces the need to write any automated tests
  4. It permanently removes third-party systems from the architecture

Explanation

Service virtualization provides controllable stand-ins for dependencies such as third-party APIs or mainframes, allowing tests to run consistently even when those systems are inaccessible or expensive. It improves reliability and test coverage of integration paths.

Question 11DevOps Continuous Testing Concepts, Terminology, and Benefits

A team wants to test a new feature against realistic data without exposing real customer information. Which continuous testing practice applies?

  1. Generating or masking synthetic test data that preserves realistic structure Correct answer.
  2. Using production data unmasked to maximize realism
  3. Copying the production database into every developer environment
  4. Skipping data-dependent tests entirely

Explanation

Synthetic or masked test data provides realistic structure and behavior while protecting privacy and complying with regulations. This lets data-dependent tests run continuously without exposing personal information.

Question 12DevOps Continuous Testing Concepts, Terminology, and Benefits

What is the main purpose of a 'test oracle' in automated testing?

  1. To store test environments for reuse
  2. To provide the mechanism for determining whether a test's actual result is correct Correct answer.
  3. To schedule when tests execute in the pipeline
  4. To generate user stories from requirements

Explanation

A test oracle is the source of expected outcomes used to judge whether an observed result is correct, such as assertions or reference outputs. Without a reliable oracle, a test cannot decide pass or fail.

Question 13DevOps Continuous Testing Concepts, Terminology, and Benefits

A team's end-to-end suite is slow and flaky, delaying every release. Which continuous testing adjustment is most appropriate?

  1. Delete all end-to-end tests and rely on manual checks
  2. Run the end-to-end suite less often while ignoring failures
  3. Rebalance toward more unit and integration tests, keeping a small, stable set of critical end-to-end scenarios Correct answer.
  4. Increase the number of end-to-end tests to improve coverage

Explanation

Applying the test pyramid, the team should push coverage down to faster, more stable unit and integration layers while retaining a small set of high-value end-to-end journeys. This reduces flakiness and speeds feedback without losing critical coverage.

Question 14DevOps Continuous Testing Concepts, Terminology, and Benefits

What does 'test flakiness' mean in the context of continuous testing?

  1. A test written in a non-standard programming language
  2. A test that produces inconsistent pass and fail results without code changes Correct answer.
  3. A test that always fails due to a known product defect
  4. A test that runs faster than expected

Explanation

A flaky test yields different outcomes across runs of the same code, usually due to timing, environment, or data issues. Flakiness erodes trust in the pipeline because failures no longer reliably signal defects.

Question 15DevOps Continuous Testing Concepts, Terminology, and Benefits

How does continuous testing typically change the role of a tester on a DevOps team?

  1. The tester becomes a quality advocate who builds automation, defines test strategy, and collaborates across the delivery team Correct answer.
  2. The tester only executes manual scripts at release time
  3. The tester focuses solely on writing documentation
  4. The tester is replaced entirely by the deployment pipeline

Explanation

Continuous testing shifts testers toward building automation, shaping strategy, and embedding quality across the team rather than executing late manual scripts. Quality becomes a shared responsibility supported by specialist skills.

Question 16DevOps Continuous Testing Concepts, Terminology, and Benefits

In a continuous delivery pipeline, why should automated tests be treated as production code?

  1. Because they must be written by operations staff only
  2. Because they need version control, review, maintenance, and refactoring to stay reliable Correct answer.
  3. Because they must run in production environments
  4. Because they should never be changed after creation

Explanation

Test code is a long-lived asset that must be versioned, reviewed, and maintained, or it becomes brittle and untrustworthy. Treating tests as production code keeps the suite reliable and the feedback meaningful.

Question 17DevOps Continuous Testing Concepts, Terminology, and Benefits

A team measures that defects found in production have dropped but mean time to detect them has risen. What does this combination suggest about their continuous testing setup?

  1. They may have strong prevention but weak observability and monitoring feedback in production Correct answer.
  2. They have eliminated the need for monitoring
  3. Their tests are fast and comprehensive across the pipeline
  4. They should remove automated tests to improve detection

Explanation

Fewer production defects suggests effective earlier testing, but slower detection points to gaps in production monitoring and observability feedback loops. Continuous testing extends into production feedback, so detection speed matters.

Question 18DevOps Continuous Testing Concepts, Terminology, and Benefits

Which statement best describes the relationship between continuous integration and continuous testing?

  1. Continuous integration triggers automated tests on each integration, making continuous testing practical Correct answer.
  2. Continuous integration and continuous testing are unrelated practices
  3. Continuous testing only occurs after continuous delivery is fully achieved
  4. Continuous testing replaces continuous integration entirely

Explanation

Continuous integration provides the frequent integration events that trigger automated tests, giving continuous testing its cadence. The practices reinforce each other: CI supplies the trigger, and continuous testing supplies the quality feedback.

Question 19DevOps Continuous Testing Concepts, Terminology, and Benefits

A regulated team must prove that every release passed specific security and compliance checks. Which continuous testing capability best satisfies this need?

  1. Automated compliance and security test gates that produce auditable evidence per release Correct answer.
  2. Relying on developers' verbal confirmation of compliance
  3. Ad hoc manual spot checks with no records
  4. Disabling security tests to speed up delivery

Explanation

Automated gates that run mandated security and compliance checks and retain results create auditable evidence tied to each release. This supports governance while preserving the speed of continuous delivery.

Question 20DevOps Continuous Testing Concepts, Terminology, and Benefits

What does 'test automation ROI' most appropriately consider in a continuous testing program?

  1. Only the initial cost of purchasing a test tool
  2. The balance of automation creation and maintenance costs against the value of faster, repeated feedback and defect prevention Correct answer.
  3. The salary of the most senior tester
  4. The number of test cases written regardless of execution frequency

Explanation

Automation ROI weighs ongoing creation and maintenance effort against benefits such as repeated execution, faster feedback, and earlier defect detection. A test that runs rarely may cost more than it returns.

Question 21DevOps Continuous Testing Concepts, Terminology, and Benefits

Which scenario best demonstrates continuous testing providing value beyond defect detection?

  1. Tests are written but never executed in the pipeline
  2. Test failures are routinely ignored by the team
  3. Tests run only to satisfy an audit checklist
  4. Test results feed deployment decisions and give the team confidence to release more frequently Correct answer.

Explanation

Continuous testing adds value when results inform release decisions and enable faster, safer delivery cadence, not merely when they detect defects. Feeding deployment decisions turns test output into actionable risk information.

Question 22DevOps Continuous Testing Concepts, Terminology, and Benefits

A team argues that because they practice continuous testing, they can reduce exploratory testing. How should this be evaluated?

  1. Incorrect, because automated checks confirm known expectations while exploratory testing discovers unknown risks and new scenarios Correct answer.
  2. Correct, because automation covers all realistic user behavior
  3. Incorrect, because exploratory testing should replace automated regression
  4. Correct, because exploratory testing is obsolete in DevOps

Explanation

Automated tests verify anticipated behaviors, whereas exploratory testing uncovers unknown risks, edge cases, and emergent issues. Continuous testing benefits from combining both rather than substituting one for the other.

Question 23DevOps Continuous Testing Concepts, Terminology, and Benefits

Which characteristic most distinguishes a continuous testing suite from a large collection of automated scripts?

  1. The absence of any test maintenance
  2. The total number of scripts in the repository
  3. Integrated execution within the delivery pipeline with fast, trustworthy feedback that drives decisions Correct answer.
  4. The use of a single programming language across all scripts

Explanation

Continuous testing is defined by integration into the delivery pipeline and by producing fast, trustworthy feedback that informs decisions. A large script collection outside the pipeline does not deliver that continuous value.

Question 24DevOps Continuous Testing Concepts, Terminology, and Benefits

A pipeline gate fails intermittently on the same commit, sometimes passing and sometimes failing with no code change. What is the most rigorous continuous testing response?

  1. Rerun the pipeline until it passes and accept the result
  2. Increase the gate threshold so occasional failures are ignored
  3. Delete the gate permanently to keep delivery moving
  4. Quarantine the flaky test, investigate root cause such as timing or shared state, and fix it before restoring the gate Correct answer.

Explanation

Flaky gates undermine trust in feedback, so the disciplined response is to isolate the test, diagnose causes like timing, ordering, or shared state, and repair it. Masking or deleting the gate hides risk rather than resolving it.

Question 25DevOps Continuous Testing Concepts, Terminology, and Benefits

In continuous testing, why is defect 'cost of delay' a central argument for early testing?

  1. Cost of delay applies only to infrastructure spending
  2. Delaying tests always reduces the number of defects
  3. The later a defect is detected, the more rework, coordination, and risk it typically incurs Correct answer.
  4. Defects cost the same to fix regardless of when they are found

Explanation

The cost-of-delay argument holds that defects found late require more rework, cross-team coordination, and carry greater release risk. Early detection through continuous testing therefore lowers total cost and risk.

Question 26DevOps Continuous Testing and Culture

In DevOps continuous testing, what does shifting testing 'left' primarily mean?

  1. Running tests earlier in the delivery pipeline, close to code commit Correct answer.
  2. Assigning testing exclusively to a separate QA department
  3. Moving all testing to the production environment after release
  4. Replacing automated tests with manual exploratory testing

Explanation

Shift-left means integrating testing activities as early as possible in the software lifecycle, so defects are found close to the moment they are introduced. This reduces the cost of rework and shortens feedback loops for developers.

Question 27DevOps Continuous Testing and Culture

Which practice best describes a 'test pyramid' in a continuous delivery context?

  1. Many end-to-end UI tests supported by a few unit tests
  2. A single comprehensive test suite run once per quarter
  3. Only manual regression tests executed before each release
  4. Many fast unit tests, fewer service tests, and a small number of end-to-end UI tests Correct answer.

Explanation

The test pyramid recommends a broad base of fast, isolated unit tests, a smaller middle layer of integration or service tests, and a thin top layer of slow end-to-end tests. This balance keeps feedback fast and maintenance costs low.

Question 28DevOps Continuous Testing and Culture

A team wants fast feedback on every commit without waiting for a full environment. Which testing layer should they prioritize in the pipeline's first stage?

  1. Unit tests that run in seconds with mocked dependencies Correct answer.
  2. Performance load tests simulating peak production traffic
  3. Manual user acceptance testing by business stakeholders
  4. Full end-to-end tests against a staging environment

Explanation

The earliest pipeline stage should provide the fastest signal, and unit tests with mocked dependencies run in seconds and isolate logic defects. Slower, environment-dependent tests belong in later stages where their cost is justified.

Question 29DevOps Continuous Testing and Culture

What is the primary purpose of a build pipeline 'quality gate'?

  1. To document manual test cases for auditors
  2. To block progression when defined quality criteria are not met Correct answer.
  3. To automatically approve every build regardless of test results
  4. To measure developer productivity by commit count

Explanation

A quality gate enforces objective criteria, such as passing tests or coverage thresholds, before an artifact moves to the next stage. It makes quality decisions automatic and consistent rather than discretionary.

Question 30DevOps Continuous Testing and Culture

Which cultural change is most essential for continuous testing to succeed?

  1. Keeping test code ownership with a single central team
  2. Making quality a shared team responsibility rather than a gatekeeper role Correct answer.
  3. Measuring testers by the number of defects they log
  4. Requiring testers to sign off on every code change manually

Explanation

Continuous testing depends on cross-functional teams where developers, testers, and operations share accountability for quality. Siloed gatekeeping creates bottlenecks and slows the feedback loop that DevOps relies on.

Question 31DevOps Continuous Testing and Culture

A test suite passes locally but fails intermittently in the CI pipeline. What is the most appropriate first step?

  1. Move the tests to a nightly run and ignore them
  2. Increase the retry count until the failures disappear
  3. Investigate environmental and timing differences causing non-determinism Correct answer.
  4. Disable the failing tests permanently to keep the pipeline green

Explanation

Flaky tests usually stem from non-determinism such as timing, shared state, or environment differences, so the root cause must be diagnosed. Hiding the failure erodes trust in the pipeline signal.

Question 32DevOps Continuous Testing and Culture

Which metric best indicates how quickly a team receives feedback from its automated tests?

  1. Total number of test cases in the repository
  2. Number of testers assigned to the project
  3. Mean pipeline execution time from commit to test result Correct answer.
  4. Lines of test code written per sprint

Explanation

Feedback speed is measured by the elapsed time between a code change and the resulting test outcome, often called the commit-to-feedback time. Test counts or staffing do not reveal how fast the team learns about defects.

Question 33DevOps Continuous Testing and Culture

What role does test data management play in continuous testing?

  1. Guaranteeing tests always use live production customer records
  2. Providing consistent, isolated data so automated tests are repeatable Correct answer.
  3. Eliminating the need for test environments
  4. Replacing assertions with data comparisons

Explanation

Reliable continuous testing requires test data that is provisioned consistently and isolated per run so results are repeatable. Using uncontrolled or production data introduces non-determinism and privacy risk.

Question 34DevOps Continuous Testing and Culture

Which approach best supports testing in production without harming users?

  1. Canary releases with automated monitoring and rollback Correct answer.
  2. Relying solely on pre-release manual sign-off
  3. Deploying directly to all users and waiting for bug reports
  4. Removing automated tests once code reaches production

Explanation

Canary releases expose a small subset of traffic to the new version while automated monitoring watches key signals, enabling rapid rollback if problems appear. This is a controlled form of shift-right validation.

Question 35DevOps Continuous Testing and Culture

A team adopts behavior-driven development (BDD). What is the main benefit for continuous testing?

  1. Automatic generation of performance load profiles
  2. Guaranteed elimination of all production defects
  3. Faster hardware provisioning for test environments
  4. Executable specifications that align business and technical understanding Correct answer.

Explanation

BDD expresses requirements as executable scenarios in shared business language, so tests document intended behavior and reduce misunderstanding between stakeholders and developers. These scenarios can be automated within the pipeline.

Question 36DevOps Continuous Testing and Culture

What does a 'test automation strategy' primarily determine?

  1. The programming language used for production code only
  2. The color scheme of the test dashboard
  3. Which tests to automate, at which layers, and how they fit the pipeline Correct answer.
  4. The number of developers to hire

Explanation

An automation strategy defines scope, prioritization, and layering of automated tests so they deliver maximum feedback for the effort invested. It connects test design decisions to pipeline stages.

Question 37DevOps Continuous Testing and Culture

A team's end-to-end suite takes four hours and blocks every merge. What is the best improvement?

  1. Split fast checks into the merge gate and run the full suite asynchronously Correct answer.
  2. Increase the merge gate timeout to four hours
  3. Require developers to run the suite manually before merging
  4. Remove all end-to-end tests from the pipeline entirely

Explanation

Keeping a fast, focused gate preserves rapid feedback while the comprehensive suite still runs to catch integration issues. This balances speed with coverage.

Question 38DevOps Continuous Testing and Culture

Which statement reflects a healthy 'quality is built in' mindset?

  1. Developers write and maintain automated tests alongside production code Correct answer.
  2. Test coverage is reviewed once a year
  3. Defects are documented but deferred to a future release
  4. Testing is performed only by a dedicated team at the end of a release

Explanation

Building quality in means developers take responsibility for automated tests as part of delivering a feature, preventing defects rather than detecting them late. This shortens feedback and reduces rework.

Question 39DevOps Continuous Testing and Culture

What is the purpose of contract testing in a microservices pipeline?

  1. Testing the user interface layout of the application
  2. Verifying that a service's interface matches what its consumers expect Correct answer.
  3. Measuring the CPU usage of each microservice
  4. Replacing all unit tests in each service

Explanation

Contract tests check that the interactions between a provider and its consumers conform to an agreed interface, catching integration breakage without deploying full environments. They are lightweight and fast enough for frequent pipeline runs.

Question 40DevOps Continuous Testing and Culture

How does continuous testing differ from traditional testing at the end of a release cycle?

  1. It removes the need for regression testing
  2. It relies exclusively on manual testers
  3. It happens only once before go-live
  4. It runs continuously throughout delivery, giving ongoing feedback Correct answer.

Explanation

Continuous testing is woven into every stage of the delivery pipeline so feedback is ongoing rather than a single late event. This supports faster, safer releases with early defect detection.

Question 41DevOps Continuous Testing and Culture

A developer's pull request shows a failing unit test in the pipeline. What should happen before merge?

  1. The merge proceeds and the failure is tracked in a backlog
  2. The pipeline is bypassed to meet the deadline
  3. The test is deleted to unblock the merge
  4. The failing test is fixed or the change is corrected before merging Correct answer.

Explanation

A red pipeline is a stop signal; the change or test must be corrected so the mainline stays releasable. Bypassing or deleting tests undermines the trust that makes continuous delivery safe.

Question 42DevOps Continuous Testing and Culture

Which practice helps teams reduce the cost of maintaining automated tests over time?

  1. Storing test logic in manual spreadsheets
  2. Applying consistent design patterns and reviewing test code like production code Correct answer.
  3. Avoiding any refactoring of test code
  4. Writing every test as a full end-to-end scenario

Explanation

Treating test code with the same rigor as production code, including patterns, reviews, and refactoring, keeps suites maintainable and reduces brittleness. Poorly designed tests become a drag on continuous testing.

Question 43DevOps Continuous Testing and Culture

What does 'test environment parity' mean in a continuous testing context?

  1. Environments are recreated manually once per year
  2. Only developers use test environments
  3. Test environments are deliberately kept minimal and dissimilar
  4. Test environments closely resemble production configuration Correct answer.

Explanation

Environment parity means test environments mirror production in configuration and dependencies so tests reveal issues that would occur in production. Infrastructure as code helps keep parity consistent.

Question 44DevOps Continuous Testing and Culture

A team notices defects are frequently found in production despite passing automated tests. Which analysis is most relevant?

  1. Remove performance tests from the pipeline
  2. Increase the number of manual testers immediately
  3. Reduce the frequency of deployments
  4. Evaluate test coverage gaps and whether tests reflect real user behavior Correct answer.

Explanation

Escaped defects usually indicate that tests do not cover the scenarios users actually exercise, so coverage and test realism should be examined. Adding manual effort or slowing deployments does not address the root cause.

Question 45DevOps Continuous Testing and Culture

Which combination best characterizes a mature continuous testing culture?

  1. Manual-only verification and infrequent releases
  2. Outsourced testing with no developer involvement
  3. Shared quality ownership, fast automated feedback, and blameless learning from failures Correct answer.
  4. Centralized testing silo, slow release cadence, and blame for defects

Explanation

Mature continuous testing cultures combine shared responsibility, rapid automated feedback, and blameless post-incident learning that drives improvement. These elements reinforce each other to sustain quality at speed.

Question 46DevOps Continuous Testing and Culture

What is the main risk of relying on a high test coverage percentage as the sole quality indicator?

  1. Coverage always correlates perfectly with defect-free code
  2. Coverage can be high while assertions are weak and behavior is unverified Correct answer.
  3. Coverage tools cannot measure line execution
  4. Coverage guarantees production performance

Explanation

Coverage measures which code executes, not whether tests meaningfully verify behavior, so weak assertions can inflate the number. It should be used alongside defect escape rates and other signals.

Question 47DevOps Continuous Testing and Culture

In a CI/CD pipeline, which test type is best suited to validate system behavior under realistic load before release?

  1. Static code analysis
  2. Spell-checking of documentation
  3. Unit tests with mocked dependencies
  4. Performance and load tests in a production-like environment Correct answer.

Explanation

Load and performance tests require realistic environments and traffic patterns to reveal bottlenecks, so they run against production-like setups. Unit tests and static analysis cannot model system-level load behavior.

Question 48DevOps Continuous Testing and Culture

What does a blameless post-incident review contribute to continuous testing?

  1. It replaces the need for automated regression tests
  2. It slows future deployments by adding approvals
  3. It surfaces test gaps and drives new automated checks into the pipeline Correct answer.
  4. It identifies individuals to discipline for failures

Explanation

Blameless reviews focus on systemic causes, revealing where tests or monitoring failed to catch an issue so new checks can be added. This closes the feedback loop and strengthens future prevention.

Question 49DevOps Continuous Testing and Culture

Which statement best explains why automated regression testing is central to continuous delivery?

  1. It eliminates the need for any human judgment in releases
  2. It provides repeatable verification that new changes do not break existing behavior Correct answer.
  3. It guarantees zero defects in production
  4. It replaces the need for version control

Explanation

Automated regression suites give repeatable, fast confirmation that existing functionality still works after each change, enabling frequent releases with confidence. They support human decisions rather than replacing them.

Question 50DevOps Continuous Testing and Culture

A team wants to introduce continuous testing but currently has almost no automated tests. What is the most pragmatic first step?

  1. Automate the highest-risk, most frequently executed regression checks first Correct answer.
  2. Wait until a complete test strategy document is finalized
  3. Outsource all testing and pause pipeline work
  4. Attempt to automate every possible test at once

Explanation

Incremental automation starting with high-risk, high-frequency checks delivers early value and builds momentum. Trying to automate everything at once is costly and often stalls.