Download ISQI CTFL-AT Mock Test Study Material [Q19-Q37]

Download ISQI CTFL-AT Mock Test Study Material [Q19-Q37]

March 31, 2024 latestexam 0 Comments

Rate this post

Download ISQI CTFL-AT Mock Test Study Material

CTFL-AT Questions Prepare with Learning Information

NEW QUESTION 19
Which two of the following statements are CORRECT with regards to test automation on agile projects?
1) Every test developed for past iterations is kept and executed as part of a regression suite for each new release of code.
2) It would be very difficult to ensure high quality in an agile project without test automation.
3) Automated acceptance tests are run regularly as part of the continuous integration full system build.
4) Automated regression suites are only run for the final release of code.
5) In agile projects, the results from automated acceptance tests provide feedback on the overall product quality.

3, 4

2, 5

1, 3

2, 3

NEW QUESTION 20
You are developing the code that controls an industrial Espresso machine which will be operated by waiting staff in restaurants.
The machine is rather complicated and has lots of switches and buttons, so in the next iteration instructions will be provided to the operator on a small LCD screen.
A User Story for the Operator-Instructions module is as follows:
“As an operator of the Espresso machine, I would like to know how to steam milk, so I can add steamed milk to the coffee.”
The following is a list of risks identified for this story, with assigned probability and impact.

Operators will not read the instructions and will try various switches and buttons until something works.
Probability: Low. Impact: Low

The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High

An untrained customer will attempt to use the coffee machine. Probability: High. Impact: High

A small child may try to steam milk. Probability: High. Impact: Low

Explanation
Risk-based testing is a technique that prioritizes testing activities based on the level of risk associated with each feature or requirement. The level of risk is usually calculated by multiplying the probability and impact of each risk. The higher the risk level, the more testing effort should be allocated to mitigate the risk. In this case, the risk level for each option is as follows:
A). Risk level = Low x Low = Low
B). Risk level = Low x High = Medium
C). Risk level = High x High = High
D). Risk level = High x Low = Medium
Therefore, the highest risk level is C, followed by B and D, and then A.
The User Story for the Operator-Instructions module should be tested according to this risk order, starting with C, then B, then D, and finally A.
Hence, the answer is B, as it is the second highest risk level and should be tested after C.
References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 16; ISTQB Agile Tester Sample Exam2, question 18.

NEW QUESTION 21
What is the definition of agile software development?

Testing carried out informally where no formal test preparation or execution takes place, no recognized test design technique is used and there are no expectations for results.

A group of software development methodologies based on iterative incremental development with self-organizing cross-functional teams who cooperate to define requirements and to implement the solution.

A framework to describe the software development lifecycle activities from requirements specification to maintenance where test planning of the various test levels is done as soon as the test basis is ready

A way of developing software where the test cases are developed, and often automated, before the software under test is developed.

NEW QUESTION 22
Which one of the following is a testable acceptance criterion?

The solution shall support business processes.

The system shall be easy to use.

The response time to confirm a customer submission must not exceed 5 seconds.

The tools for testing are tested before use and are meeting the requirements.

NEW QUESTION 23
Which of the following would provide the MOST independence for testers working with agile teams?

Testers are fully embedded in each Agile team to perform many of the testing tasks.

Testers from an independent test team who do not get involved with the Agile team, but are assigned to do System Testing once all sprints are completed.

Testers from an independent test team are assigned on-demand for the final days of each sprint.

Testers from an independent test team are assigned to the Agile team at the beginning of the project, returning for re-assignment to a new agile team.

NEW QUESTION 24
Consider an online application that allows registered users to pay the annual car tax based on the vehicle’s engine power in kW. Given the following user story:
“As a customer I need the online application to calculate the annual car tax amount that I need to pay for my car:
* If the power of the vehicle is less than 20 kW, then the annual car tax is free
* If the power of the vehicle is more or equal than 20 kW but less or equal than 150 kW, then the annual car tax is 250 Euros
* If the power of the vehicle is more than 150 kW, then the annual car tax is 750 Euros” What is the MOST suitable use of a black-box test design technique for this user story?

Decision table testing. Test the following conditions:
Conditions=registered user logged in; inserted power of the vehicle=20kW; Action=Car tax paid

State transition testing. Test the transitions between the following states:
logging in, inserting the power of the vehicle, making payment, logging out.

Equivalence partitioning. Test the annual car tax value for the following partitions:
[power of the vehicle<20 kW ; 20 kW power of the vehicles150 kW; power of the vehicle>150 kW]

Use case testing
Test the following use case (Actor=registered user):
Pre-condition=registered user logged in
Scenario=registered user inserts the power of the vehicle, making payment and logs out Post-condition=car tax paid and registered user logged out

NEW QUESTION 25
You have been asked to explain to your client how to define acceptance criteria that are fully testable. Which of the following is the BEST EXAMPLE for testable acceptance criteria?

The “ID” field must accept input value of a length between 2 and 10 characters.

The interface to External System shall be specified.

Action “Reopen” must be available only for a user with a specific authorization level.

The program’s icon should be clear and attractive.

