100%更新されたのはISTQB CTAL-TTA限定版PDF問題集
有効な試験問題を試そうCTAL-TTAには無料サイトで限定お試しチャンス
質問 # 19
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. Can each item be implemented with the techniques, tools, and resources available?
- B. Are all modules, data, and interfaces uniquely identified?
- C. Is it possible during acceptance testing to verity whether the item has been satisfied?
- D. Are all variables defined with meaningful, consistent and clear names?
正解：B
解説：
For a project where the reuse of software components is a key objective, it is essential to ensure that all modules, data, and interfaces are uniquely identified. This facilitates the tracking, maintenance, and reuse of these components in different parts of the software or in other projects. Unique identification helps in preventing confusion and conflicts that may arise due to the reuse of components that have the same name but different functionalities or interfaces.
質問 # 20
Within the world of consumer electronics, the amount of embedded software is growing rapidly. The amount of software in high-end television sets has increased by a factor of about eight over the last six years. In addition, the market of consumer electronics has been faced with a 5 -10% price erosion per year. The price of a product is, among a number of other things, determined by the microcontroller used. Therefore, the use of ROM and RAM remains under high pressure in consumer electronic products, leading to severe restrictions on code size.
Within a new high-end TV project, it has been decided to apply dynamic analysis.
Which of the quality goals listed below is MOST appropriate to the project context?
- A. Evaluate network behaviour.
- B. Improve system performance by providing information on run-time system behaviour.
- C. Prevent failures from occurring by detecting wild pointers and loss of system memory.
- D. Analyse system failures which cannot easily be reproduced.
正解：B
解説：
In the context of consumer electronics, where there is rapid growth in embedded software and pressure to minimize code size due to cost constraints, dynamic analysis can be particularly useful for improving system performance. Dynamic analysis involves examining the system's behavior during execution, which can provide insights into the efficiency of the code at runtime, memory utilization, and processing speed. In a high-end TV project where the use of ROM and RAM is under severe restrictions, dynamic analysis would be most appropriately applied to improve system performance, ensuring that the software runs efficiently within the available hardware resources. This supports the project context by contributing to the optimization of the software to run within the constraints of the microcontroller used, thereby potentially reducing costs.
質問 # 21
Which of the following statements about fault seeding tools is correct?
- A. Fault seeding tools insert defects into the source code to check the effectiveness of testing.
- B. Fault seeding tools insert defects into the source code to support the application of specification-based test design techniques.
- C. Fault seeding tools insert defects into the source code to check the level of maintainability of the software.
- D. Fault seeding tools insert defects into the source code to test the input checking capabilities of the software.
正解：A
解説：
Fault seeding is a method used to evaluate the effectiveness of a testing process. Tools designed for fault seeding intentionally insert known defects into the source code, which are then supposed to be discovered during testing. The main purpose is not to check the input checking capabilities, support specification-based test design techniques, or assess maintainability of the software, but rather to gauge how well the testing process can identify and capture defects. By comparing the number of seeded faults that are found against the total number of faults inserted, test teams can get an insight into the effectiveness of their testing strategies and coverage. This method helps in understanding the detection capabilities of testing efforts and in identifying potential areas for improvement in test processes.
質問 # 22
Which of the following is NOT a common issue with traditional capture/playback test automation?
- A. Recorded scripts are difficult to maintain by non-technical persons.
- B. Difficult to maintain when software changes.
- C. Data and actions are mixed in the recorded script.
- D. Execution of the recorded script is difficult outside office hours.
正解：D
解説：
Common issues with traditional capture/playback test automation include difficulty in maintaining the scripts when software changes (option A), the challenge for non-technical persons to maintain recorded scripts (option B), and the issue that data and actions are often intertwined within the recorded script (option C), which can make them hard to understand and modify. However, the timing of the execution of the recorded script (option D), such as the difficulty of running scripts outside office hours, is not typically a problem inherent to capture/playback test automation itself but rather an environmental or scheduling issue.
質問 # 23
Within an embedded software project, the maintainability of the software is considered to be critical. It has been decided to use static analysis on each delivered software component.
Which of the following metrics is NOT a maintainability metric typically used with static analysis?
- A. Mean Time Between Failures
- B. Number of Lines of Code (LOG)
- C. Number of Function Calls
- D. Comment Frequency
正解：A
質問 # 24
A medical company has performed a safety criticality analysis using the IEC61508 standard. The software components to be developed have been categorized by Safety Integrity Level (SIL). Most components have been rated at SIL 1 or 2, and a few components at SIL 4.
After some discussions with the QA manager, the project has decided to adhere to the recommendations for test coverage provided by the IEC61508 standard.
Which level and type of test coverage should at least be used for the components rated at Safety Integrity Level (SIL) 2?
- A. 100% statement coverage, 100% decision coverage and 100% MC/DC coverage
- B. 100% statement coverage, 100% decision coverage and 100% multiple condition coverage
- C. 100% statement coverage and 100% decision coverage
- D. 100% statement coverage
正解：C
解説：
In the context of software testing, different safety integrity levels (SIL) require different levels of rigor in testing. According to the IEC61508 standard, for software components rated at SIL 2, achieving 100% statement coverage and 100% decision coverage is recommended. Statement coverage ensures that every line of code is executed at least once during testing, while decision coverage ensures that every decision in the code (e.g., every branch of an IF statement) is executed on both the true and false sides. These coverage criteria ensure a thorough testing of the software components to validate that they behave correctly in all circumstances. Multiple condition coverage and MC/DC coverage (Options A and B) are more rigorous and typically required for higher SIL levels, such as SIL 4.
質問 # 25
You have been assigned to perform a review on code provided below:
Which type of defect should you report as part of the code review?
- A. Unreachable code
- B. Endless loop
- C. Too many nested levels
- D. No defects should be reported, code is correct.
正解：B
解説：
The code provided contains a potential endless loop. The loop is conditioned on the variable 'E' being less than 1 (IF E < 1), but within the loop, there is no operation that modifies the value of 'E'. Therefore, once the loop is entered, if the condition A > B holds true, the value of 'E' remains unchanged, leading to an endless loop situation. The decrement of 'A' in line 15 does not guarantee an exit condition for the loop, as it does not affect the value of 'E'. This is a control flow defect that could cause the program to hang or crash.
質問 # 26
Consider the code fragment provided below:
The comment frequency of the code fragment is 13%.
To which non-functional quality characteristic does a good level of comment frequency especially contribute?
- A. Performance Efficiency
- B. Maintainability
- C. Usability
- D. Portability
正解：B
解説：
The comment frequency in a code fragment relates to the number of comments in relation to the code size. A good level of comment frequency can significantly contribute to the maintainability of the software. Maintainability is a non-functional quality characteristic that refers to the ease with which a software system can be modified to correct defects, update features, improve performance or other attributes, or adapt to a changed environment. Comments in the code help developers understand the logic, purpose, and functionality of the code, which is crucial when modifications are required. This does not directly contribute to portability, usability, or performance efficiency, which are concerned with different aspects of the software's operation and user interaction.
質問 # 27
Consider the following fault attack:
* Force all possible incoming errors from the software/operating system interfaces to the application.
Which of the following is the kind of failure you are looking for when using this attack?
- A. Application crashes due to a lack of portability.
- B. Application miscalculates total monthly balance due on credit cards.
- C. Application crashes when the network is unavailable.
- D. Application crashes when unsupported characters are pasted into an input field.
正解：D
解説：
The fault attack described involves forcing all possible incoming errors from software/operating system interfaces. The type of failure being sought is one where the application does not handle erroneous or unexpected input correctly, which can lead to crashes or other unintended behavior. Thus, an application crash when unsupported characters are pasted into an input field is a typical failure that this kind of fault attack would aim to uncover.
質問 # 28
Consider the following specification:
If you are flying with an economy ticket, there is a possibility that you may get upgraded to business class, especially if you hold a gold card in the airline's frequent flier program. If you don't hold a gold card, there is a possibility that you will get 'bumped' off the flight if it is full when you check in late.
This is shown in the control flow graph below. Note that each box (i.e., statement, decision) has been numbered.
Three tests have been run:
Test 1: Gold card holder who gets upgraded to business class
Test 2: Non-gold card holder who stays in economy
Test 3: A person who is bumped from the flight
What is the level of decision coverage achieved by these three tests?
- A. 75%
- B. 67%
- C. 60%
- D. 80%
正解：B
解説：
The control flow graph provided illustrates the decision points for an airline's upgrade and boarding process. Decision coverage is a measure of the percentage of decision points executed during testing:
Test 1 covers the decision points: Gold card? (Yes) and Business full? (No).
Test 2 covers: Gold card? (No) and Economy full? (No).
Test 3 covers the decision that leads to being bumped from the flight, which is Economy full? (Yes) and Business full? (Yes).
From the given tests, the decision points for Gold card? (No) and Business full? (No) are not tested, leaving us with 4 out of 6 decision points covered, which is approximately 67% decision coverage.
質問 # 29
Consider the pseudo code for the Answer program:
Which of the following statements about the Answer program BEST describes the control flow anomalies to be found in the program?
- A. The Answer program contains unreachable code.
- B. The Answer program contains unreachable code and an infinite loop.
- C. The Answer program contains an infinite loop.
- D. The Answer program contains no control flow anomalies.
正解：B
解説：
The provided pseudo code for the Answer program shows a WHILE loop that will always execute because the condition for the loop to terminate (a >= d) is never met within the loop's body. This results in an infinite loop. Additionally, since the value of 'b' is initialized with 'a + 10' and 'a' starts from a value that is read and then set to 2, 'b' will never be equal to 12. Therefore, the 'THEN' branch of the IF statement, which includes 'print(b)', is unreachable. These are control flow anomalies because they represent logic in the code that will not function as presumably intended.
質問 # 30
Which of the following statements is TRUE regarding tools that support component testing and the build process?
- A. Build automations tools facilitate manual testing at a low level by allowing the change of variables values during test execution.
- B. Component testing tools are the basis for a continuous integration environment.
- C. Component testing and build automation tools are only used by developers.
- D. Component testing tools are typically specific to the programming language and may be used to automate unit testing.
正解：D
解説：
Component testing tools, which are often specific to a programming language, are used to automate unit tests (answer C). These tools help to validate the functionality of individual components or units of code in isolation from the rest of the application. While build automation tools are indeed used by developers and are related to continuous integration (answers A and D), and they can facilitate testing at various levels (answer B), component testing tools' primary purpose is to support the testing of individual components, often through automated unit tests, which can be specific to the language in which the components are written.
質問 # 31
There are multiple activities the Technical Test Analyst performs regarding test automation. Which of the following activities is a typical test automation activity that the Technical Test Analyst will perform?
- A. Execute the test cases and analyze any failures that may occur.
- B. Decide regarding a test automation project based on a business case.
- C. Define the business process keywords and related actions.
- D. Train the Test Analyst and Business Analyst to use and supply data for the test scripts.
正解：A
解説：
A Technical Test Analyst is primarily involved in the technical aspects of test preparation and execution. One of their typical activities includes the execution of test cases, particularly those that are automated, and the subsequent analysis of any test failures to identify defects and issues. This activity is more technical than defining business processes or training other analysts, and while making decisions based on a business case may be part of their role, it is not an activity directly related to test automation.
質問 # 32
A component has been analysed during a risk-assessment and rated as highly critical. Which of the following white-box test techniques provides the highest level of coverage and could therefore be used to test this component?
- A. Modified condition/decision testing
- B. Multiple condition testing
- C. Statement testing
- D. Decision testing
正解：A
解説：
Modified condition/decision testing (MC/DC) provides a higher level of coverage compared to other white-box testing techniques because it requires each condition in a decision to be shown to independently affect that decision's outcome. It is more rigorous than both decision testing (which only requires each decision's possible outcomes to be tested) and statement testing (which requires only each executable statement to be executed). Therefore, for a highly critical component, MC/DC is more appropriate as it ensures a more thorough assessment of the logic in the software component.
質問 # 33
Which of the following defect types is NOT an example of a defect type typically found with API testing?
- A. Timing problems
- B. Data handling issues
- C. High architectural structural complexity
- D. Loss of transactions
正解：C
解説：
In the context of API testing, the defect types generally found are related to the specific interactions with the API, such as issues with data formatting, handling, validation, and the sequencing or timing of API calls. Architectural structural complexity is not typically a defect that would be identified at the API testing level. API tests are concerned with the interface and immediate integration points, not the overarching system architecture, which would be more relevant to design or system-level testing.
質問 # 34
Below is the pseudo-code for the Win program:
The bingo program contains a data flow anomaly. Which data flow anomaly can be found in this program?
- A. It is recommended to use a variable instead of the hard-coded print results "Win" and *Loose".
- B. Variable 'A" is not assigned a value before using it.
- C. Variable 'D" is defined but subsequently not used.
- D. The program does not contain any comments.
正解：C
解説：
The pseudo-code provided for the "Win" program reads in variables A, B, C, and D. However, only variables A, B, and C are used in the conditional statements to determine if the output will be "Win" or "Loose". Variable 'D' is never used after it is read, which is a classic example of a 'defined but not used' data flow anomaly. This means that while there is an instruction to read a value into variable 'D', there is no subsequent use of this variable in the program's logic or output.
質問 # 35
Within an embedded software project, the maintainability of the software is considered to be critical. It has been decided to use static analysis on each delivered software component.
Which of the following metrics is NOT a maintainability metric typically used with static analysis?
- A. Mean Time Between Failures
- B. Number of Lines of Code (LOG)
- C. Number of Function Calls
- D. Comment Frequency
正解：A
解説：
Maintainability metrics typically used with static analysis include measures that reflect the complexity and understandability of the code, such as Number of Lines of Code (LOC), Number of Function Calls, and Comment Frequency. These metrics help in assessing how easily the software can be understood, modified, and maintained. Mean Time Between Failures (MTBF), on the other hand, is a reliability metric. It measures the time elapsed between inherent failures of a system during operation. MTBF is used to predict the system's reliability and is not directly related to the maintainability of the code. Reliability metrics like MTBF would be used in the testing phase to measure the operational reliability of the system rather than during static analysis for maintainability assessment.
質問 # 36
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. Security testing
- B. Maintainability testing
- C. Time-behaviour testing
- D. Portability testing
正解：C
解説：
The characteristics listed in the question point towards the need to manage synchronization between processes and make efficient use of limited hardware resources, such as microcontrollers and timeslots. Additionally, the complexity and concurrency of tasks highlight the importance of the software's performance over time. Time-behaviour testing is the most appropriate non-functional test type to perform in this scenario as it focuses on evaluating the timing aspects of the system, such as response times, processing times, and throughput rates. It ensures that the system meets its time-related requirements, which is critical for systems reliant on synchronization and limited by hardware performance constraints.
質問 # 37
At which test level would performance efficiency testing most likely be performed?
- A. Integration testing
- B. User acceptance testing
- C. System testing
- D. Component testing
正解：C
解説：
Performance efficiency testing is most commonly associated with system testing. This is the level at which the complete, integrated system is evaluated, and it is typically where performance, load, and stress testing are conducted to assess the system's behavior under various conditions and loads. Performance efficiency testing at this level helps to ensure that the system meets the necessary performance criteria as a whole.
質問 # 38
......
ISTQB CTAL-TTA公式認定ガイドPDF：https://www.goshiken.com/ISTQB/CTAL-TTA-mondaishu.html
無料Advance Level CTAL-TTA公式認定ガイドPDFダウンロード：https://drive.google.com/open?id=1RYd7CC8JMdycTyJlRkgLItQJCsxrZGmv