ISTQB CTFL-AT Certified Tester Foundation Level Agile Tester Exam Dumps and Practice Test Questions Set 6 Q101-120

Visit here for our full ISTQB CTFL-AT exam dumps and practice test questions.

Question 101: 

Which of the following best describes the purpose of the Agile principle “working software over comprehensive documentation”?

A) Eliminate all documentation
B) Deliver value to users through functional software
C) Focus solely on coding standards
D) Replace testing with working code

Answer: B) Deliver value to users through functional software

Explanation:

Option A, eliminate all documentation, is a common misunderstanding of this Agile principle. Agile does not advocate for a total removal of documentation because some documentation is necessary to support knowledge transfer, maintainability, and regulatory compliance. However, the principle emphasizes that documentation should be concise and valuable, serving the needs of the team and stakeholders without becoming a bureaucratic burden. Documentation that does not contribute to delivering functional software or supporting decision-making is considered less critical in Agile contexts. Eliminating it entirely would create risks of losing knowledge or making the system harder to maintain over time.

Option C, focusing solely on coding standards, misinterprets the principle by turning attention exclusively to internal code practices. While coding standards are important for maintainability and readability, they do not inherently guarantee that the software delivers value to users. Agile prioritizes outcomes and user satisfaction, so coding practices are part of the process but not the ultimate goal. Emphasizing coding standards at the expense of delivering functional software can lead to “perfect code” that may never reach the user or provide business value.

Option D, replacing testing with working code, is an unsafe and incorrect interpretation. Agile does not suggest that testing is unnecessary; rather, it emphasizes that the primary measure of progress is working software that meets user needs. Testing remains critical to ensure quality, reliability, and alignment with requirements. Ignoring testing would increase risk and likely result in software that appears functional but fails to meet quality expectations or user requirements. Agile principles support integrated testing, automated tests, and iterative feedback to complement working software delivery.

Option B, delivering value through functional software, correctly captures the intent of the principle. Agile emphasizes producing tangible, usable software that stakeholders can evaluate and provide feedback on. Documentation is created as needed but does not overshadow the delivery of functional increments. The focus is on producing results that users can interact with, allowing early feedback, reducing waste, and supporting iterative improvement. This approach ensures that Agile teams remain aligned with customer needs and business priorities, achieving a balance between necessary documentation and actual software value.

Question 102: 

Which Agile artifact represents the prioritized set of user stories for the entire project?

A) Sprint Backlog
B) Product Backlog
C) Burndown Chart
D) Definition of Done

Answer: B) Product Backlog

Explanation:

Option A, Sprint Backlog, is limited to the scope of a single sprint. It contains only the work that the development team has committed to complete within that sprint. While it is crucial for sprint execution and tracking daily progress, it does not represent the entire project’s scope or priority order. A Sprint Backlog is derived from the Product Backlog during Sprint Planning and is continually updated as tasks are completed, but it is inherently short-term and tactical.

Option C, Burndown Chart, is a visual representation of progress, typically showing remaining work against time during a sprint or project. While valuable for tracking and managing effort, it does not define or prioritize work items. A Burndown Chart helps teams monitor velocity and completion trends but is an output or measurement tool rather than a repository of requirements. It cannot replace a backlog because it lacks detailed stories, descriptions, and acceptance criteria needed for development.

Option D, Definition of Done, provides a checklist or criteria to determine whether a backlog item is considered complete. While essential for maintaining quality and shared understanding, it is not a collection of user stories. The Definition of Done ensures consistency in completed work but does not help in planning or prioritizing work across the project. It is a governance tool rather than a backlog.

Option B, Product Backlog, is correct because it represents the comprehensive, prioritized set of user stories, features, and enhancements for the entire project. Items are ordered based on business value, risk, dependencies, and customer priorities. The Product Backlog is a living artifact, continuously refined, and used as the primary input for Sprint Planning. It allows teams to focus on delivering the most valuable items first while remaining flexible to changing requirements. This ensures Agile principles of iterative delivery, responsiveness, and stakeholder collaboration are maintained throughout the project lifecycle.

Question 103: 

