Based on Module 10, Section 10.5 of the course handouts, which of the following groups of questions represents the critical decisions made during the 'Test Planning and Preparation' stage?
A.Who wrote the code, how many billing hours did they record, and what is the current CPI ratio?
B.What are the objectives and overall goals, what specific areas/features are to be tested, what would be the exit criteria, and in what environment(s) is the software to be tested?
C.How many lines of code are in the module, and which SCM version control system (Git, TFS, or VSS) is used?
D.Has the customer signed the post-deployment SLA, and has Level 1 customer support been trained?
According to Module 10, Section 10.17 of the course handouts, what is the primary focus of Sanity (Integration) Testing, and what is evaluated during this level of testing?
A.It focuses on finding compilation syntax errors inside isolated mathematical statements.
B.It focuses on the integration of different components to work together, so components along with their interconnections are examined and evaluated.
C.It focuses exclusively on testing the hardware network card bandwidth under maximum transactional load.
D.It focuses on conducting static peer reviews of the Software Requirement Specification (SRS) document.
According to Module 10 of the course handouts, what is the significance of presenting test dashboard data graphically (as mentioned in Section 10.31) and how does it relate to the transition into Release Notes Basics (Section 10.32)?
A.Graphical presentation makes the data easy to understand, allowing stakeholders to easily comprehend quality trends, which provides foundational metrics for drafting release notes.
B.Graphical representation is a compiled program file that SCM deploys directly onto production servers to bypass testing.
C.It is used exclusively to measure hardware bandwidth and CPU performance during stress tests.
D.It completely replaces the text in release notes, providing only screenshots to end users.
According to Module 10, Section 10.37 of the course handouts, which of the following best describes the core operational characteristics and Quality Assurance (QA) trade-offs of a Hot Fix?
A.A Hot Fix is a scheduled monthly update that undergoes comprehensive independent system-level stress testing and complete regression cycles prior to delivery.
B.A Hot Fix is an urgent production issue where, due to extreme time constraints and high business impact, the team bypasses the complete QA process and relies primarily on unit testing and Code Reviews rather than full regression testing.
C.A Hot Fix is an administrative tool used by the Software Configuration Management (SCM) team to delete outdated code repositories and historical file backups.
D.A Hot Fix is a paid change request where the client pays the vendor to perform static code analysis and calculate the Earned Value (EV) of the current sprint.
In the scenario described in Module 10, Section 10.39, if the client agrees that a post-delivery request (such as social media registration integration) is a 'WishList' item, how does the vendor proceed?
A.The vendor must fix the issue immediately as an urgent Hot Fix at their own expense without updating timelines.
B.The vendor conducts analysis, provides estimates, and shares updated timelines and budgets, as these are paid changes.
C.The vendor registers the request in the SCM repository as an internal compiler error and schedules a third-party CMMI audit.
D.The vendor deletes the user registration database and rolls back the live environment to Release 1.0.
According to Section 10.3 of the course handouts, what capability makes it easy to revert back any changes if a customer does not approve of changes made in a certain release?
A.Maintaining active database connection pools in production environments.
B.Versioning and keeping backups of all releases.
C.Enforcing strict data access privileges such as read, write, and update.
D.Performing ad-hoc black-box smoke testing before every code shipment.
Based on Module 10, Section 10.5 of the course handouts, why is the 'Test Planning and Preparation' stage considered one of the most important activities in the entire software testing process?
A.Because it is the only stage where code compilation warnings are resolved and redundant procedures are eliminated from the source code.
B.Because most of the decisions related to testing are made in this stage, and the answers to key questions (objectives, features, exit criteria, environments) decide the testing strategy and determine SQA quality.
C.Because it allows the project manager to calculate the Earned Value (EV) and determine whether the project is over budget.
D.Because it eliminates the need for formal inspections and direct code walkthroughs by automating the test execution phase.
According to Module 10, Section 10.12 (Example 3) of the course handouts, what is the Test Scenario, Expected Results, and Actual Results for Test Case ID TU03?
A.Test Scenario: Check Customer Login with valid Data; Expected Results: User should Login into application; Actual Results: As Expected
B.Test Scenario: Verifying Dashboard for Product; Expected Results: Product Dashboard Count should be updated with addition of new Product; Actual Results: Product Dashboard is updated
C.Test Scenario: Check Forget Password; Expected Results: User should be able to login with new password; Actual Results: Failed
D.Test Scenario: Verify SCM Code Shipment; Expected Results: Code base is compiled; Actual Results: Warning messages generated
Based on Module 10, Section 10.38 of the course handouts, how does a 'Patch' differ from a 'Hot Fix' in terms of execution timeframe, client waiting capacity, and QA cycle implementation?
A.A patch is performed with zero testing, whereas a hot fix requires complete independent third-party audits.
B.A patch addresses issues where the client can wait a short period of time, allowing the development team to do proper estimation and run full QA cycles, with a delivery timeframe typically less than a Major Release but more than a Hot Fix.
C.A patch is only used for non-critical cosmetic improvements, while hot fixes are strictly reserved for out-of-scope wishlist enhancements.
D.There is no difference; both terms are used interchangeably in CMMI process guidelines to describe daily software compilations.
According to Module 10, Section 10.35 of the course handouts, what does it mean to 'productionalize' an environment, and how are post-production issues characterized?
A.To compile code units in local scratch folders; post-production issues are syntax warnings flagged by the local Java compiler class.
B.To deploy staging server codebase to the Production Server; post-production issues are reported by end-users and may be of low priority from a development standpoint but of high priority from the end-user's viewpoint.
C.To delete all version histories in SCM to save disk space; post-production issues are missing configuration items.
D.To submit a project budget variance report to the financial department; post-production issues are schedule delays.
