In Module 01, Section O's example of a software defect involving an online payment solution, which of the following represents the deviation from user expectations found in production?
A.The system is completely offline and does not allow login via credit card details.
B.The option of selecting the debit card for making payments is missing in the production software.
C.The payment transaction has a security leak that exposes PIN numbers to developers.
D.The user is charged a double transaction tax that was not mentioned in the requirements.
In Section M's example of a semantic error, why does the expression `if ($Amount = 100)` fail to perform the intended logical check in PHP, and how is it corrected?
💻 php Snippet
if ($Amount = 100)
A.It performs an assignment of 100 to `$Amount` instead of a comparison, which always evaluates to true; it is corrected by changing the logic to use the equality operator `==`.
B.It is a syntax error because PHP variable names cannot start with capital letters; it is corrected by changing `$Amount` to `$amount`.
C.It is a compilation block error because semi-colons must be placed within parenthesis; it is corrected by adding a semi-colon inside.
D.It is an environment error because PHP does not support conditional operators; it must be run on a database server.
According to Module 01, Section T of the course handouts, how is 'Failure' defined under software quality engineering guidelines, and how does it relate to a software 'Fault'?
A.Failure is a human action or mistake that directly results in code syntax warnings during compilation.
B.Failure is a result of a fault; failure is the inability of the program to behave as expected within a given performance requirement.
C.Failure is the process of updating CMMI process guidelines when standard procedures are being ignored by developers.
D.Failure is a deviation from customer requirements that is found only after the software is shipped to the production site.
Under software fault-tolerance and containment strategies described in Section X, how can SQA engineers prevent system-level failures when code-level faults remain in the software?
A.By executing continuous automated rebuilds until all compile warnings disappear.
B.By breaking the causal relations between these faults and the resulting failures, thus “tolerating” these faults, or to contain the failures by reducing the resulting damage.
C.By reverting the codebase to an earlier version where requirements were less complex.
D.By asking the customer to lower their expectations to match the actual software capabilities.
According to Module 01, Section A of the course handouts, why is it exceptionally difficult to establish a single, standardized definition for 'software quality' in modern software systems?
A.Because software systems are isolated standalone platforms that ignore database integrations.
B.Because modern software systems are usually interconnections of multiple underlying software and exhibit a lack of standardization and a varied nature.
C.Because international standards like ISO-9126 require that all software quality characteristics be assessed by external consumers only.
D.Because SQA teams are considered pure technical resources who only execute compiler-level unit tests.
Under CMMI quality frameworks, which of the following groups of individuals are classified as 'Producers' of a software solution?
A.Persons involved in the development, management, maintenance, and service of the software product, including third-party products and organizations.
B.Only the end-users who register on the mobile application to purchase retail merchandise.
C.Only the finance department representatives who approve the project's external licensing invoices.
D.Strictly the external third-party independent auditors who perform CMMI appraisal ratings.
According to Module 01, Section N of the course handouts, what is the formal definition of a 'Defect' and where are defects typically discovered?
A.Defect refers to a compilation fault that prevents variable definitions from running in the testing environment.
B.Defect refers to the deviation from customer requirements, mostly found in the software after it is shipped to the customer at the production site.
C.Defect refers to a physical hardware failure in server racks caused by power fluctuations.
D.Defect refers to the process of rewriting development specifications to match the final compiled code.
Sourced from Module 01, Section X of the course handouts, what is the primary objective of Defect Containment, particularly when dealing with large and highly complex software systems?
A.To completely prevent any human error from occurring during the early requirement gathering phase.
B.To reduce the chance of defects passing from one phase to another, and to prevent failures by breaking the causal relations between faults and failures.
C.To eliminate all redundant code blocks and compile-time warnings automatically.
D.To reduce project development costs by replacing manual reviews with off-the-shelf automated plugins.
According to Module 01, Section E of the course handouts, which of the following is the standard definition of Off-the-Shelf (OTS) software products?
A.Software products that are custom-built from scratch for a single customer and require extensive post-release coding.
B.Software products available for any user, at cost or not, and used without the need to conduct development activities.
C.Software products developed by SQA teams to run automated touchscreen calibrations.
D.Software products that are strictly physical hardware devices deployed on remote server architectures.
According to Module 01, Section P of the course handouts, which of the following best defines a 'Bug', and what is the realistic 'ugly fact' in software development?
A.Bugs are compiled executable files that have not yet been signed, and the ugly fact is that they require physical token authorization.
B.Bugs are the errors found before the software is shipped into production, and the ugly fact is that there is nothing like Bug Free Software.
C.Bugs are design document revisions requested by external customers, and the ugly fact is that customers can reject them arbitrarily.
D.Bugs are database migration scripts that violate foreign key integrity, and the ugly fact is that they must be rewritten in assembly.