Which Agile ceremony is used to plan which backlog items will be delivered in the upcoming sprint?

A) Sprint Review
B) Sprint Planning
C) Daily Stand-up
D) Sprint Retrospective

Answer: B) Sprint Planning

Explanation:

Option A, Sprint Review, focuses on inspecting the increment completed in the previous sprint. The team demonstrates working functionality to stakeholders and gathers feedback. While it informs future planning and helps update the Product Backlog, it is not the forum where tasks for the next sprint are formally selected and planned. The primary purpose of the Sprint Review is evaluation and feedback, not detailed planning for upcoming work.

Option C, Daily Stand-up, is a short, daily meeting designed to synchronize team activities, highlight impediments, and maintain transparency. It is not a planning ceremony; it occurs throughout the sprint rather than before the sprint begins. The Stand-up helps teams adapt daily but does not involve selecting backlog items or defining sprint goals in detail.

Option D, Sprint Retrospective, is focused on process improvement. The team reflects on what went well, what did not, and how to improve collaboration and workflow. While insights from retrospectives may influence future sprint planning, this ceremony itself does not establish which backlog items will be delivered or assign tasks for the sprint.

Option B, Sprint Planning, is correct because it establishes the framework for the upcoming sprint. During this ceremony, the team collaborates with the Product Owner to select high-priority backlog items, define tasks, estimate effort, and agree on a sprint goal. This structured planning ensures that the team has a shared understanding of the work, dependencies are addressed, and the scope is achievable. Sprint Planning aligns the team with Agile principles of iterative delivery, transparency, and responsiveness to stakeholder needs.

Question 104: 

Which technique involves designing tests based on models of system behavior?

A) Risk-Based Testing
B) Model-Based Testing
C) Exploratory Testing
D) Ad-hoc Testing

Answer: B) Model-Based Testing

Explanation:

Option A, Risk-Based Testing, prioritizes testing activities based on potential impact, probability of failure, or business criticality. While it guides where to focus test efforts, it does not generate tests automatically based on system behavior models. Risk-Based Testing is a strategy for allocation of resources rather than a method of designing test cases systematically from models.

Option C, Exploratory Testing, relies on the tester’s intuition, experience, and creativity. Testers explore the system without predefined scripts to uncover defects that might be missed in structured approaches. While highly adaptive, it is not derived from formal models of system behavior. The focus is on discovery and learning rather than systematic coverage derived from a model.

Option D, Ad-hoc Testing, is informal, unstructured, and performed without planning or documentation. It lacks repeatability and does not use models to drive test design. Ad-hoc testing can be useful for finding defects quickly, but it does not provide the systematic coverage or formal verification that model-based approaches ensure.

Option B, Model-Based Testing, is correct because it systematically uses models of the system—such as state machines, decision tables, or flow diagrams—to generate test cases automatically or semi-automatically. This approach ensures that tests cover various system behaviors and decision paths efficiently. It reduces manual effort, enhances traceability, and supports early defect detection, aligning well with Agile’s need for rapid, iterative testing and continuous feedback loops. Model-Based Testing is particularly beneficial for complex systems with multiple interdependent behaviors, helping teams achieve both coverage and efficiency.

Question 105: 

Which of the following best describes “story points” in Agile?

A) Absolute hours to complete a task
B) Relative measure of effort or complexity
C) Priority assigned by Product Owner
D) Number of defects

Answer: B) Relative measure of effort or complexity

Explanation:

Option A, absolute hours, is unreliable in Agile because work duration can vary significantly among team members and across tasks. Using hours as a metric can lead to inaccurate planning, unnecessary pressure, and poor predictability. Story points intentionally abstract away from exact time to focus on effort, complexity, and risk.

Option C, priority assigned by the Product Owner, represents business importance, not effort. While prioritization informs sprint planning and backlog ordering, it does not indicate how difficult a user story is to implement or the resources required. Confusing priority with effort could misguide planning and velocity estimation.

Option D, number of defects, measures quality, not workload. Defect counts do not indicate the size, complexity, or effort of a story and are unrelated to story point estimation. Counting defects alone would not help the team predict velocity or plan sprints effectively.

