ISQI CTAL-TTA_Syll19_4.0 test insides dumps : ISTQB Certified Tester Advanced Level - Technical Test Analyst (V4.0)

You are working on project where re-use of software is an objective. You are involved in the project as a Technical Test Analyst and have been given the task to develop a checklist for code reviews.
Which question from the list below should you implement as part of the code review checklist?

• A. Is it possible during acceptance testing to verity whether the item has been satisfied?
• B. Are all modules, data, and interfaces uniquely identified?
• C. Are all variables defined with meaningful, consistent and clear names?
• D. Can each item be implemented with the techniques, tools, and resources available?

Which of the following defect types is NOT an example of a defect type typically found with API testing?

• A. Loss of transactions
• B. High architectural structural complexity
• C. Timing problems
• D. Data handling issues

Subject to testing is a software system (COTS) for Project Administration and Control (PACS). PACS is a multi-project system for controlling the project time, e.g., in terms of scheduling and tracking, and managing the productivity of projects, e.g., in terms of effort and deliverables.
During various interviews with stakeholders the following information was gathered:
* Using PACS is not business critical. There is no impact such as high financial losses or problems to the operational continuity of an organization. Its application is not critical since the software package does not support directly the operational, or the primary, business processes of an organization. It supports (project) management in the project planning and tracking process. Of course, it will be highly annoying for users if the system "goes down" from time to time. Although this does not have a high impact for the business process as a whole, the Mean Time Between Failures (MTBF) still needs to be at a good level to be successful in the market.
* Users of PACS typically have an academic educational level, but have no prior experience with this particular type of project management software. The system will be used by a large number of users within an organization.
* The system will be used on a regular basis, e.g., several times per day by project managers and several times per week by project employees. This means that the system will not be used very intensively, often only for some data input or an information request. Its usage is not considered to be very time-critical.
* The data is recorded on-line and real-time. The system is expected to run in multiple hardware environments in various network environments. It is also expected that changes in the operational environments will happen in the upcoming period that also need to be supported.
Based on the information provided by the stakeholder, which combination of non-functional quality characteristics should you propose to test as part of your test approach?

• A. Reliability and Portability
• B. Performance efficiency and Portability
• C. Reliability and Performance efficiency
• D. Security and Reliability

The following characteristics were identified during an early product risk-assessment for a software system:
* the software system needs to manage synchronization between various processes
* microcontrollers will be used that will limit product performance
* the hardware that will be used will make use of timeslots
* the number of tasks supported in parallel by the software system is large and are often highly complex.
Based on the information provided, which of the following non-functional test types is MOST appropriate to be performed?

• A. Portability testing
• B. Security testing
• C. Maintainability testing
• D. Time-behaviour testing

Which of the following statements about fault seeding tools is correct?

• A. Fault seeding tools insert defects into the source code to check the level of maintainability of the software.
• B. Fault seeding tools insert defects into the source code to check the effectiveness of testing.
• C. Fault seeding tools insert defects into the source code to support the application of specification-based test design techniques.
• D. Fault seeding tools insert defects into the source code to test the input checking capabilities of the software.