Question 1

You are estimating the effort for the integration testing activities of a new project. Consider the following factors, which can affect that estimation:

Accepted Answer

C

Question 2

Which of the following would you expect to be most likely an example of a demotivating factor for testers? Number of correct responses: 2

Accepted Answer

C, E

Explanation: Demotivating factors for testers often stem from repetitive, unchallenging work and unfair performance metrics. Manually executing the same regression tests repeatedly (C) is tedious, lacks intellectual stimulation, and is inefficient, which can significantly lower morale. Using the number of customer-reported problems as a primary measure of test quality (E) is also highly demotivating. This metric unfairly places blame on the test team for defects that escape to production, ignoring factors like project constraints, inherent code quality, and the impossibility of exhaustive testing. It fosters a culture of blame rather than collaborative quality improvement.

Question 3

Which of the following statements describing the consequences of specifying test conditions at a detailed level is NOT true? Number of correct responses: 1

Accepted Answer

A

Explanation: Specifying test conditions at a detailed level creates a strong dependency on the test basis (e.g., requirements specifications). In an environment where this basis is continuously changing, detailed test conditions become a significant maintenance burden. Each change to the test basis would require a corresponding, and often complex, update to the detailed test conditions. Therefore, in such volatile environments, it is more practical to specify test conditions at a higher, more abstract level to improve maintainability. High-level conditions are less sensitive to minor changes in the underlying documentation.

Question 4

After the presentation, you are asked to explain the chart. Assume you have applied a full risk-based testing strategy. https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/BCS_TM12/page_20_img_1.jpg Which of the following answers would you expect to best describe the pie chart? Number of correct responses: 1

Accepted Answer

C

Explanation: A full risk-based testing strategy prioritizes test activities according to the identified level of product risk. The highest-risk items are tested first and most rigorously. The provided chart shows that 97% of risk items are covered by passed tests. Following the risk-based approach, these would be the highest and medium-risk items. The remaining 3% (2% covered by failed tests and 1% not yet covered) would logically correspond to the lowest-risk items. Therefore, a release can be considered, subject to a business decision on managing the known, low-risk failures and accepting the minimal risk of the untested items.

Question 5

Assume that the following test cases have been executed at the end of the first week of test execution: TC-001, TC-002 and TC-007. All these tests are ‘passes’. What is the MINIMUM number of the remaining test cases that must be successfully executed to fulfill the EX1 exit criteria? https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/BCS_TM12/page_8_img_1.jpg Number of correct responses: 1

Accepted Answer

A

Explanation: The exit criterion EX1 states, "100% of tests of priority 1 have been executed and passed." By analyzing the provided table, we can identify a total of seven test cases with Priority 1: TC-001, TC-002, TC-003, TC-004, TC-005, TC-006, and TC-007. The scenario specifies that three of these Priority 1 test cases (TC-001, TC-002, and TC-007) have already been executed and passed. To satisfy the 100% completion requirement of EX1, the remaining Priority 1 test cases must also be successfully executed. The remaining test cases are TC-003, TC-004, TC-005, and TC-006, which amounts to a minimum of 4 test cases.

Question 6

You are managing the system testing for a SOA based system. The integrated system consists of several subsystems: - a SOA middleware - a CRM (Customer Relationship Management) system - a BRM (Billing and Revenue Management) system - a SMS (Subscriber Management System) system and you performed a risk analysis based on these subsystems. At the end of the scheduled period for test execution you produce a first classical report based on the traditional metrics of testing. Test pass/fail status and bug status (open/resolved) That table provides you a distorted picture of the quality risk, because there is no indication of the risk level of the failed tests, the tests not run, or the open bugs. Thus, you produce the following table to solve this distortion issue: https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/BCS_TM12/page_21_img_1.jpg In the table above, where you have introduced the concept of risk weighting, the highest risk test or bug report has a score of 1, while the lowest risk test or bug report has a score of 0.04. Which of the following subsystems, based on the risk scores of the table, is most risky? Number of correct responses: 1

Accepted Answer

B

Explanation: To determine the most risky subsystem, the total risk score for each must be calculated by summing the individual risk scores from the three categories provided: 'Failed Tests', 'Not Run Tests', and 'Open Bugs'. This aggregate score represents the overall quality risk for each component. The calculations are as follows: SOA: 1.2 + 0.8 + 1.5 = 3.5 CRM: 2.5 + 1.2 + 2.1 = 5.8 BRM: 1.8 + 0.5 + 1.1 = 3.4 SMS: 0.9 + 0.2 + 0.7 = 1.8 Based on these totals, the CRM subsystem has the highest aggregate risk score of 5.8, making it the most risky subsystem.

Question 7

The main objectives the senior management team wants to achieve are:
- to reduce the costs associated with dynamic testing
- to use reviews to ensure that the project is on course for success and following the plan
- to use reviews as a well-documented and effective bug-removal activity following a formal process
with well-defined roles
- to determine the effectiveness of reviews in terms of phase containment
- to improve phase containment effectiveness
Which of the following answers would you expect to describe the best way to achieve these
objectives?
Number of correct responses: 1