Option B, relative measure of effort or complexity, is correct. Story points allow teams to estimate work by comparing new stories to previously completed ones, considering complexity, risk, and effort rather than exact time. This facilitates better sprint planning, velocity tracking, and iterative delivery, while embracing Agile’s flexibility. Story points help teams predict delivery, manage capacity, and maintain a shared understanding of workload without rigid adherence to time estimates.

Question 106: 

Which of the following Agile practices emphasizes early involvement of testers in the development lifecycle?

A) Shift-left Testing
B) Regression Testing
C) Load Testing
D) Smoke Testing

Answer:  A) Shift-left Testing

Explanation:

Shift-left Testing is a practice that aims to move testing activities earlier in the software development lifecycle. By involving testers at the very beginning, during requirement analysis and design, this approach allows for early identification of potential issues, which can drastically reduce defect density downstream. Shift-left emphasizes collaboration between developers, testers, and other stakeholders from the outset, ensuring that testability, quality expectations, and acceptance criteria are clearly defined before code is even written. This proactive involvement helps prevent costly rework and supports Agile’s iterative nature, where continuous feedback loops are crucial.

Regression Testing, on the other hand, is performed after code changes have been implemented. Its purpose is to ensure that existing functionality continues to work as expected, rather than to influence development early. While regression testing is critical for maintaining stability in Agile’s frequent releases, it does not facilitate early defect detection or influence the design of features in the way shift-left testing does. It is more reactive than proactive, validating functionality after development, rather than preventing issues from occurring.

Load Testing evaluates how the system performs under heavy user load or high data volume. Although important for performance and scalability, load testing typically occurs later in the lifecycle, often in pre-release or staging environments. It is not aimed at improving code quality from the beginning or at integrating testing into the early development process, making it less aligned with the concept of early involvement of testers emphasized in Agile practices.

Smoke Testing is a preliminary test to check whether the basic functionalities of a build are working. Its purpose is to quickly validate a new build before more detailed testing is performed. While it provides early feedback on build stability, it is a narrow verification activity rather than a collaborative, lifecycle-spanning practice that guides development. It does not replace the holistic benefits of shift-left testing, which focuses on integrating quality activities throughout the development lifecycle.

Shift-left Testing is correct because it embodies the principle of early and continuous quality assurance. By including testers from the very beginning, teams can design better tests, clarify requirements, and prevent defects before they occur. This integration aligns with Agile principles, reduces late-cycle defects, supports iterative delivery, and fosters a culture where testing is not a separate phase but an ongoing collaborative process that enhances both product quality and development efficiency.

Question 107: 

Which Agile ceremony is intended for reflecting on team processes and identifying actionable improvements?

A) Sprint Planning
B) Sprint Review
C) Daily Stand-up
D) Sprint Retrospective

Answer: D) Sprint Retrospective

Explanation:

Sprint Planning is the Agile ceremony where the team defines the work to be completed in the upcoming sprint. It involves prioritizing backlog items, estimating effort, and ensuring the team understands the sprint goal. While this meeting is essential for setting direction, it does not primarily focus on reviewing past performance or identifying ways to improve team collaboration or processes.

Sprint Review is the session where completed work is demonstrated to stakeholders. Its main purpose is to inspect the product increment, gather feedback, and discuss adjustments to the product backlog. Although feedback from this session may indirectly affect processes, it is centered on product outcomes rather than on evaluating the team’s methods or dynamics.

Daily Stand-up is a brief, usually 15-minute, meeting that helps team members synchronize work, share progress, and identify obstacles. This ceremony facilitates daily coordination but is not designed for in-depth reflection on processes, identification of systemic issues, or planning long-term improvements. Its focus is operational rather than evaluative.

Sprint Retrospective is the ceremony specifically dedicated to process reflection and improvement. The team reviews how the sprint went, evaluates the effectiveness of their collaboration, tools, and practices, and identifies actionable improvements for future sprints. This ceremony fosters a culture of continuous improvement, encourages open discussion of challenges, and supports the Agile principle of adapting processes to enhance efficiency and quality. It provides a structured environment for the team to learn from past experiences and implement practical changes.

