[2025年06月03日] 完全版最新のCTAL-ATT問題集で100%カバー率問題と解答があなたをリアル試験で合格させる
最新CTAL-ATT試験問題集で有効最新の問題集
ISQI CTAL-ATT（ISTQBアドバンストレベルアジャイルテクニカルテスター）試験は、アジャイル開発環境におけるソフトウェアテスターの技術的なスキルをテストし、検証するために設計された認定プログラムです。この試験は、ISTQB Foundation Level認定を既に取得し、ソフトウェアテストに2年以上の経験を持つ個人を対象としています。CTAL-ATT認定は、グローバルに認められ、ソフトウェア開発業界の雇用主から高く評価されています。
CTAL-ATT試験は、アジャイル開発の経験を有するテストプロフェッショナルが、キャリアを進め、その分野での専門知識を証明するために理想的な試験です。これは、アジャイル開発の原則と実践に深い理解が必要であり、アジャイルテストツールと技術に対する実践的な経験も必要とされる厳しい試験です。CTAL-ATT試験に合格することは、テストプロフェッショナルにとって重要な成果であり、求人市場での新しい機会を開くことができます。
ISQI CTAL-ATT（ISTQBアドバンストレベルアジャイルテクニカルテスター）試験は、アジャイルテストのスキルを向上させたいソフトウェアテストの専門家を対象とした認定プログラムです。これは、国際的に認められた認定であり、個人のアジャイルソフトウェアアプリケーションのテストに関する知識と熟練度を確認します。この認証は、ソフトウェアテストのバックグラウンドを持ち、アジャイル手法のスキルを向上させたい専門家に適しています。
質問 # 27
You are testing a large e-commerce system for household goods that is being implemented using Agile methodologies You are currently working on deriving tests for stories that are implementing the following epic.
As a customer I want to use the e-commerce system, so that I can have my purchased goods delivered to my house.
The story you are currently working on is:
As a customer I want to be told when my items will be delivered, so I can plan to be home.
You have been given the following charter that was proposed by another tester for testing this story Login as a customer, buy enough of each item to qualify for free shipping for each item checkout and verify that no shipping fee has been added.
What is the main flaw in this charter?
- A. The actions of the user are not clearly stated in the charter
- B. It does not cover the mam functionality of the user story
- C. It focuses on the delivery company instead of the activities of the user
- D. The expected results are not defined
正解：B
解説：
The main flaw in the proposed test charter is that it does not cover the main functionality of the user story. The user story focuses on the customer wanting to be informed about the delivery time of their items so they can plan to be home. The proposed charter only tests for the absence of a shipping fee and does not address whether the system provides the customer with the delivery time information.
References = The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of aligning test charters with the user story's main functionality to ensure that tests provide adequate coverage12. It is crucial in Agile methodologies to create and evaluate testable acceptance criteria that reflect the user story's objectives12.
質問 # 28
Which of the following is an expected benefit of using storyboards to help analyze user stories and epics?
- A. They help to identify the different types of users who will use that piece of functionality
- B. They help to visualize stories to help categorize them into areas of functionality
- C. They help to ensure adequate user group coverage in testing
- D. They help to expose stakeholders or groups of stakeholders who might have been forgotten
正解：B
解説：
Storyboards are a visual tool used in Agile methodologies to represent and analyze user stories and epics.
They provide a sequential depiction of interactions, which aids in understanding and categorizing functionalities.
* Visualization of Stories: Storyboards offer a visual representation of user interactions, making it easier to categorize stories into different functional areas. This visualization helps teams understand the flow and grouping of functionalities within the system.
* Categorization into Functional Areas: By depicting user interactions and system responses, storyboards assist in organizing user stories and epics into specific categories or modules. This categorization is crucial for planning development and testing activities.
Therefore, option D accurately reflects the benefit of using storyboards in analyzing user stories and epics.
質問 # 29
Which of the following best describes when the test automation suite should be updated in order to keep up with the development of new/changed software?
- A. At the end of each iteration, after the completion of manual testing
- B. During each iteration as the code is received
- C. At the end of each release, during regression testing
- D. At the start of each iteration, during planning
正解：B
解説：
* Agile Development and Automation:Agile methodologies encourage frequent updates to the test automation suite to stay in sync with incremental development. This ensures that testing can validate new changes as soon as they are made.
* Updating During Iteration:Updating the test suite as code is developed allows for immediate feedback on changes, improving efficiency and reducing defect leakage.
* Conclusion:Option D is correct because it aligns with continuous integration and Agile principles.
質問 # 30
You have received this BDD test
Given that a customer enters the correct PIN When they request to make a withdrawal And they have enough money in their account Then they will receive the money And a receipt Which of the following is the user story that best fits this BDD test?
- A. As a customer
I want to deposit money into my account
So that I can collect interest - B. As an ATM
I want to provide services to my customer
So they will be happy - C. As a customer
I want to withdraw money from my account
So that I can buy a present - D. As a bank teller
I want customers to use the ATM
So that I don't have to deal with them
正解：C
解説：
The BDD test scenario provided describes a customer performing a withdrawal transaction after entering the correct PIN and having sufficient funds in their account. The outcome is the customer receiving money and a receipt. This aligns with the user story inoption C, which focuses on the customer's desire to withdraw money for a specific purpose, which is to buy a present. The other options do not match the actions described in the BDD test scenario.
References = The answer is verified based on the ISTQB Advanced Level Agile Technical Tester documents which emphasize the importance of aligning BDD scenarios with the corresponding user stories to ensure that the tests reflect the user's needs and interactions with the system12.
質問 # 31
Why might static analysis be used on an Agile project'
SELECT ONE OPTION
- A. To manually identify potential defects and thus avoid technical debt
- B. To clarify and simplify code design without changing its behavior
- C. To implement a test-driven approach at the component level
- D. To identify the causes of technical debt through the use of tools
正解：D
解説：
Static analysis in Agile projects is utilized to identify potential issues in code that could lead to technical debt.
This process involves using tools to analyze the code without actually executing it, which helps in detecting complex code, potential bugs, and areas of the code that may require refactoring. By identifying these issues early in the development process, teams can address them promptly, thus maintaining code quality and avoiding the accumulation of technical debt that could hinder future development efforts.
References = The ISTQB Advanced Level Agile Technical Tester syllabus includes learning objectives that cover the understanding of static code analysis and its role in identifying defects and technical debt as part of code review processes in Agile projects12.
質問 # 32
**You have received this BDD test:
Given that a customer enters the correct PIN
When they request to make a withdrawal
And they have enough money in their account
Then they will receive the money
And a receipt
Which of the following is the user story that best fits this BDD test?**
- A. As a customer
I want to deposit money into my account
So that I can collect interest - B. As an ATM
I want to provide services to my customer
So they will be happy - C. As a customer
I want to withdraw money from my account
So that I can buy a present - D. As a bank teller
I want customers to use the ATM
So that I don't have to deal with them
正解：C
解説：
* Aligning the BDD Test with the User Story:
* The BDD test specifies a withdrawal operation, including entering a PIN, checking account balance, dispensing cash, and providing a receipt.
* The user story must describe the behavior and motivation of a customer performing this action.
* Analyzing Options:
* A: Describes a deposit operation, which does not align with the BDD test.
* B: Too vague and describes the ATM's role, not the customer's perspective.
* C: Correctly matches the behavior and motivation of the withdrawal process.
* D: Focuses on the bank teller, which is irrelevant to the BDD test.
References:Aligned with ISTQB principles emphasizing the importance of user stories that closely match BDD test scenarios.
質問 # 33
Your Agile team is developing a web-based system that will allow users to browse and buy online from a store's shopping catalogue. Continuous Integration has been implemented and technically it is working well, running several times per day, but each run is taking almost as much time as the team is prepared to allow. It is clear that after a few more iterations, as the number of tests needed grows with the product, it will be taking too much time.
Which of the four options contains a pair of solutions that will BOTH help to solve this problem?
a.Only include unit and component integration tests in the automated Cl runs.
b.Schedule low priority tests to be the first ones executed in each run, in order to provide rapid build verification.
c.Reduce the extent to which the automated tests go through the user interface, using technical interfaces instead.
d.Reduce the number of Cl cycles run each day.
e.Select a subset of automated tests for the daytime Cl runs, and run as many of the other tests as possible in an overnight cycle.
SELECT ONE OPTION
- A. d and e
- B. c and e
- C. a and c
- D. b and d
正解：B
解説：
The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of optimizing Continuous Integration (CI) processes in Agile environments. Option C suggests reducing the extent to which automated tests interact with the user interface and instead using technical interfaces, which is often faster as it bypasses the GUI layer. Additionally, running a subset of tests during the day and the rest overnight can help manage the CI process without overloading the system during peak hours. These strategies align with the best practices for maintaining efficient CI cycles and ensuring that the CI process remains sustainable as the number of tests grows with the product.
References = The ISTQB Advanced Level Agile Technical Tester documents and training resources provide guidelines on test automation approaches and continuous deployment and delivery, which are relevant to optimizing CI processes12. Moreover, best practices for continuous testing in Agile suggest prioritizing tests that provide fast feedback and running extensive test suites outside of peak hours3.
質問 # 34
The following user story has been written:
As a paying hotel guest
I want to see the charges that have been added to my bill
So that I can monitor my expenditure and know In advance how much I will have to pay when I check out The notes that have been added to It mention that It must be possible for the guest to get a printout of the bill, see It In a variety of currencies and set a flag in the hotel's billing system against any Item that they wish to challenge.
The following acceptance criteria have been defined:
1.The user shall be able to choose from the most commonly-used currencies.
2.The application must be accessible on most mobile platforms as well as on the hotel room's smart TV.
3.The hotel manager must be notified whenever a bill item is flagged by a hotel guest.
4.End-to-end response time for any individual request submitted by a user must not exceed 7 seconds.
Applying the INVEST technique to this user story, including its acceptance criteria, which of the following statements is correct?
SELECT ONE OPTION
- A. The Testable and Small criteria of INVEST have not been satisfied
- B. The INVEST criteria have all been satisfied by this epic
- C. The Testable and Negotiable criteria of INVEST have not been satisfied
- D. The Negotiable and Small criteria of INVEST have not been satisfied
正解：D
解説：
The user story provided is quite broad and encompasses multiple functionalities, which suggests it is more of an epic than a small, deliverable user story. The INVEST criteria for Agile user stories require that stories be Independent, Negotiable, Valuable, Estimable, Small, and Testable. In this case:
* Independent: This user story seems to have dependencies, as the ability to print the bill, view it in different currencies, and flag items are likely interconnected functionalities.
* Negotiable: The user story provides specific solutions rather than outlining the problem to solve, which limits the negotiation on how to implement the solutions.
* Valuable: The story does provide value to the hotel guest, which is clear.
* Estimable: With the information provided, the development team can likely estimate the effort required.
* Small: The story is not small; it covers multiple features that probably cannot be delivered in a single iteration.
* Testable: The acceptance criteria are testable, although they are quite detailed and prescriptive.
References = The explanation is based on the INVEST criteria as described in Agile methodologies1234. The criteria are used to assess the quality of a user story, ensuring it is well-defined and suitable for Agile development practices. The user story in question does not fully meet the 'Negotiable' and 'Small' criteria, which is essential for maintaining flexibility and delivering incremental value in Agile projects.
質問 # 35
"As the leader of the marketing department, I want to have a content management system so that my employees can edit and provide quality content to the readers" Which of the following requirements engineering techniques would be the MOST effective for identifying and prioritizing user stories for the given Epic?
- A. Storyboarding
- B. Defining Personas
- C. Class Diagrams
- D. Use Cases
- E. Story mapping
正解：A、E
質問 # 36
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
正解：B
解説：
Exploratory testing is a type of testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the quality of his/her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project. While exploratory testing can be highly effective in certain contexts, for safety-critical systems, it is generally not recommended. Safety-critical systems require a high degree of assurance and predictability that each component of the system behaves as expected under all circumstances. Manual black-box tests, which are more structured and can be thoroughly planned and documented, are preferred in these scenarios to ensure comprehensive coverage and traceability.
References = The ISTQB Advanced Level Agile Technical Tester syllabus and training materials provide guidance on the appropriate use of different testing techniques in various contexts, including the recommendation of structured manual black-box testing over exploratory testing for safety-critical systems1234.
質問 # 37
When test cases are re-run after refactoring, what should always be verified?
- A. That tests that have now been made redundant are removed from the test set
- B. That they provide better logging than before
- C. That the branch coverage is the same or increased
- D. That they provide the same results as before
正解：D
解説：
* Purpose of Test Case Refactoring:
* Refactoring focuses on improving the structure of test cases without changing their behavior.
* Key Verification After Refactoring:
* Tests must produce the same results as before to confirm that refactoring has not altered functionality or introduced defects.
* Analyzing the Options:
* A: Branch coverage may change during refactoring, but consistent results are the primary focus.
* B: Improved logging is desirable but not a critical verification.
* D: Redundant test removal is unrelated to verifying unchanged behavior.
References:Aligned with ISTQB principles emphasizing consistency in test results after refactoring.
質問 # 38
The following user story has been developed:
As a customer of Alpha Airways who has booked a flight
I want to access the flight reservation
So that I can update the booking details
Which BDD scenario written in Gherkin format correctly applies to this user story?
SELECT ONE OPTION
- A. Given that the logged-on user is a customer of Alpha Airways
When that user enters their surname correctly
Then they are able to see all flights currently booked so that they can select which flight they want to update - B. Given that a customer has booked a flight with Alpha Airways
When that customer enters their surname and the flight number OR enters their customer ID and the flight number for this reservation Then they are taken to the booking details for that flight so that they can update the booking details - C. Given that a customer has booked a flight with Alpha Airways
When that customer enters their surname AND enters the flight number for this reservation Then the booking details for that flight are displayed - D. Given that a customer has booked a flight with Alpha Airways
When that customer enters the correct surname and flight number for this reservation Then the booking details for that flight are displayed ELSE an appropriate error message is presented
正解：D
解説：
The correct BDD scenario for the given user story is option C, which aligns with the principles of Behavior-Driven Development (BDD) and the Gherkin syntax. This scenario clearly specifies the context (Given), the action (When), and the outcome (Then), along with handling alternate flows (ELSE). It ensures that the customer can access and update their booking details only if they provide both the correct surname and flight number, which is a common practice for verifying a customer's reservation. This scenario also includes an error handling path, which is essential for a comprehensive test case.
References = The ISTQB Advanced Level Agile Technical Tester syllabus and related materials emphasize the importance of creating testable acceptance criteria for user stories using requirements engineering and test techniques, which include the formulation of BDD scenarios in Gherkin format123.
質問 # 39
The following User story is being developed using the 8DD approach:
As a Purchasing Manager
i want to see a list of all Purchase Orders placed so far this month with their total value So that I can control the amount of money being spent Which scenario is BOTH written in correct Gherkin format AND is appropriate for this User Story9 SEI ECT ONE OPTION
- A. Given that three Purchase Orders with a total value of £21.75 have been placed so far this month AND the Purchasing Manager has navigated to the Purchase Order Reporting page When the Purchasing Manager clicks the button 'List of Purchase Orders placed this month' Then the 3 orders and their total value of £21.75 are displayed
- B. Given that three Purchase Orders with a total value of £21.75 have been placed so far this month When the Purchasing Manager requests the list of Purchase Orders placed this month Then the appropriate details are displayed
- C. Given that I am a Purchasing Manager AND three Purchase Orders with a total value of £21.75 have been placed so far this month When I request the list of Purchase Orders placed this month Then all orders and their total value of £21.75 are displayed
- D. Given that three Purchase Orders with a total value of £21.75 have been placed so far this month When the Purchasing Manager requests the list of Purchase Orders placed this month Then the 3 orders and their total value of £21.75 are displayed
正解：D
解説：
Option D is written in correct Gherkin format and is appropriate for the User Story. It clearly states the precondition (three Purchase Orders with a total value of £21.75 have been placed), the action taken by the Purchasing Manager (requesting the list of Purchase Orders placed this month), and the expected outcome (the
3 orders and their total value of £21.75 are displayed). This scenario directly addresses the Purchasing Manager's desire to see a list of all Purchase Orders placed so far this month with their total value, which aligns with the User Story's goal of controlling the amount of money being spent.
References = ISTQB Advanced Level Agile Technical Tester documents and Training resources12.
質問 # 40
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. Story Mapping and use Cases
- B. Personas and Diagrams
- C. Storyboards and Personas
- D. Diagrams and Story Mapping
正解：C
解説：
In Agile development, requirements engineering techniques are crucial for understanding and defining user needs and system requirements. The issues identified in the user story suggest the use of Personas and Storyboards. Personas are fictional characters created based on user research to represent different user types within a targeted demographic, attitude, and behavior set. They help in understanding various user needs and experiences, which is reflected in issue 1 and 2. Storyboards, on the other hand, are visual representations of a user's interaction with the product, providing a narrative of how the product is used. They help in visualizing the process and identifying any missing elements, such as the lack of specified acceptance criteria for the booking process speed (issue 3) and the details on how confirmation is sent (issue
4). The need for a stub to test the payment method (issue 5) also aligns with the storyboard technique, which can help visualize the integration points and dependencies.
References = The ISTQB Advanced Level Agile Technical Tester syllabus and study resources provide insights into various requirements engineering techniques and their application in Agile environments12. These resources emphasize the importance of understanding user stories and acceptance criteria, which are key to uncovering the issues mentioned34567.
質問 # 41
Why is it important to refactor test cases to make them easier to understand?
- A. Because the observable behavior of the test case will change and the product owner needs to be able to clearly see what the behavior should be
- B. Because developers need to use them for performance testing
- C. Because they will be used as the code-under-test changes, so they need to be easy for other testers to understand and modify
- D. Because users will apply them as use cases for UAT and need to be able to determine the main path and alternate paths
正解：C
解説：
* Refactoring Test Cases:
* Refactoring improves test case readability and maintainability, ensuring they can be understood and updated as the system evolves.
* In Agile, where code changes frequently, clear test cases are essential for quick adaptation and collaboration among testers.
* Analyzing the Options:
* A: Developers may not necessarily use these test cases for performance testing.
* C: Users performing UAT focus on business scenarios, not technical test cases.
* D: Test cases are for internal team use; product owners typically review acceptance criteria or feature behavior.
* B: Correctly identifies the importance of refactoring for maintainability and collaboration as the system changes.
References:Aligned with ISTQB Advanced Agile Technical Tester syllabus, which highlights the need for test case clarity to support agile practices and team collaboration.
質問 # 42
You are developing a test automation suite for an agile project and want to include as much coverage as possible Unfortunately one of the critical web services (e-commerce checkout) is not scheduled for completion until the later iterations Which of the following would be a good option to allow you to progress with your end-to-end test automation without creating too much extra work?
- A. Use a service virtualization tool to create a virtualized service to be used by the test automation
- B. Use a service from a legacy product and integrate it with the system to allow use by the test automation
- C. Have the automation create a stub to replace the service for each execution and destroy the stub after execution is complete
- D. Write the missing web service yourself and then hand over that code to the developers for further refinement
正解：A
質問 # 43
You are testing a new feature in the current iteration. The feature is supposed to take the input of a name and return the number of characters in the name. This information is used by another feature that will determine the size needed on a form. The acceptance criteria state the following
1) a name of up to 30 characters should be accepted
2) standard error processing should be in place to limit user errors
The developers are using TDD and you have asked to see their tests. This is what they gave you
When yourun your manual tests you are finding that when you use the following inputs you get the associated results:
From these results what can you conclude about the TDD process?
- A. The tests are insufficient and need to include more options
- B. The developers are not running the tests prior to releasing the code
- C. The story needs to be enhanced to include the capabilities that are causing errors
- D. The tests cannot be passing
正解：A
質問 # 44
Your organization has been making animal food dispensers for free-range chickens and has been using a combination of test automation exploratory testing and some black-box testing on all products. The company has been using the following approach to the testing of the high-risk items:
Exploratory testing = 85%
Black-box testing = 15%
Test automation = coverage goal is 25% but time is only allocated to automation if no other testing is needed, so the coverage is currently about 5% and the automation suite is run only infrequently.
The company has decided to modify their product and use it for pill dispensing for pharmacies Regardless of the mechanical challenges of this modification you now have to determine how testingshould be adjusted for this safety critical application Which of the following would follow the guidelines in the syllabus for the testing approach for the high-risk items?
- A. Exploratory testing = 85%
Black-box testing = 15%
Test automation = 25% coverage executed infrequently - B. Exploratory testing = 15%
Black box testing = 85%
Test automation = 25%, executed for every code release - C. Exploratory testing = 50% Black box testing = 50%
Test automation = 50% coverage executed before every production release - D. Exploratory testing = 25% Black-box testing = 75%
Test automation = 75% coverage executed for every code release
正解：D
解説：
For a safety-critical application like a pill dispenser for pharmacies, it is crucial to ensure that the testing approach is rigorous and thorough. The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of test automation, especially for high-risk items, to ensure consistent and extensive coverage.
Therefore, increasing test automation to 75% coverage and executing it for every code release aligns with the guidelines for testing safety-critical applications. This approach ensures that any changes or additions to the code are immediately and thoroughly tested, which is vital for maintaining the integrity and safety of the application. Additionally, the balance between exploratory testing and black-box testing allows for both creative unscripted tests and specification-based tests to ensure comprehensive test coverage.
References = ISTQB Advanced Level Agile Technical Tester documents and Training resources12.
質問 # 45
When test cases are re-run after refactoring, what should always be verified'?
- A. That tests that have now been made redundant are removed from the test set
- B. That they provide better logging than before
- C. That the branch coverage is the same or increased
- D. That they provide the same results as before
正解：D
質問 # 46
Summarize the characteristics of test automation in relation to development projects.
- A. In large projects, there is usually one best solution that fits all needs, and so. on dedicated test automation strategies fits best
- B. Test automation supports the goals of an iteration directly, e.g., by reducing the regression risk associated with stability of the system
- C. Test automation can play an important role in test environment configuration and test release acquisition
- D. Supportive test automation effort must be done in the teams of the iteration teams themselves
正解：C
質問 # 47
You are testing a large e-commerce system for household goods that is being implemented using Agile methodologies You are currently working on deriving tests for stories that are implementing the following epic.
As a customer I want to use the e-commerce system, so that I can have my purchased goods delivered to my house.
The story you are currently working on is:
As a customer I want to be told when my items will be delivered, so I can plan to be home.
You have been given the following charter that was proposed by another tester for testing this story Login as a customer, buy enough of each item to qualify for free shipping for each item checkout and verify that no shipping fee has been added.
What is the main flaw in this charter?
- A. The actions of the user are not clearly stated in the charter
- B. It does not cover the mam functionality of the user story
- C. It focuses on the delivery company instead of the activities of the user
- D. The expected results are not defined
正解：B
解説：
The main flaw in the proposed test charter is that it does not cover the main functionality of the user story.
The user story focuses on the customer wanting to be informed about the delivery time of their items so they can plan to be home. The proposed charter only tests for the absence of a shipping fee and does not address whether the system provides the customer with the delivery time information.
References = The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of aligning test charters with the user story's main functionality to ensure that tests provide adequate coverage12. It is crucial in Agile methodologies to create and evaluate testable acceptance criteria that reflect the user story's objectives12.
質問 # 48
How does static code analysis help reduce technical debt?
- A. It can remove the need for unit tests and will help improve the efficiency of the build process
- B. It can remove the need for code reviews and speed up the development process
- C. It can identify inefficiencies, complexities and insecure code which can then be fixed by the developer
- D. It can improve the efficiency of the developer as they are writing the code
正解：C
解説：
Static code analysis is a method used to automatically scan and analyze the source code for potential issues. It helps reduce technical debt by identifying inefficiencies, complexities, and insecure code. These issues, once identified, can be addressed by developers, leading to improved code quality and maintainability. This process aids in preventing the accumulation of technical debt, which can occur when problematic code is left unaddressed and compounds over time.
References = The ISTQB Advanced Level Agile Technical Tester documents outline the importance of static code analysis in identifying defects and technical debt as part of a code review process12. It is emphasized that this analysis is crucial for maintaining code quality and reducing technical debt in an Agile environment31.
質問 # 49
"As the leader of the marketing department, I want to have a content management system so that my employees can edit and provide quality content to the readers" Which of the following requirements engineering techniques would be the MOST effective for identifying and prioritizing user stories for the given Epic?
- A. Defining Personas
- B. Class Diagrams
- C. Storyboarding
- D. Use Cases
- E. Story mapping
正解：E
解説：
Story mapping is the most effective requirements engineering technique for identifying and prioritizing user stories related to the epic mentioned. It allows the team to visualize the entire customer journey, which is crucial for a content management system that aims to enhance the content editing and publishing process. By mapping out the user stories, the team can see how they fit into the overall system, prioritize them based on the value they provide to the end-users, and ensure that all necessary functionalities are covered.
References = The ISTQB Advanced Level Agile Technical Tester materials discuss the use of various requirements engineering techniques in an Agile context. Story mapping, in particular, is highlighted as a valuable method for organizing and prioritizing user stories to create a shared understanding among the team members123.
質問 # 50
Which of the following correctly describes positive characteristic of unit tests?
- A. A unit test should be written against large and complex code structures to get fast and feedback of the code quality
- B. Unit test can be derived from the given epics and existing code of the test object
- C. While refactoring, the redesign of the unit test to adapt to the changed code is crucial
- D. Unit tests should be independent from system components other than the one to be tested
正解：D
質問 # 51
......
無料セールまもなく終了！100%有効なCTAL-ATT試験：https://www.passtest.jp/ISQI/CTAL-ATT-shiken.html
検証済みCTAL-ATT試験解答合格確定させる：https://drive.google.com/open?id=1XGx5ZbTO5PJkXAz1kj3E4AGBLFof_Z8D