ISO-IEC-27001-LEAD-IMPLEMENTER practice question 30 of 35

Scenario 9: CoreBit Systems CoreBit Systems, with its headquarters m San Francisco, specializes in information and communication technology (ICT)…

Full set: 290 questions

Domain Continual improvement of an ISMS based on ISO/IEC 27001

Scenario 9: CoreBit Systems CoreBit Systems, with its headquarters m San Francisco, specializes in information and communication technology (ICT) solutions, its clientele primarily includes data communication enterprises and network operators. The company's core objective is to enable its clients a smooth transition into multi-service providers, aligning their operations with the complex demands of the digital landscape. Recently. John, the internal auditor of CoreBit Systems, conducted an internal audit which uncovered nonconformities related to their monitoring procedures and system vulnerabilities, in response to the identified nonconformities. CoreBit Systems decided to employ a comprehensive problem- solving approach to solve these issues systematically. The method encompasses a team-oriented approach, aiming to identify, correct, and eliminate the root causes of issues. This approach involves several steps. First, establish a group of experts with deep knowledge of processes and controls. Next, break down the nonconformity into measurable components and implement interim containment measures. Then, identify potential root causes and select and verify permanent corrective actions. Finally, put those actions into practice, validate them, take steps to prevent recurrence, and recognize and acknowledge the team's efforts. Following the analysis of the root cause of the nonconformities, CoreBit Systems's ISMS project manager. Julia, developed a list of potential actions to address the identified nonconformities. Julia carefully evaluated the list to ensure that each action would effectively eliminate the root cause of the respective nonconformity. While assessing potential corrective action for addressing a nonconformity, Julia identified the issue as significant and assessed a high likelihood of its reoccurrence Consequently, she chose to implement temporary corrective actions. Afterward. Julia combined all the nonconformities Into a single action plan and sought approval from the top management. The submitted action plan was written as follows: A new version of the access control policy will be established and new restrictions will be created to ensure that network access is effectively managed and monitored by the Information and Communication Technology (ICT) Department. However. Julia's submitted action plan was not approved by top management The reason cited was that a general action plan meant to address all nonconformities was deemed unacceptable. Consequently, Julia revised the action plan and submitted separate ones for approval Unfortunately, Julia did not adhere to the organization's specified deadline for submission, resulting in a delay in the corrective action process, and notably, the revised action plans lacked a defined schedule for execution. Which method did CoreBit Systems use to address and prevent reoccurring problems after identifying the nonconformities?
Answer options
A: The Eight Disciplines Problem Solving (8Ds) method Correct answer
B: DMAIC (Define, Measure, Analyze, Improve, Control) method
C: Lean Six Sigma method
Correct Answer:
A. The Eight Disciplines Problem Solving (8Ds) method
Explanation

The problem-solving approach described in the scenario aligns directly with the Eight Disciplines (8D) method. The text outlines a sequence of steps: (1) establish a group of experts (D1: Use a Team), (2) break down the nonconformity (D2: Describe the Problem), (3) implement interim containment measures (D3: Implement Containment Actions), (4) identify root causes (D4: Define and Verify Root Cause), (5) select and verify permanent corrective actions (D5: Verify Corrective Actions), (6) implement and validate actions (D6: Implement Corrective Actions), (7) prevent recurrence (D7: Prevent Recurrence), and (8) recognize the team (D8: Congratulate the Team). This structured, team-centric process for addressing and eliminating recurring problems is the defining characteristic of the 8D methodology.

Why Incorrect

B. DMAIC (Define, Measure, Analyze, Improve, Control) method: This is a data-driven quality strategy for improving processes. It does not explicitly include the distinct steps of "interim containment actions" or "team recognition" as described in the scenario.
C. Lean Six Sigma method: This is a broad management methodology that uses tools like DMAIC to reduce waste and defects. It is not a specific, step-by-step problem-solving process as detailed in the scenario.

References

1. Zasadzień, M. (2016). Application of the 8D Method to Solve the Problems of the Production Process. Production Engineering Archives, 10(1), 12-15. This paper outlines the 8D method, detailing the disciplines from D1 (Establish the Team) to D8 (Congratulate the Team), which directly correspond to the steps taken by CoreBit Systems. (https://doi.org/10.30657/pea.2016.10.03)

2. University of Cambridge, Institute for Manufacturing (IfM). (n.d.). Eight Disciplines of Problem Solving (8D). IfM Engage. This university resource describes the 8D process as a method to "identify, correct, and eliminate recurring problems," and lists the eight steps that are mirrored in the scenario's description.

3. Benbow, D., & Kubiak, T. M. (2005). The Certified Six Sigma Black Belt Handbook. ASQ Quality Press. In Chapter 1, the DMAIC methodology is described. A comparison shows that while both DMAIC and 8D address root causes, the specific sequence and inclusion of interim containment and team recognition are hallmarks of the 8D process.

4. Różak, O., & Wyrwicka, M. K. (2017). The 8D Method as an Effective Way of Improving the Organization. In Management Engineering '17 Conference Proceedings (pp. 100-107). This academic publication presents the 8D method as a structured approach for corrective action, emphasizing its team-oriented nature and its steps for containment, root cause analysis, and prevention, all of which are mentioned in the CoreBit Systems scenario.

Scroll to Top