Sprint Retrospective is correct because it is the formal mechanism in Agile for reflecting on the team’s performance, identifying areas of improvement, and committing to concrete actions. It reinforces continuous improvement, supports team cohesion, and ensures that lessons learned are applied in subsequent sprints, making the development process more effective and aligned with Agile principles.

Question 108: 

Which type of testing focuses on verifying that previously working functionality still works after changes?

A) Unit Testing
B) Regression Testing
C) Exploratory Testing
D) Load Testing

Answer: B) Regression Testing

Explanation:

Unit Testing involves testing individual components or modules of code in isolation to ensure that each unit functions correctly. While crucial for validating the correctness of specific pieces of code, unit testing does not focus on verifying whether previously implemented functionality continues to work after changes elsewhere in the system.

Exploratory Testing is an unscripted, experience-based approach where testers explore the application to find defects. It emphasizes learning, creativity, and discovery rather than systematically verifying that existing functionality remains intact. While exploratory testing can uncover defects in modified areas, it is not designed to validate previously verified functionality in a repeatable way.

Load Testing evaluates system performance under heavy user or data load. Its purpose is to identify bottlenecks and ensure system reliability under stress. Load testing does not verify correctness of existing functionality after changes, so it does not address the core objective of regression testing.

Regression Testing is correct because its primary goal is to ensure that new changes, bug fixes, or enhancements do not unintentionally break existing functionality. In Agile, where frequent releases are common, continuous regression testing helps maintain system stability and confidence in iterative delivery. Automated regression suites complement this approach, enabling quick and repeatable verification of the system’s behavior, reducing risk, and supporting continuous integration and delivery.

Question 109:

Which Agile practice involves merging code frequently into a shared repository with automated testing?

A) Continuous Integration
B) Regression Testing
C) Exploratory Testing
D) Load Testing

Answer:  A) Continuous Integration

Explanation:

Regression Testing verifies that existing functionality remains unaffected by recent changes. While regression testing can be automated, it does not inherently involve merging code or integrating changes frequently. Its scope is verification rather than integration.

Exploratory Testing focuses on discovering defects through unscripted investigation. It does not involve routine integration of code changes or automated test execution in a shared environment.

Load Testing examines how a system performs under stress or high usage. It does not involve frequent code merges or automated integration tests, so it does not align with the continuous integration practice.

Continuous Integration is correct because it is an Agile practice where developers frequently integrate code into a shared repository. Each integration triggers automated builds and tests, providing immediate feedback on integration issues. This practice reduces integration risk, enables early defect detection, and ensures that code is always in a potentially shippable state. It supports Agile principles by promoting collaboration, rapid feedback, and iterative delivery of working software.

Question 110: 

Which ceremony demonstrates completed work to stakeholders for feedback?

A) Sprint Planning
B) Sprint Review
C) Daily Stand-up
D) Sprint Retrospective

Answer: B) Sprint Review

Explanation:

Sprint Planning is for defining what work the team will undertake during the sprint. It does not involve showcasing completed work to stakeholders or collecting feedback. Its focus is on preparation and planning rather than evaluation.

Daily Stand-up is a short team meeting aimed at coordinating daily tasks. It is internal to the team and does not provide a platform for stakeholder feedback or demonstration of deliverables.

Sprint Retrospective focuses on the team’s processes, collaboration, and improvement opportunities. It does not involve stakeholders or demonstration of product increments; instead, it addresses internal process improvement.

Sprint Review is correct because it provides an opportunity to showcase completed work to stakeholders, gather their feedback, and align future work with customer priorities. This ceremony embodies the Agile principle of inspect-and-adapt, ensuring that the product evolves in response to stakeholder input and remains closely aligned with business goals and user expectations.

Question 111: 

Which of the following best describes a “potentially shippable increment”?

A) Partially completed code
B) Fully integrated, tested, and ready for release
C) Test plan document
D) Unstarted backlog item

Answer: B) Fully integrated, tested, and ready for release

Explanation:

