According to Module 08 of the course handouts, what is the most important factor when making decisions regarding defect resolutions (such as deciding whether a defect is to be fixed or not)?
A.The decision should be made unilaterally by the lead programmer to prevent development delays.
B.The decision must be accepted by all stakeholders with mutual consent, ensuring that if a defect is left unfixed in the current release, everyone agrees.
C.The decision is automated by static review tools like Mantis or configuration management frameworks.
D.The decision must be deferred to external third-party auditors during formal biannual CMMI reviews.
According to Module 08 of the course handouts, what is the core definition of the traditional 'Defect Resolution' process, and how does its workflow typically proceed?
A.It is an automated compilation process that monitors database transaction speeds and locks SCM branches.
B.It is a process that keeps a record of a reported defect until the testing department formally closes it after validation of the fix.
C.It is a business analysis method designed to rewrite requirements in the SRS without developer inputs.
D.It is a post-deployment client support activity where release notes are generated using spreadsheet templates.
According to Module 08 of the course handouts, which of the following describes the traditional Defect Resolution workflow and how a defect is handled if it cannot be resolved?
A.It is a process where developers unilaterally close reported bugs, and unresolved defects are deleted from the database without any client notification.
B.It typically starts with defect identification by the QA team, is sent to the development team to fix, and is returned to QA to be validated; if unresolved due to reasons like lack of communication or inability to remove, all parties must agree to leave it unfixed.
C.It is a process where the configuration management team automatically generates code fixes, and unresolvable defects are marked as completed to avoid SPI drops.
D.It is an informal review activity led by an independent external auditor, where unresolved bugs are permanently reclassified as normal requirements.
According to Module 08 of the course handouts, which of the following correctly describes the role of the Level 2 and Level 3 support teams within the post-deployment software maintenance and defect handling framework?
A.Level 2 involves members of the QA team to provide support, while Level 3 involves members of the development team to provide support to customers.
B.Level 2 involves members of the financial audit team to calculate SPI/CPI, while Level 3 involves third-party certified CMMI appraisers.
C.Level 2 is handled by external first-party auditors, while Level 3 is automated by SCM versioning compilers.
D.Level 2 is managed by the sales team to negotiate SLAs, while Level 3 is managed by technical writers to draft release notes.
Based on Module 08 of the course handouts, which of the following is a key characteristic of defect management and support in a 'Product-Based' software scenario?
A.Defect resolution is a one-time activity that ends immediately upon shipping the software to the production site.
B.Defect resolution is an ongoing activity that continues even after the product is deployed on the client's site, managed by a dedicated post-deployment support team to ensure hot-fixes.
C.Product defects are excluded from SLA agreements and are always handled under separate sales projects.
D.Product defects can be closed by the developer without any verification or validation by the QA team.
According to Module 08 of the course handouts, when must all bugs and defects be discovered and resolved in a project-based scenario compared to a product-based scenario?
A.All defects must be discovered and fixed before handing over the product to the customer.
B.Defects are continuously resolved over an indefinite period after deployment without any formal project boundaries.
C.All defects are automatically managed by compiler optimization software at compile-time to maintain SCM baselines.
D.Defects are resolved exclusively by the client's internal sales team after the final release notes are distributed.
According to the course handouts, what is the primary benefit of establishing and sharing a sample defect tracking and log template within a project team?
A.It restricts developer access to database shared variables to prevent inter-team conflicts.
B.It is shared with all team members to improve collaboration and ensure that necessary details are communicated to the development team to understand and fix defects.
C.It automates the compilation of hot-fixes and patches without requiring SQA verification cycles.
D.It replaces the need for writing functional test cases or using specific defect-tracking tools.
According to the course handouts, what critical parameters must be included in a defect log established during the testing phase, and what is the primary purpose of providing these details to the development team?
A.Total project budget, line count of code, and server IP addresses; to calculate CPI and SPI metrics.
B.Defect ID, priority and severity level, current defect status, and others; to ensure the development team has necessary details to understand and fix the defect.
C.User passwords, customer bank details, and database access keys; to run integration sanity checks.
D.Marketing release schedules and draft user manuals; to finalize post-deployment SLA terms.
According to the product evaluation guidelines in Module 08, which of the following represents the correct set of key criteria evaluated during this process?
A.Opportunity assessment, initiating process, project planning, executing/controlling, and closing.
B.Code quality, sustainability of the product, defect backlog, features, reliability of features, compatibility, and support of features.
C.First-party audits, second-party audits, and third-party appraisals.
D.Unit testing, sanity testing, system level testing, and regression testing.
According to the 'Defect Log Instructions' in Module 08 of the course handouts, what does the 'Priority' code of a logged defect indicate on a software project?
A.The complexity of the system architecture as evaluated by the Lead Architect.
B.The impact of this defect on the project.
C.The count of code lines that must be rewritten by the development team.
D.The percentage of test cases that failed during the integration testing phase.