Accepted Answer

D

Explanation: This option directly addresses all of the senior management's objectives. Planning for "formal exit-phase reviews" satisfies the need for a well-documented, formal bug-removal activity with defined roles. The process of analyzing bugs to "determine the phase in which they have been introduced" is the exact mechanism required to measure and subsequently improve "phase containment effectiveness." By identifying where defects originate, the team can enhance the review and testing processes in those specific early phases. This shift-left approach of finding and fixing defects earlier is a proven method for reducing the overall costs associated with later-stage dynamic testing.

Question 8

After a selection process you have selected a test management tool that is going be introduced in
your organization and used by your test team in a pilot project.
You have already identified the member of your test team who will be the administrator of the tool,
since he/she has a significant experience with the administration of test management tools and so
he/she is able to make effective and efficient up-front decisions about "how" the tool will be used.
You have also developed a training plan for the other members of your test team.
In collaboration with the administrator of the tool you have also devised standard ways of managing,
storing and maintaining the tool and its assets including backup/restore procedures.
You have also analyzed standard formats supported by the tool (CSV, XLS, XML, etc.) to export, import
and archive all the information managed by the tool itself (requirements, test case specifications,
test plans etc.) for compliance with the most important test management tools, in order to minimize
the impacts of migrating this information to a new tool that could replace the existing one in the
future.
Which of the following phases in the lifecycle of the new tool has NOT been adequately considered in
this description?
Number of correct responses: 1

Accepted Answer

C

Explanation: The scenario describes activities related to several phases of the tool's lifecycle. The selection process covers Acquisition. The creation of backup/restore procedures and standards for managing assets covers Support and Maintenance. Analyzing data export formats for future migration explicitly addresses the Retirement phase. However, the 'Evolution' phase is not adequately considered. This phase involves the ongoing adaptation and growth of the tool's usage, such as rolling it out to other projects beyond the pilot, integrating it with other tools in the software development lifecycle (e.g., CI/CD pipelines), and planning for version upgrades. The description focuses on the initial setup and eventual replacement, omitting the strategy for its growth and adaptation over time.

Question 9

You are performing a quality risk analysis for a CSCI (Computer Software Configuration Item) used to
implement a CBIT (Continuous Built-In Test) module of a safety-critical system.
During the quality risk analysis you are trying to identify the ways in which failures of the CBIT
module can occur, for each of them trying to determine the potential causes and likely effects, and
the risk level (calculated as the product of three factors: severity, occurrence and detection).
Which of the following risk analysis techniques are you working with?
Number of correct responses: 1

Accepted Answer

B

Explanation: The process described is a textbook application of Failure Mode and Effect Analysis (FMEA). This technique systematically identifies potential "failure modes" (ways a system can fail), analyzes their "effects," and determines their root "causes." A key component of FMEA is the calculation of a Risk Priority Number (RPN) to prioritize risks. The question explicitly states this calculation as the product of three factors: severity, occurrence (likelihood), and detection. This structured, bottom-up approach is characteristic of FMEA and is widely used for risk analysis in safety-critical systems, as described in the scenario.

Question 10

You are a Test Manager working for a software organization where reviews have never been applied.
After a meeting with your managers examining a business case for reviews, (including their costs,
benefits, and potential issues), the management finally decides to adopt formal reviews for future
projects.
You have been given a budget that you have spent to provide training in the review process and to
introduce the review process on a pilot project.
On that pilot project the introduction of reviews has been very positive in terms of positive
involvement from all the participants. All the reviews applied to different documents have been very
effective for their purposes (especially at revealing defects).
Which of the following answers describes an important success factor for the introduction of formal
reviews which is missing in this scenario?
Number of correct responses: 1

Accepted Answer

C

Explanation: The scenario explicitly confirms the presence of management support, participant involvement, and training. A business case was examined, and the pilot was effective. However, a critical success factor for the long-term institutionalization of a new process is the ongoing measurement of its value. The scenario does not mention the definition and systematic use of metrics to calculate and demonstrate the Return on Investment (ROI). While the pilot was successful, sustaining management support and optimizing the process requires quantitative proof of its benefits, which is achieved through metrics.

Question 11

Assume you have some data related to confirmation testing during system testing of a past project.
In that project 240 bug reports have been opened once, 80 were opened twice, 10 were opened
three times and no bug reports have been opened more than three times.
You estimate that a bug report, which has failed its confirmation test, costs, on average, 3 person-
hours.
Which of the following statements correctly describe the value of these confirmatory testing
activities based on cost of quality?
Number of correct responses: 1

Accepted Answer

A