Option A, partially completed code, does not meet the definition of a potentially shippable increment because it is incomplete and may contain defects or missing functionality. Partially completed work cannot be delivered to stakeholders or end-users, as it does not provide immediate value or feedback potential. In Agile, the goal is to ensure that increments at the end of a sprint are fully usable, so code that is only partially implemented cannot fulfill this principle. While partially completed code is a step toward delivery, it is not considered an increment that stakeholders can rely on.

Option C, a test plan document, is an important artifact in software development but does not constitute a shippable increment. A test plan may guide the execution of tests and help ensure quality, but it does not deliver functional software. Agile emphasizes delivering working software rather than documentation alone. While documentation supports development, it is not sufficient to be considered potentially shippable because it provides no immediate functionality for users or customers to interact with.

Option D, an unstarted backlog item, clearly does not represent a potentially shippable increment. Backlog items that have not been worked on are theoretical at best—they have not undergone analysis, design, coding, testing, or integration. Delivering value in Agile requires that features be implemented incrementally and iteratively, which means unstarted items cannot provide any business value or feedback opportunities. They remain placeholders in planning and prioritization processes.

Option B is correct because a fully integrated, tested, and ready-for-release increment aligns perfectly with Agile principles. Such an increment has completed all necessary development steps, passed all relevant tests, and met the Definition of Done. This means it is usable by stakeholders and can be released if desired. The potentially shippable increment is central to the iterative delivery model in Agile, as it allows teams to obtain feedback early and frequently, adapt future work accordingly, and continuously provide value. By ensuring increments are potentially shippable, Agile teams maintain transparency, predictability, and focus on delivering working software at the end of every sprint, supporting iterative improvement and stakeholder engagement.

Question 112: 

Which Agile practice emphasizes learning, test design, and execution simultaneously without predefined scripts?

A) Unit Testing
B) Exploratory Testing
C) Smoke Testing
D) Load Testing

Answer: B) Exploratory Testing

Explanation:

 Option A, Unit Testing, focuses on validating individual modules or components of software. Unit tests are predefined and automated, aiming to verify that a specific function or class works as expected. They are essential for regression testing and verifying correctness at a granular level, but they do not involve the simultaneous learning and exploration process characteristic of Agile exploratory testing. Unit tests follow scripts, which limits adaptability to unexpected behaviors.

Option C, Smoke Testing, is a preliminary check to see if the basic functionality of a system works after a new build. While smoke tests are valuable for quickly assessing stability, they are predefined and narrow in scope. They do not involve dynamic learning, creativity, or simultaneous test design, and therefore do not align with the exploratory testing approach, which requires continuous observation and adaptation.

Option D, Load Testing, assesses system performance under heavy usage or stress. It is focused specifically on performance and scalability rather than functionality or defect discovery. Load testing is typically automated and highly structured, leaving little room for the adaptive, creative approach used in exploratory testing. While performance insights are valuable, they do not satisfy Agile’s principle of simultaneous learning and feedback during testing.

Option B is correct because exploratory testing integrates learning, test design, and execution in real-time. Testers actively interact with the system, adapt their testing strategy based on observations, and use their experience and intuition to uncover defects that might not be anticipated by predefined scripts. This approach complements automated testing by targeting areas that require human judgment and creativity. It supports Agile’s iterative process by providing rapid feedback, uncovering unexpected defects early, and enhancing overall software quality while maintaining flexibility and adaptability.

Question 113: 

Which principle prioritizes collaboration with customers over contract negotiation?

A) Responding to change
B) Customer collaboration
C) Working software
D) Individuals and interactions

Answer: B) Customer collaboration

Explanation:

Option A, Responding to change, emphasizes adaptability and the ability to incorporate changing requirements. While critical to Agile, it is more about flexibility than actively engaging with customers. Teams may respond to changes without direct collaboration if they are merely implementing changes dictated externally. This option focuses on the process rather than the principle of stakeholder engagement.

Option C, Working software, prioritizes delivering functional software over documentation or theoretical planning. While this principle is central to Agile, it does not explicitly emphasize interaction with the customer or collaborative decision-making. Working software represents value delivery but not necessarily the partnership aspect of development.

