CTFL-v4 Practice Test 5 — 10 Questions

Question 1

Which TWO of the following statements accurately describe the characteristics of a formal review process?

Accepted Answer

Formal reviews follow a documented process with defined roles and entry/exit criteria.. Formal reviews are characterized by a structured process, documented results, and defined roles. They provide a disciplined approach to quality improvement by ensuring that participants follow specific procedures, such as preparation and a review meeting. These characteristics distinguish formal reviews from informal reviews, making them highly effective for ensuring compliance with standards and identifying critical defects in high-risk project artifacts throughout the development cycle.

Answer

Formal reviews must always include the participation of a test manager.

Answer

Formal reviews always require the use of automated static analysis tools.

Answer

Formal reviews are generally faster and cheaper than informal reviews.

Question 2

Refer to the exhibit. A tester is validating this security policy. Which activity represents 'validation'?

Accepted Answer

Testing if the policy effectively prevents unauthorized access.. Validation confirms that the system meets user needs. By checking if the security policy actually protects the user's data and meets business security goals (e.g., does it actually prevent unauthorized access?), the tester is performing validation. This is distinct from verification, which would simply check if the code implements the JSON values as written without considering the broader business impact or the effectiveness of the security controls in a real environment.

Answer

Checking if the code correctly parses the JSON file.

Answer

Verifying that the password length is exactly 12 characters.

Answer

Running a syntax check on the JSON configuration file.

Question 3

Refer to the exhibit. A tester reviews this configuration file during the static testing of a test environment setup. What is the primary risk of this configuration in a formal testing phase?

Accepted Answer

The disabled strict mode may allow invalid data to be processed, masking bugs.. Testing requires stable and representative environments. The 'strict_mode: false' setting allows suboptimal code paths or weak error handling to pass, which should fail in production. Finding this via static testing prevents 'false negatives' where the system appears stable in testing due to permissive settings. Ensuring the test environment configuration mirrors production requirements is a critical aspect of early SDLC validation and risk management.

Answer

The log level set to debug will cause an overflow error in the production database.

Answer

The exponential retry policy will increase the latency of the system during stress testing.

Answer

The environment tag set to 'dev' indicates that the deployment is insecure by design.

Question 4

Which of these is a 'test basis'?

Accepted Answer

Business requirement specifications.. A test basis is the documentation used as the foundation for identifying test conditions. It includes everything from requirements and design documents to business processes and user stories. Without a clear test basis, it is impossible to know what the system is supposed to do, making it impossible to write meaningful test cases. Testers use this basis to trace their tests back to specific requirements to ensure complete coverage.

Answer

The list of identified defects.

Answer

The source code of the application.

Answer

The test execution report.

Question 5

What is the primary difference between verification and validation in the context of testing?

Accepted Answer

Verification checks specifications; validation checks user needs.. Verification asks 'Did we build the system right?' by checking if the software meets the specifications. Validation asks 'Did we build the right system?' by checking if it meets user needs. Both are essential: verification ensures internal consistency and adherence to requirements, while validation ensures the software provides real value to the end user. Combining both ensures the software is both technically sound and fit for its intended business purpose.

Answer

Verification is for developers, validation is for testers.

Answer

Validation is done early; verification is done late.

Answer

Verification is testing; validation is debugging.

Question 6

Which of the following is a key characteristic of the 'whole-team' approach to testing in Agile environments?

Accepted Answer

Testing is considered a shared responsibility across the entire team.. In a whole-team approach, quality is a shared responsibility, not just the tester's job. Developers, testers, and business analysts collaborate throughout the process, from planning to deployment. This reduces silos, improves communication, and ensures that quality is considered at every step. By involving everyone, the team leverages diverse perspectives, leading to faster identification of issues and a more robust, user-focused end product that satisfies all stakeholder expectations effectively.

Answer

Testers work in isolation to ensure objective and unbiased results.

Answer

Developers do not need to write tests, as the tester handles all validation.

Answer

Documentation is eliminated entirely to save time for writing code.

Question 7

What is the primary purpose of a 'Defect Triage' meeting in the context of managing test activities?

Accepted Answer

To decide which defects will be fixed and their priority levels.. Defect triage is a collaborative effort to prioritize bugs. It ensures that developers and testers agree on which defects must be fixed immediately versus which can be deferred. This prevents resource wastage on low-priority items and ensures that the most critical issues, which represent the highest risk to the software, are addressed by the development team first during the limited release window.

Answer

To discipline developers for writing poor quality code.

Answer

To rewrite the test cases for the defects that were found.

Answer

To automatically trigger the redeployment of the test environment.

Question 8

A test team has adopted a test automation tool for a web application. After several sprints, they notice that the automated test suites are producing many false failures due to frequent changes in the user interface. Which approach best addresses this problem while maintaining the benefits of test automation?

Accepted Answer

Implement a page object model to separate test logic from UI locators.. The core issue is that UI changes cause automation scripts to fail even when the application behaves correctly. A page object model abstracts UI element locators into separate classes, so changes to the UI require updates in only one place, not across all tests. This reduces maintenance effort and false failures, preserving the value of automation. Other options either increase fragility or reduce test frequency without addressing the root cause.

Answer

Switch to a capture/playback tool to record tests directly from user interactions.

Answer

Reduce the frequency of test execution to once per release.

Answer

Increase the number of test cases in the automated suite to cover more UI variations.

Question 9

What is the main goal of using a 'Capture/Playback' tool during the initial phase of test automation?

Accepted Answer

To quickly understand the tool's interaction capabilities and generate initial scripts.. Capture/Playback tools are excellent for rapidly creating initial test scripts by recording user interactions. They allow testers to quickly visualize how the tool translates actions into code. This provides a gentle learning curve for teams new to automation. However, these tools are best used as a starting point, as they often produce brittle, hard-to-maintain scripts that need significant refactoring into data-driven or keyword-driven frameworks for long-term project success.

Answer

To create a permanent, low-maintenance automation suite for long-term use.

Answer

To perform deep security and vulnerability scanning on the application.

Answer

To automatically optimize the application's source code for better performance.

Question 10

What is the primary difference between a 'Walkthrough' and an 'Inspection'?

Accepted Answer

An inspection is primarily for defect finding, while a walkthrough is for learning.. An inspection is a formal, highly structured review process with specific roles and entry/exit criteria, aimed at identifying defects. A walkthrough is less formal, often led by the author to explain the logic to the team, focusing on shared learning and understanding rather than purely defect finding. This fundamental difference in purpose and process depth defines the choice of which review type to use in various situations.

Answer

A walkthrough is more formal than an inspection.

Answer

A walkthrough requires a moderator and a scribe, but an inspection does not.

Answer

Inspections are never planned in advance, whereas walkthroughs are.