Free CLSSYB-001 Practice Test

The Risk Priority Number (RPN) is a key output of a Failure Modes and Effects Analysis (FMEA). It is a calculated metric used to quantify and rank the risk associated with each identified potential failure mode. The RPN is determined by multiplying the scores for Severity (the impact of the failure), Occurrence (the frequency of the failure), and Detection (the likelihood of detecting the failure before it reaches the customer). By ranking failure modes from the highest RPN to the lowest, teams can prioritize their resources and focus mitigation efforts on the most critical risks affecting the process output.

B. False: This is incorrect. The statement accurately describes the fundamental purpose of the RPN, which is to provide a systematic method for ranking failure modes to prioritize corrective actions.

1. Stamatis, D. H. (2003). Failure Mode and Effect Analysis: FMEA from Theory to Execution. ASQ Quality Press. In Chapter 4, "The FMEA Form," the RPN is defined as "a mathematical product of the numerical ratings of the severity, occurrence, and detection" (p. 83). The text further explains that its purpose is to "rank-order the concerns in the process" (p. 84).

2. Purdue University, School of Industrial Engineering. (n.d.). Failure Modes and Effects Analysis (FMEA). Course materials. Retrieved from https://engineering.purdue.edu/~xe/courses/ie336/FMEAhandout.pdf. On page 1, the document states, "The Risk Priority Number (RPN) is the product of the SEV, OCC and DET scores... The RPN is used to prioritize the failure modes for corrective action."

3. Liu, H. C., Liu, L., & Liu, N. (2013). Risk evaluation approaches in failure mode and effects analysis: A literature review. Expert Systems with Applications, 40(2), 828-838. https://doi.org/10.1016/j.eswa.2012.08.010. In Section 2.1, "Traditional FMEA," the paper states, "The risk of a failure mode is evaluated by the risk priority number (RPN)... The RPN value for each failure mode is used to rank the risks in a descending order."

The expression Y = f(Xn) represents a fundamental concept in process improvement and statistics. In this function, 'Y' is the output or effect, and its value is a function of, or depends on, the inputs. Therefore, Y is the dependent variable. The 'Xn' represents the various inputs, factors, or causes that are believed to influence the output. These are the variables that can be manipulated or changed to observe their effect on Y, making them the independent variables. This relationship is central to the Six Sigma methodology for identifying the root causes of process variation.

A. Independent, dependent: This option incorrectly reverses the roles of the output (Y) and the inputs (Xn) in the functional relationship.
B. Individual, multiple: These terms describe the quantity of the variables (one output, multiple inputs) but not their statistical or functional relationship of dependency.
C. Sole, multiple: Similar to option B, this describes the number of variables involved rather than their roles as cause (independent) and effect (dependent).

