A potential drawback of relying solely on Exploratory Testing is the lack of documentation. Since the testing process is exploratory and not based on predefined scripts, it may lead to insufficient documentation of test cases and steps, making it challenging to reproduce and track issues systematically.

Prioritizing defects based on severity contributes to efficiency by addressing critical issues first, reducing the impact on the system and enabling a faster and more targeted testing process.

The increase in defects could be attributed to the introduction of new features without adequate testing. The team should investigate and prioritize testing these new features to identify and fix defects. Proper regression test coverage and an effective bug tracking system are essential to prevent such issues during regression testing.

Functional testing ensures that the software product meets user requirements during the SDLC. It focuses on validating the system's behavior as per user expectations.

Traceability matrices are commonly used in Use Case Testing to establish a link between the requirements and the corresponding use cases. By maintaining this traceability, testers can identify potential issues, track the coverage of requirements, and refine use cases to ensure comprehensive testing. It provides a structured approach to managing and aligning the test scenarios with the specified requirements, enhancing the effectiveness of Use Case Testing.

Security testing is a type of non-functional testing that focuses on identifying vulnerabilities and ensuring the system's security. Scalability and reliability testing are also non-functional aspects.

Security Testing involves analyzing the system's ability to handle unexpected inputs and outputs securely. It helps identify vulnerabilities and weaknesses in the software that could be exploited by malicious entities. This type of testing is crucial for ensuring the robustness of the application against security threats.

Compatibility testing ensures the application works seamlessly across different devices, screen sizes, and resolutions, a crucial aspect for a mobile banking app.

Load testing assesses system behavior under normal and peak conditions. Stress testing specifically evaluates the system's stability under extreme conditions, like a surge in user traffic during a sale event.

Streamlining the Defect Lifecycle involves adopting strategies such as implementing automated testing and continuous monitoring, establishing clear communication channels within teams, conducting regular root cause analysis, and trend analysis. Additionally, implementing a robust change management process helps manage the introduction of changes, minimizing the occurrence of defects and ensuring efficient defect management throughout the software development lifecycle.

To address stakeholder concerns about the risks of frequent deployments in CI/CD, it is crucial to communicate the benefits and provide a comprehensive risk mitigation plan. Frequent automated testing helps ensure the reliability of deployments, while features like Blue-Green Deployment and Gradual Rollout with Feature Flags offer strategies to minimize potential issues and roll back changes if needed.

Pairwise testing, also known as combinatorial testing, focuses on efficiently covering various combinations of input parameters by testing all possible pairs. This approach helps reduce the number of test cases needed while ensuring comprehensive coverage of potential input interactions.