Based on Module 10, Section 10.17 of the course handouts, which of the following outlines the correct workflow of code management and verification involving Software Configuration Management (SCM) and Sanity Testing?
A.SCM automatically compiles and deploys code directly to production, skipping developers and SQA to minimize release time.
B.Multiple developers work on different modules of the same software, SCM merges the code, and then the merged code is handed over to developers again to perform sanity testing.
C.The client merges the codebases manually and executes white-box branch coverage checks before SCM reviews the build.
D.The EPG reviews the project budget sheets first, and if a variance of over 25% is detected, SCM deletes the repository.
Based on Module 10, Sections 10.38 and 10.39 of the handouts, which of the following is correct regarding how the Social Media registration integration request is packaged and delivered if it is accepted as a WishList item?
A.It is deployed instantly as an urgent Hot Fix by bypassing all developer code reviews and unit test validations.
B.It is estimated, analyzed, and eventually delivered as a Patch (or within a planned release), with the timeline incorporating proper SQA/regression testing cycles.
C.It is treated as a pre-release compiler warning that does not require any customer confirmation or specification tracking.
D.It is archived in the Software Configuration Management repository as a non-reproducible defect that will not be implemented.
According to Module 10 of the course handouts, which of the following best describes the core characteristic of 'Hot Fixes' and how SQA activities are managed during their implementation?
A.Hot fixes are non-urgent cosmetic updates deployed monthly, requiring complete CMMI level multi-stage peer reviews.
B.Hot fixes are live production issues where, due to extreme urgency, the team depends on unit testing and code reviews to deploy fixes quickly instead of executing full regression testing.
C.Hot fixes are out-of-scope wishlist requirements that must always be scheduled for the next major yearly software release.
D.Hot fixes represent automated database backups executed by SCM during low-traffic periods to prevent memory leaks.
According to Module 10, Section 10.16 of the course handouts, which of the following is NOT described as a direct organizational or economic impact of performing Unit Testing?
A.It ensures early defect removal since it is very easy to look for defects individually and independently in all units.
B.Because it is done in isolation, it becomes easy to debug the code to prevent defect reproduction.
C.The testing efforts are done at the developer's level who can easily understand the code.
D.It automatically guarantees that when these units are integrated, they will require no integration or sanity testing whatsoever.
Based on Module 10, Section 10.20 (Example 1) and Section 10.21 of the course handouts, which of the following options correctly represents the list of 4 features under sanity testing and the definition of 'Feature Level Testing'?
A.Features: Input, Output, Compile, Run; Feature Level Testing is checking statement-level branch coverage.
B.Features: Registration, Booking, Payment, & Reports; Feature Level Testing is aimed at making sure software functions and their underlying units meet all specifications.
C.Features: Database, Network, Server, Client; Feature Level Testing is verifying hardware resource limits.
D.Features: Alpha, Beta, Sanity, Regression; Feature Level Testing is conducted exclusively by the final end users.
According to Module 10, Section 10.6 of the course handouts, how are software requirements mapped to test cases during the test preparation phase?
A.Software requirements are automatically converted to test cases by third-party CMMI Level 5 off-the-shelf plugins.
B.Software requirements are further divided into use cases which describe what users will follow to perform a certain task, and test cases are then established against all user stories to verify whether users can perform them.
C.Software requirements are bypassed entirely, and test cases are written based on ad-hoc discussions with developers during daily standup meetings.
D.Software requirements are mapped directly to database capacity metrics, and test cases are generated only for performance load-balancing checks.
Based on the SQA standards in Module 10, what is the role of Use Cases in generating the test case suite during the test preparation phase?
A.Use cases are compiled automatically by configuration management databases to run sanity test plans.
B.Use cases describe what users will follow to perform a certain task, and test cases are established against all user stories to verify whether users will be able to perform them successfully.
C.Use cases represent the actual programming structures tested statement-by-statement in white-box testing.
D.Use cases are primarily financial planning tools used to compute the Cost Performance Index (CPI) of the project.
According to the comparative table in Module 10, Section 10.13 of the course handouts, how do the environment-specificity and release cycles of test cases differ between bespoke Project-Based Testing and commercial Product-Based Testing?
A.Project test cases are updated continuously per release, while product test cases are tailored only once for a single client environment.
B.Project test cases are usually specific under a specific environment and represent a one-time activity, while product test cases are regularly updated as per release and correspond to an ongoing activity.
C.Project test cases are completely abstract black-box checklists, while product test cases are branch-level statements generated by developers.
D.There is no difference; both are managed using identical static templates that are archived immediately after initial deployment.
According to Module 10, Section 10.36 of the course handouts, why is the process of handling pre-production issues fundamentally different from handling post-production issues?
A.Because pre-production issues are compiled automatically by the EPG lead auditor, while post-production issues are handled by SCM.
B.Because the end-user is usually not involved during development, whereas post-production issues are reported directly by live end-users.
C.Because pre-production issues require zero-defect validation, while post-production issues are completely ignored by the vendor.
D.Because pre-production issues only consist of database capacity changes, while post-production issues are budget adjustments.
Based on Module 10, Section 10.29 of the course handouts, how do Test Dashboards assist the Quality Assurance (QA) team in making useful decisions regarding testing strategy?
A.They calculate the Schedule Performance Index (SPI) and Cost Performance Index (CPI) of the development sprint.
B.They allow the SQA team to monitor test activities, report on progress, find gaps in test coverage, and identify test areas that may require additional investigation.
C.They eliminate the need for subsequent regression and sanity testing by verifying code units in absolute isolation.
D.They facilitate peer reviews of the Software Requirement Specification (SRS) without requiring technical developer input.