Option D, Individuals and interactions, underscores the importance of team communication and collaboration within the development team. It promotes knowledge sharing, team cohesion, and effective coordination but does not explicitly focus on customer engagement or ongoing stakeholder involvement in decision-making.

Option B is correct because customer collaboration places continuous engagement with stakeholders at the center of Agile practice. It encourages active participation, feedback loops, and iterative alignment with actual business needs. By prioritizing collaboration over contract negotiation, teams ensure that they are delivering features that truly provide value, adjusting priorities dynamically based on input, and fostering a partnership mentality rather than a purely transactional relationship. This principle ensures that Agile development is responsive, user-focused, and capable of producing solutions that reflect real-world requirements.

Question 114: 

Which technique uses system models or decision rules to generate test cases automatically?

A) Risk-Based Testing
B) Model-Based Testing
C) Exploratory Testing
D) Ad-hoc Testing

Answer: B) Model-Based Testing

Explanation:

Option A, Risk-Based Testing, is about prioritizing test activities according to the likelihood and impact of potential failures. While it guides where testing effort should focus, it does not automatically generate test cases using models or system logic. It is a strategic planning approach rather than a method for test case creation.

Option C, Exploratory Testing, relies on the tester’s intuition, experience, and creativity. Testers design and execute tests simultaneously, learning from system behavior to uncover defects. While effective for discovering unexpected issues, it does not utilize predefined models or rules to automatically generate test cases, and it depends heavily on human judgment rather than system-driven logic.

Option D, Ad-hoc Testing, is informal and unstructured. Testers execute tests without prior planning or documentation, often to quickly identify defects in areas they suspect might fail. This approach provides flexibility and creativity but does not systematically generate tests using models or decision rules, and it lacks the repeatability and efficiency of model-based approaches.

Option B is correct because Model-Based Testing uses abstract representations of system behavior, such as workflows, state diagrams, or decision tables, to automatically produce test cases. This ensures thorough coverage of functional scenarios, consistency in test design, and repeatability of tests across iterative development cycles. It is especially valuable in Agile environments, where teams need to efficiently generate reliable test cases for frequent iterations. Automated generation using models reduces human effort, increases accuracy, and supports both exploratory and regression testing needs.

Question 115: 

Which artifact is created and refined continuously to capture all desired features of the product?

A) Sprint Backlog
B) Product Backlog
C) Burndown Chart
D) Definition of Done

Answer: B) Product Backlog

Explanation:

Option A, Sprint Backlog, is specific to a single sprint and contains the tasks selected for immediate completion. It does not capture the overall set of desired features for the product or maintain a continuously evolving perspective on business priorities. Its focus is tactical rather than strategic.

Option C, Burndown Chart, is a visual tracking tool showing work completed versus remaining in a sprint or project. While it provides insight into progress, it does not describe or capture product requirements or features. It supports planning and monitoring but is not an artifact for feature definition.

Option D, Definition of Done, specifies the conditions that must be met for work to be considered complete. While essential for quality and consistency, it does not capture features or guide future development priorities; instead, it ensures that delivered work meets agreed-upon standards.

Option B is correct because the Product Backlog represents a prioritized, continuously refined list of all desired product features, enhancements, and fixes. It is the central repository for requirements in Agile, updated as stakeholders provide feedback, market conditions change, or team insights emerge. Continuous refinement ensures that the most valuable items are delivered first and that planning remains adaptive and transparent. The Product Backlog drives iterative development, facilitates communication between team members and stakeholders, and underpins Agile’s emphasis on delivering incremental value efficiently and predictably.

Question 116: 

Which Agile practice encourages moving testing activities earlier in the development lifecycle?

A) Shift-left Testing
B) Regression Testing
C) Smoke Testing
D) Load Testing

Answer:  A) Shift-left Testing

Explanation:

Option A, Shift-left Testing, is a practice in Agile and DevOps methodologies that emphasizes integrating testing activities early in the development lifecycle, rather than waiting until the later stages of development. The term “shift-left” comes from the concept of moving tasks earlier in the traditional left-to-right project timeline. This practice encourages collaboration between developers, testers, and business stakeholders from the start, ensuring that quality is considered during requirement gathering, design, and coding phases. It supports early defect detection, which reduces the cost and effort associated with fixing issues discovered late in the development cycle. By addressing problems early, teams can avoid cascading issues that may impact multiple components later.

