According to Module 07 of the course handouts, how are 'Pre-Release Defects' defined in a software product, and under what conditions do they typically manifest?
A.They are defined as 'Dormant Defects' which have the potential to create problems for users, often triggered by a specific situation or in low-priority areas with lower QA concentration.
B.They are compile-time warnings that automatically lock the SCM repository until a senior software architect reviews the code.
C.They are in-scope errors that are fixed immediately after the first client kickoff meeting.
D.They are run-time exceptions caused exclusively by hardware incompatibilities in the production environment.
Based on the post-release defect example in Module 07, what was the primary reason the database log export to CSV failed at the production site despite passing internal SQA testing?
A.The SCM repository branches were completely locked, preventing database compile scripts from executing.
B.The CSV export was tested only up to 30,000 records because no upper limit was defined in the SRS, whereas the production database exceeded 500,000 records where records went missing.
C.The technical team used an off-the-shelf social media login plugin that altered the database table schemas.
D.The client failed to approve the user interface wireframes, which corrupted the database export formats.
According to Module 07, what is the 'last resort' in the relationship between Quality Assurance (QA) and software defects if a product cannot be made completely bug-free?
A.Ensuring that the critical functionality of the software product works at least, and that defects do not produce any kind of threat or damage to the critical function of the product.
B.Bypassing the testing phase entirely and relying on post-release customer support to find errors.
C.Locking the software configuration management repository to prevent any further code modifications.
D.Relying solely on automated static compilers to fix semantic and runtime exceptions.
According to Module 07, why is domain-specific knowledge of utmost importance for understanding requirements, and how do organizations solve this for technical resources?
A.Because all domains share the exact same terminologies; specialists are hired to perform manual unit testing.
B.Because domains have their own distinct terminologies whose meanings vary from domain to domain; domain specialists are hired to work with business analysts and/or developers to provide technical insights related to the domain.
C.Because domain knowledge determines the software's execution time in milliseconds; specialists are hired to configure SCM repositories.
D.Because domain knowledge is used to write release notes; specialists are hired to completely eliminate SQA review gates.
What does Module 07 state regarding the general conduct and execution of 'Inspections' across the software development life cycle (SDLC)?
A.Inspections are run automatically at compile-time by configuration management software to lock write access.
B.Inspections are only conducted during the deployment phase to verify network bandwidth limits.
C.Inspections are conducted to identify smells at any phase of SDLC and usually consist of walkthroughs of different artifacts to provide another EYE.
D.Inspections are client-side interviews aimed at redefining functional requirements in the SRS.
According to 'Defect Prevention Basics' in Module 07, what is the core assumption of defect prevention, and what is the best way to execute it?
A.It assumes that bugs are caused by hardware defects; the best way to prevent them is to replace client servers periodically.
B.It assumes that there are known error sources or inappropriate actions causing defects, and the best way to prevent them is to detect them as early as possible, find their source, and take corrective actions.
C.It assumes that clients write perfect SRS documents; the best way to prevent them is to eliminate SQA reviews entirely.
D.It assumes that developers never make syntax mistakes; the best way to prevent them is to lock the codebase post-compilation.
According to Module 07, since it is impossible to test exhaustively all conditions and paths in modern complex software, what is the final possible strategy to prevent catastrophic consequences?
A.To break the fault-failure relation to contain the damage or tolerate those faults.
B.To completely lock the development repository and restrict all user interactions to command-line interfaces.
C.To ignore the errors and reclassify all reported runtime bugs as out-of-scope wish-list features.
D.To increase the count of SQA test cases with the exact same inputs to eliminate hardware-level conflicts.
Under the CMMI and SQA guidelines in Module 07, how is the concept of 'Defect Prevention' defined, and what is its primary focus?
A.It is the process of executing the product under stress conditions to evaluate performance benchmarks.
B.It is the process of addressing the root causes of defects to prevent their future occurrence (Error Source Removal).
C.It is the measurement of the proportion of defects found by QA out of the total found in production.
D.It is the automated review of code blocks by an independent Lead SCM Auditor.
According to Module 07 of the course handouts, when does formal testing of a software product start, and what is the relationship between the development and QA teams at this point?
A.It starts during the requirements-gathering phase before any code is written or compiled.
B.It starts when the development team hands over the code to the QA team, who then perform different testing and sub-testing activities to ensure product stability.
C.It starts immediately after the client signs the contract, using ad-hoc wireframe designs.
D.It starts after the product is fully deployed at the production site by third-party support teams.
According to Module 07, what is the primary aim of having a vigorous 'Defect Reduction' process in place alongside defect prevention mechanisms?
A.To completely lock SCM repositories to prevent developers from checking in unapproved code modifications.
B.To reduce defects as much as possible from their sources to prevent them in the future and remove those that bypassed prevention gates.
C.To automatically rewrite database query codes using third-party off-the-shelf compiler tools.
D.To eliminate the need for writing functional test cases by relying on client-side demo reviews.
