According to the test ideas for arithmetic operations presented in Section 09.8, what testing strategies should be used to explore supported values in a black-box scenario?
A.Perform tests using floating-point numbers, integers, and boundaries of integers.
B.Compile the program using multiple compiler optimization flags to monitor execution memory.
C.Analyze database transaction logs to determine if rollback locks are released within 200 milliseconds.
D.Conduct path coverage and branch level testing (if-else, loops, switch) inside the development environment.
In the context of DaysInMonth(month, Year) black-box testing, why does the course handout recommend testing years such as 'even 100s' and '4s'?
A.To evaluate database transaction rollback limits and track SQL database latency.
B.To ensure statement coverage of the compiler's primary arithmetic blocks reaches 100%.
C.To thoroughly test leap year boundary rules, since leap years occur every 4th year, but century years (even 100s) are only leap years if divisible by 400.
D.To verify configuration baseline tags in Git, VSS, or TFS repositories.
According to Module 09 of the course handouts, why is White Box Testing typically performed by the developer rather than an independent tester?
A.Because developers hold administrative rights to log tickets in tools like Mantis.
B.Because it requires extensive knowledge of the code and the flow of code.
C.Because developers need to estimate the Schedule Performance Index (SPI) of compile-time iterations.
D.Because SQA standards prohibit independent testing teams from reviewing database schemas.
According to Section 09.7 of the course handouts, what is described as a good way to perform Black Box Testing, and what is the objective of 'Smoke Tests'?
A.A static walkthrough is the best way; Smoke Tests aim at testing all possible mathematical paths of deep compiler statements.
B.A Specification Checklist is a good way to perform this testing, while Smoke Tests are the most abstract level of testing that aims at ensuring that the most important functions work.
C.Using automated database rollback logs is the best way; Smoke Tests verify configuration management baseline tags.
D.Relying on CMMI Level 4 statistical process boundaries is the only way; Smoke Tests evaluate the Cost Performance Index (CPI).
How does the course handout differentiate a Test Checklist from Functional Testing?
A.A Test Checklist is a static peer-review activity led by a certified facilitator, while Functional Testing is a white-box dynamic testing technique.
B.A Test Checklist is simply a list of readiness preparation activities to execute before and during testing, whereas Functional Testing is a totally different concept concerned with requirements conformance.
C.A Test Checklist is a quantitative analysis tool used only at CMMI Level 5, while Functional Testing is used at Level 1.
D.There is no difference; they are interchangeable terms used to describe black-box testing.
According to Module 09 of the course handouts, how are the terms 'Functional Testing' and 'Black Box Testing' related, and what is the simplest definition of Black Box Testing?
A.They are completely unrelated; functional testing tests internal structural logic while black box testing is a manual code review technique.
B.They are two terms used interchangeably, where black box testing in its simplest form is an ad-hoc running and execution of the software system to observe any difference between expected and actual performance.
C.Functional testing is a sub-phase of white box testing, whereas black box testing is a third-party CMMI compliance audit process.
D.They represent the first and fifth maturity levels of the CMMI process management framework respectively.
According to Module 09, Example 2 of the course handouts, which of the following is a key objective of a Web Performance Test Checklist, and what does it exclude?
A.It is designed to verify system architecture, database capacity, and load balancing, and it explicitly excludes functional testing.
B.It is designed to evaluate manual black-box user interfaces, and it explicitly excludes system-level integration verification.
C.It is designed to count the lines of code executed per loop, and it explicitly excludes structural path testing.
D.It is designed to monitor the Schedule Performance Index (SPI) of the development team, and it explicitly excludes cost auditing.
According to the Data Security Web Testing Checklist in Module 09, which of the following is NOT one of the sample checks explicitly listed?
A.Are data inputs adequately filtered?
B.Are data access privileges identified? (e.g., read, write, update and query)
C.Has the database capacity been identified and has anticipated growth data been obtained?
D.Have data backup and restore processes been defined and tested?
Based on the Black Box Testing guidelines in Module 09 of the course handouts, what action should be taken if a gap or variance is observed between expected and actual performance, and what is the purpose of this action?
A.The testing process must be immediately halted and escalated to the Level 1 Customer Support Team.
B.The software configuration baseline must be rolled back to the previous release without any re-run.
C.The execution process is repeated to eliminate the possibility of hardware failure causing the difference.
D.The SQA team must unilaterally change the SRS document to match the actual output of the compiler.
According to Section 09.15 of the course handouts, what is the primary objective of an 'Inspection' and how are its findings managed?
A.To measure schedule variance (SPI) and log project planning delays in a milestone progress chart.
B.To evaluate the level of compliance with specific rules, principles or best practices, with all activities well documented and defects logged in a defect logging sheet.
C.To bypass standard coding principles by hot-fixing compiler warning messages automatically.
D.To analyze database schema index performance and update transaction query limits in production.
