Diagnostics C14-001–012
C14-001 — A
Why correct: Chapter 14 links the topics but distinguishes the Big Data environment/management challenge from the Data Science analytical process.
A: Correct.
B: “Big” is relative; DMBOK does not define a fixed 100-TB boundary.
C: Both can involve many structures/forms.
D: Historical vs real-time is not the distinction.
Source: pp. 471–474 · Confusion: Big Data vs Data Science · Tag: vocabulary confusion
C14-002 — B
Why correct: Descriptive analytics is hindsight-oriented: what happened and why.
A: Predictive asks what is likely next.
B: Correct.
C: Prescriptive recommends action.
D: Reinforcement is a learning approach, not this analytics horizon.
Source: pp. 474–475 · Confusion: Descriptive vs Predictive · Tag: vocabulary confusion
C14-003 — C
Why correct: A churn probability estimates a future outcome; it does not recommend an intervention or necessarily run in a live operational loop.
A: Not historical explanation.
B: No action recommendation.
C: Correct.
D: No live operational stream/trigger is stated.
Source: pp. 474–475, 481–483 · Confusion: Predictive vs Prescriptive vs Operational · Tag: confusion pair
C14-004 — D
Why correct: The changed fact is a recommended action intended to influence the predicted outcome.
A: Not historical description.
B: Prediction is present, but recommendation adds prescriptive logic.
C: Profiling characterizes data; it does not recommend interventions.
D: Correct.
Source: pp. 481–482 · Confusion: Predictive vs Prescriptive · Tag: missed qualifier
C14-005 — A
Why correct: The chapter follows iterative scientific reasoning: observations and results can change requirements, source choices, hypotheses, and models before/after deployment.
A: Correct.
B: It does not require using every possible source.
C: Business need remains the starting point.
D: Iteration does not mean uncontrolled redeployment after every record.
Source: pp. 474–476, 490–491 · Confusion: Iteration vs lack of requirements · Tag: sequence/process
C14-006 — B
Why correct: Technical novelty without a business decision/value does not pass the chapter's value and feasibility gate.
A: Large data does not justify speculative production.
B: Correct.
C: Lower latency cannot create missing business value.
D: More training data cannot define the purpose.
Source: pp. 484–485, 489–491, 496–497 · Confusion: Business value vs technical novelty · Tag: best-action error
C14-007 — C
Why correct: Viscosity is difficulty using/integrating the data.
A: Velocity = speed.
B: Volatility = change/useful life.
C: Correct.
D: Veracity = trustworthiness.
Source: pp. 476–477 · Confusion: Viscosity vs Velocity/Volatility/Veracity · Tag: vocabulary confusion
C14-008 — D
Why correct: Volatility describes change frequency/useful life; the clue asks how long the feed remains valuable.
A: Velocity is generation/capture speed.
B: Volume is amount.
C: Variety is forms/structures.
D: Correct.
Source: pp. 476–477 · Confusion: Velocity vs Volatility · Tag: confusion pair
C14-009 — A
Why correct: The distinction is processing order: ETL transforms before load; ELT loads first and transforms/integrates for use later.
A: Correct.
B: Not an absolute structured/unstructured division.
C: Both require Metadata/Data Management.
D: Real-time vs batch is not the defining distinction.
Source: pp. 471–472, 476–478 · Confusion: ETL vs ELT · Tag: confusion pair
C14-010 — B
Why correct: The files are raw but managed, discoverable, contextualized, and quality-tagged. Raw data alone does not make a swamp.
A: Raw can be legitimate in a lake.
B: Correct.
C: A lake need not first become a relational warehouse.
D: Storage-before-transformation does not define a speed layer.
Source: pp. 478–480, 499–500 · Confusion: Lake vs Swamp · Tag: overgeneralization
C14-011 — C
Why correct: The services pattern uses batch for completeness, speed for recent data, and serving for the combined consumer view.
A: Speed alone loses required history.
B: Batch alone misses required current events.
C: Correct.
D: Swamp is a management failure, not architecture.
Source: pp. 479–480 · Confusion: Batch vs Speed vs Serving · Tag: architecture selection
C14-012 — D
Why correct: Low latency must be justified by actionable business timing and value; the business acts only daily.
A: Real-time is not inherently better.
B: Expense/flexibility does not override value.
C: Removing monitoring is not an acceptable trade.
D: Correct.
Source: pp. 479–480, 484–485, 496–497 · Confusion: Latency vs cost/value · Tag: overthinking