CTFL Block01 - Certifica2IT

Question 1 of 10

1. Which of the following statements is one of the twelve core agile manifesto values?

A.Deliver working software frequently, at intervals of between a few months to a few years, with preference to the longer time scale.

B.Simplicity the art of maximizing the amount of work not done - is essential.

C.The best architecture, requirements and designs emerges from teams free from all management control

D.The most efficient and effective method of conveying information to and within a development team is by using written documentation.

Question 1 of 10

Question 2 of 10

2. Which of the following statements about agile software project is true?

A.Communication, simplicity, feedback, courage and respect are key pillar of Kanban to guide development.

B.In Kanban transparency of content and progress of tasks is usually visualize of the active task for example on public whiteboard.

C.Scrum is agile management framework that defines three roles : The... master and development team (Scrum Master, Product Owner, Development Team)

D.Scrum does not provide guidance on how development has to be done in a Prescribes the adoptions of specific testing techniques.

Question 2 of 10

Question 3 of 10

3. Which of the following statements about iteration and release planning is true?

A.a) During release planning, testers establish and prioritize the user stories of the release, and then participate in the quality risk analysis for these stories.

B.Release planning defines and re-defines the product backlog and provides the basis for a test approach and test plan spanning all iterations.

C.During release planning, testers add vales by breaking down user stories in the task (Particularly testing tasks)

D.Release plans cannot change as Agile project proceeds, but iteration plan may change to accommodate new needs.

Question 3 of 10

Question 4 of 10

4. Which of the following would you expect most likely to be an advantage of the whole-team approach?

A.Improve quality of requirements specification (through examples and automatable tests) when adopting the acceptance test-driver development practice.

B.Eliminating the schedule risk associated with big bank integration.

C.Improved code quality as the result of the refactoring step performed as part of the test-driven-devleopment technique.

D.Providing constant availability of executable software through the iteration for testing, demonstration, or education purposes.

Question 4 of 10

Question 5 of 10

5. Which of the following statements about the whole team approach would you expect most likely to be true?

A.The whole team approach is consistent with the ‘Power of three’ concept for which a user story is the conjunction of three elements (Card, Conversation, Confirmation)

B.The whole team approach tends to advocate the idea of team members being "Generalists" without having keep skills in specific disciplines.

C.The whole team approach is a consensus-based approach for estimating, mostly used to estimate the relative size of user stories.

D.The whole team approach helps to ensure tester, developers and the business work together to ensure that the desired quality level and achieved.

Question 5 of 10

Question 6 of 10

6. Which of the following statements is true?

A.Early and frequent feedback in agile projects provides earlier information about the stability of the software product but not about its quality.

B.Early and frequent feedback in agile projects allows the team to provide customers with products that better meet their requirements sooner. |

C.Early and frequent feedback in agile projects allow the team to find number od defects at the unite test level than in non-agile projects.

D.Early and frequent feedback in agile projects help maintain a uniform distribution of defects through the code and thus avoid defect clustering.

Question 6 of 10

Question 7 of 10

7. Which of the following is describes a direct benefits of early and frequent feedback associated to the adoption of continuous integration?

A.Making quality everyone's responsibility.

B.Reducing the need of conducting retrospective.

C.Eliminating and isolating code quality problems early.

D.Detecting and isolating code quality problems early.

Question 7 of 10

Question 8 of 10

8. Consider the agile project aimed at developing a test management tool. This tool allows test managers to generate reports for test analysis test design and test execution phases in traditional phases in traditional projects. Consider the following user story of this agile project : "As a test manager who is looking at a progress report, | want to be able to print this progress report, so that | can keep a hard copy for my daily records" for this user story the following acceptance criteria is define :" Given that lama test manager looking at progress report, whin | click the 'Print' button, Then the progress report should be printed" Based only on the given information, which of the following would you expect most likely to be true?

A.Both the user story and acceptance criterion are expressed in adequate from, but the user story does not describe functional that is valuable to the user.

B.During the convention, the acceptance criterion should not be discussed since it described using the given-when-then template.

C.During the convention, the neeed to update the acceptance criterion by specifying that a date stamp be visible on the printout could emerge.

D.Both the user story and the acceptance criterion are expressed in adequate from, but the user story is not testable.

Question 8 of 10

Question 9 of 10

9. Which of the following statements about retrospective is true.

A.All of the improvements identified an agile retrospective must be inalementsed as soon as possible during the next iteration.

B.Metrics such as bumdown charts, velocities and number of stories completed, could be effectively used during agile retrospective for process management.

C.Agile retrospectives should focus exclusively as improving negative aspects, without wasting time is discussion what worked well during the iteration.

D.An agile retrospective should be held at the end of an iteration only when the number of story points completed by the team in that iteration is lower than the team velocity.

Question 9 of 10

Question 10 of 10

10. What of the following describes the frequency with which usually all changes made to the software are managed and all changes components are integrated regularly in a continuous iteration process.

A.At least once a month.

B.At least once a day.

C.At least once per iteration.

D.At least once a week.

Question 10 of 10

Block 01