Explanation
According to the ISTQB Tester Foundation Level Agile Tester syllabus, acceptance criteria are a set of conditions that a user story must satisfy to be accepted by the customer or stakeholder. Acceptance criteria should be testable, meaning that they can be verified by objective measurements or observations. Testable acceptance criteria should be clear, unambiguous, complete, and consistent. Therefore, option A is the best example for testable acceptance criteria, as it specifies a clear and measurable condition for the input value of the ID field. Option B is not a good example for testable acceptance criteria, as it is vague and does not define any specific condition or expectation for the interface to External System. Option C is not a good example for testable acceptance criteria, as it is incomplete and does not specify what the specific authorization level is or how it is determined. Option D is not a good example for testable acceptance criteria, as it is subjective and not measurable. What is clear and attractive for one user may not be for another. References: ISTQB Tester Foundation Level Agile Tester syllabus, section 1.1.1, page 7; ISTQB Tester Foundation Level Agile Tester syllabus, section 1.1.2, page 8; ISTQB Tester Foundation Level Agile Tester syllabus, section 3.1.1, page 23; ISTQB Tester Foundation Level Agile Tester syllabus, section 3.1.2, page 24.
3of30

NEW QUESTION 26
Why is regression of software a high risk in agile projects?

Test-driven development means that existing functionality is not considered.

Test automation can cause regression of software in the test environment.

Regression is built into software as a safeguard against unexpected failures.

There is code churn due to change in business needs over several sprints.

NEW QUESTION 27
Iteration planning for Sprint 5 of your current project is complete. The plan for the sprint is to increase performance of the system, which of the following acceptance criteria would you expect for Sprint 5?
1) User access for all roles has been validated.
2) A static analysis tool has been executed for all code.
3) 100% of the existing regression test suite has passed.
4) System is responding in less than 3 seconds, 90% of the time.
5) A new version of internet Explorer has been included.

1, 3

3, 4

4, 5

2, 5

Explanation
The acceptance criteria for a sprint are the conditions that must be met for the user stories to be considered done and deliver value to the customer1. The acceptance criteria should be specific, measurable, achievable, relevant, and testable2. In this case, the plan for the sprint is to increase performance of the system, so the acceptance criteria should reflect that goal. Therefore, the acceptance criteria that would be expected for Sprint
5 are:
100% of the existing regression test suite has passed. This criterion ensures that the system has not introduced any new defects or broken any existing functionality while improving performance3.
System is responding in less than 3 seconds, 90% of the time. This criterion defines a clear and quantifiable performance target that can be verified by testing4.
The other options are not relevant or appropriate acceptance criteria for Sprint 5:
User access for all roles has been validated. This criterion is not related to the performance of the system, but rather to the security or functionality of the system. It might be an acceptance criterion for a different sprint or user story, but not for Sprint 55.
A static analysis tool has been executed for all code. This criterion is not a customer

NEW QUESTION 28
Which of the following sentences related to Risk-based testing is CORRECT?

Risk-based testing fits well in Agile development processes, as risks are analyzed twice – during release and iteration planning.

Risk-based testing does not fit well in Agile development processes, as short iterations mandate short test times.

Risk-based testing does not fit in Agile development processes, as each iteration focuses on limited parts of the product.

Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories.

Explanation
Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories. User stories are short descriptions of features or functionalities that are valuable to the customers or users. They help to define the scope and priority of the work in each iteration. By breaking down the work into user stories, the Agile team can identify the potential risks associated with each story, such as technical complexity, business criticality, or user feedback. The team can then prioritize the testing effort based on the risk level of each story, ensuring that the most important and risky features are tested first and thoroughly. Risk-based testing also helps to optimize the testing time and resources, as the team can focus on testing the most relevant aspects of the software, rather than testing everything equally. References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.2, page 181; ISTQB Foundation Level Agile Tester Sample Exam Questions, Question 2.3.2-1, page 92

NEW QUESTION 29
Which of the following sentences about the integration of development and testing activities in Agile projects is INCORRECT?

While developers develop automated unit test scripts, testers write automated system level tests.

Testers replace developers in writing unit test automation scripts.

Developers write acceptance criteria and test cases, together with testers.

Developers and testers may work as a pair to develop and test a feature.

NEW QUESTION 30
Which of the following is NOT a typical task performed by the tester within an Agile team?

Ensuring all project status meetings are held according to the plan.

Ensuring the appropriate testing tasks are scheduled during iteration planning.

Suggesting improvements in team retrospectives.

Working with business stakeholders to clarify requirements.

Explanation
The tester within an Agile team is not responsible for ensuring all project status meetings are held according to the plan. This is typically a task for the Scrum Master, who facilitates the meetings and ensures that the team follows the Agile principles and practices. The tester within an Agile team is responsible for ensuring the appropriate testing tasks are scheduled during iteration planning, suggesting improvements in team retrospectives, and working with business stakeholders to clarify requirements. These are all tasks that contribute to the quality of the software and the testing process, as well as the collaboration and communication within the team and with the customers. References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.1, page 171; ISTQB Foundation Level Agile Tester Sample Exam Questions, Question
2.3.1-1, page 82

