In white-box testing, "coverage" refers to the amount or percentage of the codebase that has been tested. It provides an objective measure to ensure that most, if not all, paths, branches, statements, and conditions in the code have been exercised.

In the V-model, each development stage corresponds to a testing phase. As the development progresses downwards on the left side of the "V", testing activities are prepared. When development reaches integration and system levels, the testing phases commence upwards on the right side of the "V". This ensures that testing is integrated in parallel with development, unlike the Waterfall model where testing happens after the entire development phase.

The risk avoidance strategy involves taking actions to remove the threat or condition that represents the risk entirely, essentially ensuring that the risk event doesn't occur. This strategy is employed when risks are deemed too high and cannot be mitigated.

QTP stands for QuickTest Professional. However, it was later rebranded by Hewlett-Packard (HP) as "Unified Functional Testing" (UFT). UFT provides a comprehensive solution for functional and regression testing and is one of the most popular tools in the testing industry for automating GUI testing tasks.

Exit criteria in the Software Testing Life Cycle (STLC) are a pre-defined set of conditions or metrics which must be achieved to conclude a testing phase. These conditions could include factors like achieving a certain percentage of test coverage, a limited number of high-severity defects remaining open, meeting performance benchmarks, etc. Having a clear exit criteria ensures that a testing phase achieves its intended quality objectives before moving to the next phase.

Decision Coverage in white-box testing ensures that each decision point or branch has been executed for both 'true' and 'false' conditions. It is more robust than simple statement coverage because it ensures that each decision leads the control flow in both directions.

Automated test suites, which consist of a collection of test scripts, test data, and execution sequences, require effective management to ensure organized execution and reporting. Test Management tools offer capabilities to define, organize, and execute tests, as well as to report defects and generate metrics, streamlining the automation workflow.

The Test Manager oversees the entire testing process and ensures that all testing activities align with the project timelines and budget. They coordinate between stakeholders and the testing team, ensuring that the testing phase progresses smoothly.

Feature flags or toggles are utilized in Continuous Integration primarily to progressively release new features to a subset of users or environments. This means that a feature can be developed and integrated into the main codebase but can remain hidden to users until it's ready for release. It provides developers with the flexibility to test new functionalities without affecting all users and roll back quickly if issues arise.

"Inherent risks" are the risks that exist in the absence of any control or action to address them. It's the natural level of risk that exists. "Residual risks" are the remaining risks after controls and actions have been applied to mitigate the inherent risks.