Free iSQI CTFL-AcT Practice Exam with Questions & Answers

You ask two volunteers to play a part in front of the team. One will try to defend the project and propose positive arguments and ways forward. The other will do the opposite. You then recapitulate the major arguments of both sides and debate them openly with the team.

You draw a staircase with 11 steps, each of them representing a major milestone of the project. The bottom of the stairs corresponds to the first day of the project and the upper step means that the project is released. You locate the present situation in the middle of the stairs. The team is asked to identify and discuss the major steps down and up.

You organize a day out with challenging physical exercises practiced in teams followed by an afterwork dinner and drink. After all, nothing is best for motivation than hard times together, strong common objectives and a promise of good time.

You visualize all remaining major milestones of the project, starting with today and ending with project release. Then, you ask the team to identify and discuss the necessary actions to move forward from the present situation and to reach the milestones.

Beta testing is a synonym for acceptance testing used in specific application domains.

Beta testing should include predefined acceptance test scenarios based on acceptance criteria.

Beta testing allows the product to be tested in realistic business configurations and contexts.

Beta testing is a systematic approach to acceptance testing and provides measurable coverage of the user stories.

Expert reviews help to understand how users interact with a system and what is more or less visible.

Biometrics-based evaluation help to understand retrospectively, how users interacted with the system and to improve it.

Log file analysis performed by usability experts identifies strong points of an interface that attract the user's attention.

Walkthrough and thinking aloud methods can indicate difficulties users experience with certain tasks.

Indicating that the tester should take the role of a novice user can be part of an exploratory test charter.

The test charter is elaborated during the testing session according to test execution results.

Each exploratory test charter is based on a previously defined list of activities that would be interesting to test.

Acceptance testers use the exploratory test charter during the testing session to define the test oracle.

You invite the team members and ask them to design their own (team-wise) emblem representing their values, beliefs, goals, tasks together than a common motto.

You invite every member in turn to describe his/her past experience and his/her major achievements in the organization or in their former job.

You ask every member in turn to write down three things he/she likes and dislikes in the organization and to post them on a wall. A volunteer is then chosen to read randomly some posts that are then discussed with the group.

You draw a staircase with 11 steps, each of them representing a major milestone of the project. The bottom of the stairs corresponds to the first day of the project and the upper step means that the project is released. You locate the present situation in the top of the stairs. The team is asked to identify and discuss the major steps downwards.

Test 1, Test 3

Test 1, Test 2, Test 3

Test 2, Test 4

Test 1, Test 2, Test 4

Identify the requirements / user stories that are not satisfied.

Assess the impact of corrective actions on other parts of the system's implementation.

Analyze the function that failed step by step to identify the cause of the defect.

Check, whether other paths in the business process model perform as intended.

Review of the source code to ensure traceability of user stories to system components.

Verification of the traceability between user stories and test cases to make sure it is up to date.

Checklist-based verification of requirements to ensure their completeness and quality.

Eye tracking to verify the feasibility of previously defined user acceptance tests.

static code analysis

input validation

equivalence partitioning

defect-based test design

Option A

Option B

Option C

Option D