Option B, Regression Testing, involves re-executing previously run test cases to confirm that new code changes have not introduced defects into existing functionality. While regression testing is critical in maintaining software quality, it typically occurs after code changes are integrated and is performed repeatedly during development and release cycles. It does not inherently shift testing earlier in the lifecycle; rather, it is reactive, detecting issues after the code is already implemented. Therefore, regression testing does not fulfill the principle of proactive early defect detection emphasized by shift-left testing.

Option C, Smoke Testing, refers to a basic set of tests run to determine whether a build is stable enough for further testing. It is also called “build verification testing” and is generally performed after a software build is completed. Smoke testing ensures that critical functionalities work and that the system is not broken, but it does not systematically address early defect prevention or involve extensive collaboration between developers and testers. As such, it is not primarily concerned with moving testing activities earlier in the development process.

Option D, Load Testing, is designed to assess how a system performs under expected or peak load conditions. This type of performance testing is usually conducted during later stages of development or in staging environments to validate system scalability, stability, and responsiveness. While it provides important insights into system performance, it does not address the early integration of testing practices or support continuous quality monitoring from the start.

Shift-left Testing is the correct option because it uniquely promotes the proactive engagement of testing and quality practices throughout the entire software development lifecycle. By involving testers from the planning and design stages, defects are discovered and addressed before they propagate, reducing rework and improving overall product quality. This approach aligns perfectly with Agile principles such as iterative delivery, early feedback, and collaboration, making it an essential practice for high-performing Agile teams.

Question 117: 

Which ceremony allows the team to plan work and define the sprint goal?

A) Sprint Planning
B) Daily Stand-up
C) Sprint Review
D) Sprint Retrospective

Answer:  A) Sprint Planning

Explanation:

Option A, Sprint Planning, is an essential Agile ceremony conducted at the start of each sprint. During this meeting, the team selects items from the product backlog to include in the sprint backlog, defines the tasks necessary to complete each item, and establishes the sprint goal. This goal provides a shared focus for the team and serves as a benchmark against which success can be measured. Sprint Planning ensures that all team members have clarity regarding priorities, responsibilities, and expected outcomes, enabling them to plan their work efficiently for the sprint duration.

Option B, Daily Stand-up, is a short, time-boxed meeting held daily to synchronize activities and discuss progress, blockers, and next steps. While it supports coordination and transparency, it is not intended to define the sprint goal or plan the work for the entire sprint. Its focus is on day-to-day collaboration and quick problem-solving, making it a tactical rather than strategic planning activity.

Option C, Sprint Review, is a ceremony held at the end of a sprint to inspect the completed increment and gather feedback from stakeholders. The team demonstrates what has been accomplished, and stakeholders provide input to inform future backlog prioritization. Although this ceremony involves reflection and assessment, it is forward-looking in terms of backlog refinement rather than defining a new sprint goal.

Option D, Sprint Retrospective, is conducted after the Sprint Review to focus on process improvements. The team reflects on what went well, what didn’t, and identifies actions to enhance future performance. While valuable for continuous improvement, it does not involve planning work or selecting backlog items for the upcoming sprint.

Sprint Planning is the correct option because it is explicitly designed to allow the team to plan work and define the sprint goal. It provides structure and alignment, ensuring that team members understand their responsibilities and have a shared objective to guide their efforts throughout the sprint. This ceremony sets the foundation for a focused, coordinated, and successful sprint execution.

Question 118: 

Which Agile practice ensures that integration issues are identified and resolved quickly?

A) Continuous Integration
B) Regression Testing
C) Exploratory Testing
D) Load Testing

Answer:  A) Continuous Integration

Explanation:

Option A, Continuous Integration (CI), is a development practice where code changes are merged into a shared repository frequently, often multiple times a day. Each merge triggers an automated build and test process, allowing teams to detect integration issues as soon as they occur. CI reduces the risk of late integration problems, ensures that software remains in a deployable state, and supports rapid feedback, which aligns well with Agile principles. Early detection of integration defects prevents cascading failures, reduces debugging time, and improves overall software quality.