1. Hart, D. M. M. (2006). Applying Lean Six Sigma in a High-Mix Low-Volume Manufacturing Environment [Master's thesis, Massachusetts Institute of Technology]. MIT DSpace. On page 13, the thesis states, "The underlying principle of Six Sigma is the equation Y=f(x). Y is the output or effect... X represents the inputs or causes... Y is a dependent variable, a function of the independent variables, X." Retrieved from https://dspace.mit.edu/handle/1721.1/36659

2. University of Washington, College of Engineering. (n.d.). Introduction to Process Improvement and Lean Six Sigma. In this courseware, the relationship is defined as: "Y = f(x) ... Y is the output (dependent variable) ... x’s are the inputs (independent variables)." (Module: Six Sigma Overview, Slide on "The Six Sigma Philosophy").

3. Montgomery, D. C. (2013). Introduction to Statistical Quality Control (7th ed.). Wiley. Chapter 1, Section 1-3, "The DMAIC Process," introduces the concept of Y = f(x) where Y is the output (a dependent variable) and the x's are the controllable or uncontrollable input variables (independent variables) that affect it. This is a foundational textbook for quality engineering and Six Sigma.

A properly constructed business case within a Lean Six Sigma framework must be specific, measurable, and quantify the problem's impact in clear terms, usually financial. The provided statement fails this standard by using vague, colloquial language such as "a whole bunch of money" instead of a specific financial figure (e.g., "$500,000 in rework and warranty costs"). Furthermore, the target of "nearly no returns" is not a SMART (Specific, Measurable, Achievable, Relevant, Time-bound) goal. A well-defined business case provides the data-driven justification necessary for project approval and is a critical component of the project charter.

A. True: This is incorrect because the business case lacks the essential quantification and specificity required for a formal project proposal. Vague statements undermine its credibility and utility for decision-making.

1. Pyzdek, T., & Keller, P. A. (2018). The Six Sigma Handbook (5th ed.). McGraw-Hill Education. In Chapter 10, "The Define Phase," the authors detail the components of a project charter, emphasizing that the business case must clearly articulate the problem and its financial impact on the organization. Vague descriptions like "a whole bunch of money" are explicitly discouraged in favor of quantified estimates.

2. George, M. L., Rowlands, D., Price, M., & Maxey, J. (2005). The Lean Six Sigma Pocket Toolbook. McGraw-Hill. In the section on "Project Charter" (pp. 18-20), the toolbook explains that a business case should answer "Why is this project important to the business?" with quantifiable data, linking the project to strategic objectives and financial metrics.

3. University of Michigan College of Engineering, Nexus. (n.d.). Lean Six Sigma Green Belt Certification Courseware. In the module covering the "Define" phase, the curriculum specifies that a business case must "Quantify the impact of the problem on the customer and the business (e.g., cost, revenue, margin)." This principle directly contradicts the imprecise language used in the question's example.

Critical-to-Quality (CTQ) characteristics are the key measurable attributes of a product or process that must meet specific standards to satisfy the customer. They translate broad customer needs into quantifiable requirements. Functionality (does it perform its intended task?), Durability (how long does it last?), and Dependability (how reliably does it perform over time?) are all fundamental aspects of product quality that are of high importance to customers. Therefore, all of these are very likely to be identified as CTQs during the Voice of the Customer (VOC) analysis in the Define phase of a Six Sigma project. Since all listed options are valid examples of CTQs, none of them would be excluded.

A. Functionality: This is a primary customer requirement. If a product does not function as expected, it fails to meet the most basic quality standard and is a classic example of a CTQ.
B. Durability: A product's lifespan and resistance to wear are critical factors for customer satisfaction and value perception, making durability a common and important CTQ.
C. Dependability: This attribute, also known as reliability, measures the consistency of a product's performance. It is a crucial quality characteristic and a frequent source for CTQs.

1. Griffin, A., & Hauser, J. R. (1993). The Voice of the Customer. Marketing Science, 12(1), 1–27. This foundational paper discusses how customer needs (such as dependability, durability, and functionality) are translated into specific, measurable engineering characteristics, which is the essence of a CTQ. The entire article is premised on capturing these types of attributes.

2. Antony, J., & Banuelas, R. (2002). Key ingredients for the effective implementation of Six Sigma program. Measuring Business Excellence, 6(4), 20-27. https://doi.org/10.1108/13683040210451679. The article emphasizes that Six Sigma projects focus on improving business performance by addressing customer needs, which are defined by CTQs like reliability (dependability) and performance (functionality).

3. MIT OpenCourseWare. (2009). 16.851J / ESD.35J Engineering Systems Analysis for Design, Lecture 5: The Voice of the Customer. Massachusetts Institute of Technology. Retrieved from https://ocw.mit.edu/courses/16-851j-engineering-systems-analysis-for-design-fall-2009/resources/mit16851jf09lec05/. Slide 12 ("The CTQ Tree") and the surrounding lecture notes explain the process of breaking down general customer needs into specific, measurable CTQs, using examples that fall under categories like functionality and reliability.

DPMO, which stands for Defects Per Million Opportunities, is a fundamental metric in the Six Sigma methodology. It quantifies the performance of a process by measuring the number of defects for every one million opportunities for a defect to occur. This standardized metric allows for the comparison of different processes, regardless of their complexity or volume. A lower DPMO value indicates a higher level of process capability and quality. The ultimate goal of a Six Sigma process is to achieve a DPMO of 3.4 or less.

A. Delayed production metrics output: This term is incorrect. DPMO is a measure of process quality (defects), not the timeliness of reporting metrics.
B. Defects by management oversight: This describes a potential root cause for defects, not the standardized metric used to measure process performance.
D. Developed production management oversight: This is an unrelated management phrase and does not correspond to the DPMO acronym or its application in quality control.

1. Montgomery, D. C. (2013). Introduction to Statistical Quality Control (7th ed.). Wiley. In Chapter 1, Section 1.4.3, "Six Sigma," the text defines DPMO as "defects per million opportunities" and explains its calculation and significance in measuring process performance.

2. Pyzdek, T., & Keller, P. (2018). The Six Sigma Handbook (5th ed.). McGraw-Hill Education. Chapter 5, "Six Sigma Metrics," provides a detailed definition: "DPMO = Defects Per Million Opportunities. This is the average number of defects per unit observed during an average production run, divided by the number of opportunities to make a defect on that unit, normalized to one million."

3. Antony, J., & Banuelas, R. (2002). Key ingredients for the effective implementation of Six Sigma program. Measuring Business Excellence, 6(4), 20-27. On page 22, the article lists DPMO (defects per million opportunities) as a key Six Sigma metric for measuring process performance. DOI: https://doi.org/10.1108/13683040210451679

The statement is false. The Six Sigma standard refers to a process where the nearest specification limit is six standard deviations (6σ) away from the process mean. This level of performance, which accounts for a potential 1.5σ long-term shift in the process mean, corresponds to a defect rate of only 3.4 defects per million opportunities (DPMO). The statement incorrectly specifies 8 standard deviations and an unrealistic 100% containment. For a normal distribution, ±6σ from the mean contains 99.99966% of data points, not 100%.

A. True: This is incorrect because the Six Sigma methodology is defined by 6 standard deviations to the specification limits, not 8, and it corresponds to 3.4 DPMO, not 100% perfection.

1. Purdue University. (n.d.). What is Six Sigma? Purdue Online, College of Engineering. Retrieved from https://online.purdue.edu/blog/business/what-is-six-sigma. In the section "What is Six Sigma?", it states, "A Six Sigma process is one in which 99.99966% of all opportunities to produce some feature of a part are statistically expected to be free of defects. This is equivalent to 3.4 defects per million opportunities (DPMO)."

2. Antony, J., & Banuelas, R. (2002). Key ingredients for the effective implementation of Six Sigma program. Measuring Business Excellence, 6(4), 20-27. https://doi.org/10.1108/13683040210451679. On page 21, the paper defines Six Sigma as "a statistical measure of the performance of a process or a product characteristic" and clarifies that "Six Sigma quality... means that the process will be producing no more than 3.4 parts-per-million (PPM) defects."

3. Harry, M. J., & Schroeder, R. (2000). Six Sigma: The Breakthrough Management Strategy Revolutionizing the World's Top Corporations. Doubleday. In Chapter 3, "The Six Sigma Breakthrough Strategy," the concept is explained as achieving a process capability where the specification limits are ±6 standard deviations from the mean, which, after accounting for a 1.5 sigma shift, yields 3.4 DPMO.

In measurement systems analysis, accuracy and precision are distinct concepts. Accuracy refers to the closeness of the average of a set of measurements to the actual or target value. Precision refers to the closeness of the measurements to each other, indicating the degree of random variation or spread. The scenario describes data that is "generally centered relative to the targeted value," which signifies high accuracy. However, it is also "rather widely disbursed," which signifies low precision. Therefore, the data set is accurately centered on the target but lacks consistency in its measurements.

A. Precise but not accurate: This describes data points that are tightly clustered together but are far from the central target value.
C. Precise but skewed: "Precise" contradicts the "widely disbursed" nature of the data. Skewness refers to the asymmetry of a distribution, not its central tendency versus its spread.
D. Accurate but distributed: While technically correct that the data is "distributed," this term is too general. "Not precise" is the specific statistical term that correctly describes a wide disbursement.

1. Montgomery, D. C. (2013). Introduction to statistical quality control (7th ed.). Wiley. In Chapter 8, Section 8-2, "Sources of Variability," Montgomery distinguishes between accuracy ("the difference between the true value... and the observed average of the measurements") and precision ("the variability of the measurements when the measurement process is repeated"). The scenario aligns with the definition of an accurate but imprecise process.

2. MIT OpenCourseWare. (2005). 16.660J Introduction to Lean Six Sigma Methods, IAP 2012. Lecture 10: Measurement Systems Analysis. Slide 10 defines accuracy as the location of the data relative to the true value and precision as the spread of the data. A visual representation on this slide shows a target with shots that are centered on average but widely spread, labeled "Accurate, Not Precise."

3. Taylor, B. N., & Kuyatt, C. E. (1994). Guidelines for evaluating and expressing the uncertainty of NIST measurement results. National Institute of Standards and Technology (NIST) Technical Note 1297. In Appendix D, Section D.1.1.2, the document defines accuracy as the "closeness of agreement between the result of a measurement and a true value," while precision is defined as the "closeness of agreement among a set of results." This foundational document supports that a centered but widely disbursed set is accurate but not precise.

The statement is correct. The X-Y Diagram, also known as a Cause and Effect (C&E) Matrix, is a core prioritization tool used in the Measure and Analyze phases of the DMAIC (Define, Measure, Analyze, Improve, Control) methodology. Its primary function is to systematically evaluate the relationship between process inputs (the X's) and process outputs (the Y's). By scoring the impact of each input on the critical outputs, the matrix generates a ranked list of inputs. This ranking allows the project team to distinguish the "vital few" inputs that have the most significant influence on the process outcome from the "trivial many" that have little to no effect, thereby focusing improvement efforts effectively.

B. False: This is incorrect. The fundamental purpose of the X-Y Diagram is to apply a structured, data-informed approach to prioritization, which is precisely what "separating the vital few from the trivial many" describes.

1. Kubiak, T. M., & Benbow, D. W. (2017). The Certified Six Sigma Black Belt Handbook (3rd ed.). ASQ Quality Press. In Chapter 12, "Measure Phase," the section on the Cause-and-Effect (C&E) Matrix states its purpose is to "prioritize a list of potential x’s for further investigation" and "identify the 'vital few' x’s that have the most impact on the y" (p. 215).

2. Montgomery, D. C. (2020). Introduction to Statistical Quality Control (9th ed.). Wiley. Chapter 1, Section 1.4.2, "The DMAIC Process," discusses the Analyze phase where "the key variables that are most likely to create process variation are identified." The X-Y Matrix is a key tool for this identification and prioritization step.

The Voice of the Customer (VOC) is a foundational concept in Lean Six Sigma used to capture customer requirements, expectations, and needs. In the Define phase of a DMAIC project, the team assesses the VOC to understand what the customer truly values. This understanding establishes the ideal or desired state of the process, which is often termed "what should be." The primary goal of the improvement project is then to identify and close the performance gap between the current state ("what is") and this customer-defined ideal state ("what should be").

A. “What isn’t”: This option is too vague and imprecise. While it is the logical opposite of "what is," it does not specifically represent the customer's desired state or requirements for improvement.
B. “What will make money”: This reflects the Voice of the Business (VOB), which focuses on financial outcomes like profitability. While important, it is distinct from the VOC, which prioritizes customer satisfaction and requirements.
C. “What will cost less”: This is another example of the Voice of the Business (VOB) or Voice of the Process (VOP). Cost reduction is an internal business objective, not the customer's primary expectation.

1. Montgomery, D. C. (2013). Introduction to Statistical Quality Control (7th ed.). John Wiley & Sons. In Chapter 1, Section 1.3.2 "The DMAIC Process," the text explains that the Define step involves identifying the gap between current performance ("as-is") and the required performance level ("should be") based on customer needs.

2. Purdue University, Manufacturing Extension Partnership. (n.d.). Lean Six Sigma Green Belt - Define Phase. In the course materials for the Define phase, it is stated that a key activity is to "Understand the Voice of the Customer (VOC) to determine what the customer says is important... This helps define the 'should be' state for the project." (Module: Define, Section: Voice of the Customer).

3. George, M. L., Rowlands, D., & Kastle, B. (2004). What is Lean Six Sigma?. McGraw-Hill. Chapter 4, "The Define Phase," emphasizes that projects are launched to close the gap between the current state ("what is") and what the customer requires ("what should be"), which is determined by collecting the VOC.

4. Antony, J., & Banuelas, R. (2002). Key ingredients for the effective implementation of Six Sigma program. Measuring Business Excellence, 6(4), 20-27. https://doi.org/10.1108/13683040210451679. The article discusses how Six Sigma projects are initiated to address problems, which are defined as the deviation of the current state ("what is") from the desired state ("what should be"), with the desired state being heavily influenced by customer expectations (VOC).

DMAIC is the foundational, data-driven problem-solving methodology used in Six Sigma projects. The acronym represents the five sequential phases of the process: Define, Measure, Analyze, Improve, and Control. The 'Measure' phase is the second step, where the project team establishes a baseline for the process performance by collecting relevant data. This quantitative understanding of the current state ("As-Is") is crucial for identifying the root causes of problems in the subsequent 'Analyze' phase and later verifying the effectiveness of implemented solutions.

A. Manage: While project management is integral to executing a DMAIC project, "Manage" is not one of the five distinct phases of the methodology itself.
C. Memorize: Memorization is a cognitive learning activity and is not a phase in this structured, analytical process improvement framework.
D. Manipulate: This term is contrary to the ethical and objective principles of Six Sigma, which relies on accurate data and statistical analysis, not manipulation.

1. Antony, J., & Banuelas, R. (2002). Key ingredients for the effective implementation of Six Sigma program. Measuring Business Excellence, 6(4), 20-27. In Section "The Six Sigma problem solving approach (DMAIC)", page 21, the authors state, "The Six Sigma problem solving approach consists of five phases: Define, Measure, Analyse, Improve and Control (DMAIC)." DOI: https://doi.org/10.1108/13683040210451679

2. The Ohio State University, Fisher College of Business. (n.d.). The Five Phases of Lean Six Sigma. In this university courseware overview, the text explicitly states, "The Lean Six Sigma methodology is composed of five phases: Define, Measure, Analyze, Improve and Control (DMAIC)." Retrieved from https://fisher.osu.edu/blogs/lead/blog/the-five-phases-of-lean-six-sigma

3. de Mast, J., & Lokkerbol, J. (2012). An analysis of the Six Sigma DMAIC method from the perspective of problem solving. International Journal of Production Economics, 139(2), 604-614. The abstract and introduction (p. 604) define the DMAIC method as a sequence of five steps: "Define–Measure–Analyze–Improve–Control." DOI: https://doi.org/10.1016/j.ijpe.2012.05.035