Explanation: The total cost is calculated based on the number of times confirmation tests failed, which is indicated by bug reports being reopened. - 80 bug reports were opened twice, meaning each failed confirmation testing once (80 1 = 80 failures). - 10 bug reports were opened three times, meaning each failed confirmation testing twice (10 2 = 20 failures). - Total failures = 80 + 20 = 100 failed confirmation tests. - Total cost = 100 failures 3 person-hours/failure = 300 person-hours. In the Cost of Quality model, costs associated with defects found before delivery to the customer are classified as internal failure costs. Since system testing is an internal pre-release activity, the cost of rework and re-testing falls into this category.

Question 12

An agile development team decides to hire a tester who has always worked:
- in independent test teams, reporting the problems found in a defect tracking system
- in safety-critical projects, with a stronger focus on the quality of the product than on time and
budget.
This agile team is focused on short-term goals to get the product released on time and within
budget.
Which of the following answers would you expect to be most likely true in this scenario?
Number of correct responses: 1

Accepted Answer

D

Explanation: In an agile environment, the role of a tester shifts from a formal gatekeeper to an integrated team collaborator. The primary goal is to provide rapid feedback to developers to ensure the product meets requirements and can be released on time. The tester's background in formal defect reporting and prioritizing quality above all else conflicts with the agile team's focus on speed and budget. Therefore, the most likely successful adaptation is for the tester to change their mission. They would focus on verifying that user stories meet acceptance criteria and communicating findings directly to developers, rather than using a formal defect tracking system for every issue, which aligns with agile principles of direct communication and delivering value quickly.

Question 13

You are the Test Manager of a new project that will have three formal levels of testing: unit,
integration and system testing. The testing strategy you decide to adopt a blend of risk-based testing
and reactive testing strategies.
Which of the following answers describes the most consistent example of implementation of this test
strategy during the execution of the system tests?
Number of correct responses: 1

Accepted Answer

C

Explanation: The specified test strategy is a blend of risk-based and reactive approaches. A risk-based strategy is analytical and proactive, involving the design of tests based on a product risk analysis before execution. This is represented by "scripted tests designed...to cover the identified product risks." A reactive strategy involves designing and executing tests dynamically based on the system's behavior during execution. This is represented by "exploratory testing sessions." Option C is the only answer that correctly combines both the proactive, pre-planned element of risk-based testing with the dynamic, adaptive nature of reactive testing, providing a consistent implementation of the blended strategy.

Question 14

Assume you are the Test Manager for a new software release of an e-commerce application.
The server farm consists of six servers providing different capabilities. Each capability is provided
through a set of web services.
The requirements specification document contains several SLAs (Service Level Agreements) like the
following:
SLA-001: 99.5 percent of all transactions shall have a response time less than five seconds under a
load of up-to 5000 concurrent users
The main objective is to assure that all the SLAs specified in the requirements specification document
will be met before system release. You decide to apply a risk-based testing strategy and an early risk
analysis confirms that performance is high risk.
You can count on a well-written requirements
specification and on a model of the system behavior under various load levels produced by the
system architect.
Which of the following test activities would you expect to be the less important ones to achieve the
test objectives in this scenario?
Number of correct responses: 1

Accepted Answer

B

Explanation: The main objective stated is to "assure that all the SLAs... will be met before system release." Monitoring SLAs after the system is in production (Option B) is a post-release activity. While essential for operational management and ensuring ongoing performance, it does not contribute to the pre-release assurance goal. The other options represent critical pre-release testing activities within a comprehensive, risk-based performance testing strategy. Unit performance testing (A), static architectural review (D), and system performance testing (C) are all designed to find and mitigate performance risks before the application goes live, directly supporting the stated objective.

Question 15

Based on the historical data of 5 past and similar projects, you have calculated these average
numbers of defects detected in system testing:
- for each 10000 LOC (lines of code), 200 defects
- for each person-month of development team effort, 49 defects
You want to use this information to perform estimation for a new project.
The project manager tells you that he/she has estimated 20000 new LOC for this new project.
Four developers work for four months on this project before system testing.
During system testing, 797 defects are discovered.
Assume that the system test of this new project is using the same amount of work as spent in the
past projects.
Based on this information only, which of the following statement is certainly true about this project?
Number of correct responses: 1

Accepted Answer

B

Explanation: The analysis involves comparing two prediction models against the actual outcome. 1. Prediction based on LOC: The historical rate is 200 defects per 10,000 LOC. For the estimated 20,000 LOC, the expected number of defects is (20,000 / 10,000) 200 = 400 defects. 2. Prediction based on Effort: The historical rate is 49 defects per person-month. The project effort is 4 developers 4 months = 16 person-months. The expected number of defects is 16 49 = 784 defects. The actual number of defects discovered was 797. This number is extremely close to the effort-based prediction (784) but significantly different from the LOC-based prediction (400). Therefore, the statement that is "certainly true" is that the number of defects is approximately proportional to the development effort for this project.

Free BCS TM12 Actual Exam Questions