Option B, Regression Testing, verifies that existing functionality continues to work after code changes. While regression testing is vital for quality assurance, it is not inherently focused on the frequent detection of integration issues. Regression tests are usually run at specific intervals or as part of CI pipelines, but their main purpose is to catch unintended consequences of changes rather than proactively preventing integration conflicts.

Option C, Exploratory Testing, involves simultaneous learning, test design, and execution to uncover defects that scripted tests might miss. While this practice is highly effective for discovering unanticipated issues, it is primarily manual, ad hoc, and less structured for addressing the frequent integration of new code changes. Exploratory testing does not inherently guarantee rapid detection of integration problems.

Option D, Load Testing, evaluates system performance under expected or peak load conditions. Although performance issues can be identified, this type of testing does not focus on integration problems and is typically performed later in the lifecycle or in dedicated environments.

Continuous Integration is the correct answer because it systematically addresses integration challenges by promoting frequent merging, automated builds, and automated testing. This ensures early detection and resolution of conflicts, reduces integration-related risks, and supports the iterative, fast-paced nature of Agile development.

Question 119: 

Which Agile ceremony focuses on collecting stakeholder feedback on completed work?

A) Sprint Planning
B) Sprint Review
C) Daily Stand-up
D) Sprint Retrospective

Answer: B) Sprint Review

Explanation:

Option A, Sprint Planning, occurs at the beginning of the sprint to plan work and set the sprint goal. It is forward-looking and does not involve reviewing completed work or collecting feedback from stakeholders. Its purpose is to ensure alignment on what the team will accomplish during the sprint rather than evaluating outcomes.

Option B, Sprint Review, is the ceremony specifically designed to inspect the completed increment and gather stakeholder feedback. During this meeting, the team demonstrates the working product, receives input on functionality, and discusses potential adjustments for future sprints. This feedback loop is essential for aligning the product with business needs and refining the backlog based on real-world insights.

Option C, Daily Stand-up, is a brief meeting to coordinate daily activities. It focuses on immediate progress, blockers, and next steps, rather than evaluating completed work or collecting stakeholder input.

Option D, Sprint Retrospective, occurs after the sprint and focuses on team processes, collaboration, and performance improvements. While valuable for enhancing team efficiency, it is internally oriented and does not involve external stakeholders reviewing the product.

Sprint Review is the correct option because it provides a structured opportunity for stakeholders to engage with the team, review work done, and provide feedback. This ensures that the product evolves according to stakeholder expectations and helps maintain alignment between development efforts and business priorities.

Question 120: 

Which Agile artifact contains tasks and user stories selected for completion in a sprint?

A) Product Backlog
B) Sprint Backlog
C) Burndown Chart
D) Definition of Done

Answer: B) Sprint Backlog

Explanation:

Option A, Product Backlog, is a comprehensive list of all features, enhancements, and bug fixes for the product. While it serves as the primary source for work to be done, it contains items for the entire project and is not restricted to the current sprint. The Product Backlog is prioritized but does not provide a detailed plan of action for a specific iteration.

Option B, Sprint Backlog, is a subset of the Product Backlog selected during Sprint Planning for completion in the current sprint. It includes detailed tasks, assignments, and planned deliverables, giving the team a clear view of what needs to be accomplished. It is dynamic and may evolve as work progresses, providing transparency and accountability for sprint objectives.

Option C, Burndown Chart, is a visual representation of work remaining versus time. While it helps track progress during a sprint, it is not an artifact containing tasks or user stories itself; rather, it reflects the completion status of items in the sprint backlog.

Option D, Definition of Done, outlines the criteria that must be met for a product backlog item to be considered complete. It ensures quality and consistency but does not contain tasks or user stories to be executed.

The Sprint Backlog is the correct answer because it explicitly identifies the work the team commits to during the sprint. It organizes user stories, tasks, and responsibilities, providing focus, transparency, and alignment to achieve the sprint goal. This artifact is central to Agile execution, supporting collaboration and effective delivery within the sprint timeframe.