試験準備には欠かさない！CTAL-TTA問題解答でCTAL-TTA試験問題集
リアルISTQB CTAL-TTA試験問題 [更新されたのは2024年]
質問 # 69
Which statement is correct regarding the use of exploratory testing for safety critical systems?
SELECT ONE OPTION
- A. It is highly recommended for all risk levels
- B. It is not recommended, as manual black-box tests should be used instead
- C. It should be used when black-box tests cannot be automated
- D. It is highly recommended for low risk levels only
正解：D
解説：
Exploratory testing is recommended for low-risk levels only when considering safety-critical systems. The correct response is option D.
* Safety-Critical Considerations: For safety-critical systems, where failures can result in severe consequences, structured and well-planned testing strategies are generally prioritized to ensure comprehensive coverage and risk mitigation.
* Role of Exploratory Testing: Exploratory testing can be effective in low-risk scenarios within safety-critical systems by providing a method to quickly identify obvious issues without the constraints of scripted testing. However, it is not typically recommended for higher risk areas due to its less systematic nature and potential for missing critical test cases.
This approach ensures that while innovation and spontaneous testing are employed, they do not compromise the safety and rigorous validation required in critical system components .
質問 # 70
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. The program does not contain any comments.
- C. Variable 'A" is not assigned a value before using it.
- D. Variable 'D" is defined but subsequently not used.
正解：D
解説：
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.
質問 # 71
When conducting a data flow analysis of following section of pseudo code:
Declare C, F, Z Decimal
Set Z = 32
Read F
SetC = (F-Z) * 5/9
Free C, F. Z
Print F
Which of the variables utilized above has a potential anomalie?
- A. C and Z
- B. F
- C. AI1 of the variables
- D. None of the variables
正解：B
解説：
Analyzing the given pseudocode for potential anomalies in data flow:
Declare C, F, Z Decimal Set Z = 32 Read F Set C = (F-Z) * 5/9 Free C, F, Z Print F The potential anomaly is with variable F. It is used after being freed, which typically indicates an error in managing the variable's lifecycle within the code.
* Explanation: Freeing a variable typically indicates that it is no longer available for use, but F is used after this operation, which could result in undefined behavior or errors.
質問 # 72
Which of the following statements BEST describes how tools support model-based testing?
- A. Random sets of threads of execution are generated as test cases.
- B. Large sets of test cases are generated to provide full code coverage.
- C. Finite state machines are used to describe the intended execution-time behavior of a software-controlled system.
- D. An engine is provided that allows the user to execute the model.
正解：C
解説：
Model-based testing tools support the creation and execution of tests based on models of the system under test. Finite state machines (FSMs) are often used in model-based testing to describe the expected behavior of a system during execution. FSMs help in defining the states of the system and the transitions between these states based on events, which can then be used to generate test cases that validate the system's behavior against the model.
質問 # 73
You are defining the test approach for an Agile project release focused on significantly overhauling the user interface of a golf club's booking system. Additional features will allow more flexible bookings across three courses. These changes are driven by numerous customer complaints about the current system's confusing design and limited options. The release will consist of six two-week sprints.
Stakeholders have performed a risk assessment and consider the impact of system failure as high due to potential customer loss. A regression-averse strategy is recommended due to the extensive changes expected in screen design and functionality.
Which option below represents the BEST test approach for this release? Please use the following symbols consistently:
* + (highly recommended)
* (recommended)
* o (neutral/optional)
* * (not recommended)
* - (not to be used)
SELECT ONE OPTION
- A. 0
- B. 1
- C. 2
- D. 3
正解：B
解説：
In addressing the scenario described in the question, the primary considerations for choosing a test approach include the focus on overhauling the user interface, adding new features, and addressing customer complaints in a high-risk environment due to potential customer loss. A regression-averse strategy is also highlighted as critical due to significant changes in design and functionality.
Option D (2) is marked with + for Exploratory Testing (manual) and for Black-box Testing, with Test Automation marked as not to be used (). This selection aligns best with the project's needs for several reasons:
* Exploratory Testing (Highly Recommended): This type of testing is crucial in Agile projects, especially when dealing with UI changes and new functionalities. Exploratory testing allows testers to interact with the system in ways that typical scripted testing may not cover, making it ideal for catching unforeseen issues in new interfaces and features.
* Black-box Testing (Recommended): This testing focuses on the functionality of the application without needing to understand the internal workings. Given the UI overhaul and feature additions, ensuring that the system behaves as expected from an end-user's perspective is necessary.
* Avoidance of Test Automation (Not to be Used): While automation is valuable, focusing primarily on manual testing techniques like exploratory testing is suggested for this specific release due to the extensive UI changes and the need for creative and intuitive testing approaches that adapt quickly to newly developed features.
By using Option D, the test approach supports the dynamic and user-focused nature of the release, addressing both the technical aspects of functionality and the user experience enhancements that are central to this overhaul .
質問 # 74
Which statement about test automation is TRUE?
SELECT ONE OPTION
- A. Test suite coverage can be increased without the need for refactoring
- B. The number of test cases in the test suite increases by default from one iteration to another
- C. Test development time should not consider changes to the test environments)
- D. Staff availability should not be allowed to constrain automated deployment
正解：A
解説：
The statement "Test suite coverage can be increased without the need for refactoring" is accurate because test suite coverage refers to the extent to which the test cases cover the software under test. This coverage can be enhanced by adding new tests that address areas not previously covered, without necessarily modifying the existing test structures or setups. Refactoring is often related to improving the internal design of the tests for better maintainability or performance but does not inherently affect the coverage directly .
質問 # 75
Which of the following are activities that the Technical Test Analyst performs when setting up a test automation project?
1.Schedule the manual testing
2.Define interface requirements between tools
3.Perform a code review on the functional specifications
4.Determine whether to use a rule-dnven approach
5.Tram the test analysts to use and supply the data
- A. 2,5
- B. 3. 5
- C. 1.2
- D. 1.4
正解：A
解説：
In setting up a test automation project, the Technical Test Analyst performs activities such as defining interface requirements between tools and training the test analysts to use and supply the data. These activities are crucial for ensuring that the automation tools are effectively integrated and that the team is capable of utilizing these tools efficiently.
質問 # 76
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. 60%
- B. 80%
- C. 75%
- D. 67%
正解：D
解説：
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.
質問 # 77
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 test the input checking capabilities of the software.
- 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 check the effectiveness of testing.
正解：D
解説：
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.
質問 # 78
The following user story has been written for a new application being developed to pre-book a space at a National Car Park.
As a vehicle driver
i want to be able to pre-book a car parking space online, selecting a disabled driver's space if needed So that l can pay in advance and receive confirmation of my parking space number.
The following acceptance criteria have also been written:
*Payment can be made via PayPal, Debit or Credit Card
*Confirmation of payment and car parking details should be sent after the booking process is completed
*Driver information is stored in the reservation database
The database has been built and tested in a previous sprint, but the interface to the different payment methods have yet to be developed As a tester in an agile team, you have been asked to review the user story You have detected some issues with this story:
1.it needs to cater for different user groups: a driver or disabled driver
2.it needs to cater for different vehicle types: a car. 4x4. van or motorbike
3.There are no acceptance criteria relating to how quick the booking process should be
4.How confirmation is to be sent for payment and space number, and other important details, have not been specified
5.A stub will be needed to test the payment method
Which pair of requirements engineering techniques are you MOST LIKELY to have used to uncover these issues' SELECT ONE OPTION
- A. Storyboards and Personas
- B. Personas and Diagrams
- C. Diagrams and Story Mapping
- D. Story Mapping and use Cases
正解：A
解説：
The most likely pair of requirements engineering techniques used to uncover the issues mentioned with the user story would be "Storyboards and Personas." This approach allows for a visual and persona-based exploration of how different users (such as drivers of different vehicle types and disabled drivers) would interact with the system. This technique helps in uncovering varied user needs and ensuring that all critical user interactions are considered during the development process.
質問 # 79
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. 60%
- B. 80%
- C. 75%
- D. 67%
正解：D
解説：
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.
質問 # 80
Which of the following test categories would best characterize a test designed to confirm that the data backup tapes stored offsite by a bank can be retrieved and loaded within the business process service level agreement?
- A. Security testing
- B. Hazard testing
- C. Continuity testing
- D. Reliability testing
正解：C
解説：
Testing that focuses on confirming that data backup tapes can be retrieved and loaded within specified service levels is classified as Continuity Testing. This type of testing ensures that business processes can continue after a disruption, such as data loss or system failure.
* Explanation: Continuity testing specifically addresses scenarios where operational capacity must be restored and verified within business continuity planning frameworks, such as disaster recovery processes.
質問 # 81
Consider the code fragment provided below:
How many test cases are needed for the code fragment lines 26 - 37 to achieve 100% modified condition/decision coverage?
- A. 2 test cases
- B. 8 test cases
- C. 4 test cases
- D. 6 test cases
正解：C
解説：
Modified condition/decision coverage (MC/DC) requires each condition in a decision to be shown to independently affect the decision's outcome. For the code fragment provided, we have three independent conditions that need to be evaluated both as true and false. The minimum number of test cases needed to satisfy MC/DC for three conditions is four, which would allow each condition to be shown to independently affect the outcome of the decision.
質問 # 82
Installability testing is usually conducted during which stage in the application's SDLC and usually includes which other types of testing?
- A. System testing, with functionality and usability testing
- B. Acceptance testing, with usability and accuracy testing
- C. Integration testing, with functionality and performance testing
- D. Unit testing, with security and performance testing
正解：A
解説：
Installability testing is usually conducted during the System Testing stage of the SDLC. It typically includes testing the installation process of the software to verify that it installs correctly across various systems and configurations. This type of testing often overlaps with functionality testing to ensure all functions are available post-installation, and usability testing to ensure that the installation process is intuitive and user-friendly.
* Explanation: System testing encompasses a broad spectrum of testing practices intended to validate the software in its entirety, ensuring it meets the specified requirements and is ready for operation.
質問 # 83
Consider the pseudo code for the Price program:
Which of the following statements about the Price program describes a control flow anomaly to be found in the program?
- A. The Price program contains no control flow anomalies.
- B. The Price program contains an infinite loop.
- C. The Price program contains unreachable code.
- D. The Price program contains data flow defects.
正解：B
解説：
The pseudo code provided for the Price program shows a potential for an infinite loop due to the way the 'Del_Charge' variable is being manipulated. The loop is set to continue 'WHILE Del_Charge > 0', and within the loop, 'Del_Charge' is initially set to 5 and then potentially decreased by 2 if 'Sale_Value > 60000'. However, at the end of each loop iteration, 'Del_Charge' is increased by 1. This means that if 'Sale_Value' is not greater than 60000, 'Del_Charge' will not decrease and will instead increment indefinitely, causing an infinite loop. Even if 'Sale_Value' is greater than 60000, the decrement by 2 could be negated by the subsequent increments if the loop runs enough times, potentially leading to an infinite loop situation. There is no guaranteed exit condition once the loop is entered, which is a control flow anomaly.
質問 # 84
......
CTAL-TTA合格させる試験問題集には更新されたのは2024年：https://www.passtest.jp/ISTQB/CTAL-TTA-shiken.html
無料CTAL-TTA試験問題集でお手軽に試験合格させる：https://drive.google.com/open?id=1lzK-7f36HBPsdBfxvXiuMoiTvuUX6dGm