NEW QUESTION 31
Which of the following sentences related to Risk-based testing is CORRECT?

Risk-based testing fits well in Agile development processes, as risks are analyzed twice – during release and iteration planning.

Risk-based testing does not fit well in Agile development processes, as short iterations mandate short test times.

Risk-based testing does not fit in Agile development processes, as each iteration focuses on limited parts of the product.

Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories.

NEW QUESTION 32
Which of the following describes the main purpose of a task management tool in agile projects?

A task management tool is used by team members to share ideas and collaborate on assigned tasks.

A task management tool is used to manage and track user stories, tests and other tasks.

A task management tool is used to store source code and automated tests.

A task management tool allows developers to continuously integrate their code.

NEW QUESTION 33
Which of the following is NOT a typical task performed by the tester within an Agile team?

Ensuring all project status meetings are held according to the plan.

Ensuring the appropriate testing tasks are scheduled during iteration planning.

Suggesting improvements in team retrospectives.

Working with business stakeholders to clarify requirements.

NEW QUESTION 34
Which of the following is the BEST way for a test team to keep its independence when working in an Agile development environment?

Share the Test Strategy with the Agile development team, but not the details of the Test Cases.

Locate the team that develops the test automation framework in a different location to the Agile development team.

Assign testers to be members of the Agile team, but ensure the testers report to a different manager than the developers.

Co-locate only some of the testers with the Agile development team, while the rest of the testers are in a different location.

NEW QUESTION 35
Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?

Having at least once a day an automated build and test process that detects integration errors early and quickly.

Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.

Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.

Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.

NEW QUESTION 36
Which of the following activities are done in release planning?
1) Identifying testable user stories with acceptance criteria.
2) Elaborating the user stories into tasks.
3) Prioritizing the user stories.
4) Creating acceptance tests for the user stories.
5) Analyzing risks for each of the user stories.
6) Performing high level estimation for the release.

Activities 1, 4 and 6

Activities 2 and 4

Activities 2, 3 and 5

Activities 1, 3 and 6

Explanation
Release planning is a process of defining the scope and timeline for an iterative or incremental product development project. It is used in agile or hybrid projects where a mid- to long-term planning of the product or system development or integration is required12. Release planning involves the following activities:
Identifying testable user stories with acceptance criteria. User stories are short descriptions of the features or functionalities that the customer or user wants from the product. Acceptance criteria are the conditions that must be met for the user story to be considered done and acceptable. Identifying testable user stories with acceptance criteria helps to define the scope and quality of the release13.
Prioritizing the user stories. User stories are prioritized based on the value they deliver to the customer or user, as well as the dependencies, risks, and costs associated with them. Prioritizing the user stories helps to determine the order and frequency of the releases13.
Performing high level estimation for the release. High level estimation is a technique to estimate the effort, time, and resources needed to complete the user stories in the release. High level estimation can be done using various methods, such as analogy, expert judgment, planning poker, etc. Performing high level estimation for the release helps to set realistic and achievable goals and deadlines13.
Therefore, activities 1, 3 and 6 are done in release planning. Activities 2, 4 and 5 are done in iteration planning, which is a more detailed and short-term planning of the work to be done in each iteration or sprint13. References: 1: ISTQB Foundation Level Agile Tester Syllabus, Section 2.2, Fundamental Agile Testing Principles, Practices and Processes1; 2: Agile Release Planning in Hybrid and Agile Projects4; 3: How to Create an Agile Release Plan5

NEW QUESTION 37
Which of the following describes the main purpose of a task management tool in agile projects?

A task management tool is used by team members to share ideas and collaborate on assigned tasks.

A task management tool is used to manage and track user stories, tests and other tasks.

A task management tool is used to store source code and automated tests.

A task management tool allows developers to continuously integrate their code.

Explanation
A task management tool is a software application that helps agile teams plan, organize, and monitor their work. A task management tool typically allows the team to create, assign, prioritize, update, and track user stories, tests, and other tasks that are part of the agile project. A task management tool can also provide various views and reports to visualize the progress and status of the project, such as Kanban boards, burndown charts, velocity charts, etc. Some examples of task management tools are Jira, Trello, Asana, and Monday.com12345.
References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.1.1, page 13; ASTQB Agile Tester Certification Resources, Section 2.1.1, page 13.

Loading …

Most Reliable ISQI CTFL-AT Training Materials: https://www.latestcram.com/CTFL-AT-exam-cram-questions.html

Related Certifications

C-TS411-2022 (1)
C_THR95_2205 (1)
C-HCMOD-01 (1)
C_THR95_2111 (1)
C_S4CS_2202 (1)
C_S4CFI_2302 (2)
C-ARSCC-2202 (1)
C_ARSOR_2302 (1)
C-THR96-2305 (1)
C-S4CSV-2208 (1)

Free Cram & Latest Exams Dumps

Download ISQI CTFL-AT Mock Test Study Material [Q19-Q37]

leave a comment Cancel reply

Related Certifications

Recent Posts

Archives

Categories