Design review prototypeNot for students

BUSM1042Analyst JourneyBack to journey map

Module 03 · Week 3 · Individual mission

Find Data Quality Problems Before Fixing Them

Diagnose the quality problem before changing the data.

About 7 minutes. There is no timer.Formative practice only. No assessment marks.1 Insight Capsule on completionSLO3SLO5
Mission statusNot started
  1. 1BriefingCurrent
  2. 2Worked exampleNext
  3. 3Case boardNext
  4. 4CheckpointsNext
  5. 5ReflectionNext
  6. 6CompleteNext

Start here

Briefing

A clean-looking table can still contain missing, duplicated, or inconsistent records.

Your job is to diagnose the problem, choose a defensible cleaning rule, and verify that the rule did not hide information.

Practice boundary

Your answers and progress are kept only while this page remains open. Refreshing or closing the page resets them. Your answers are not stored on this device or sent to a server.

Game economy

Build Momentum without risking XP

+3Correct checkpoint
−1First incorrect check in a checkpoint
100 XPAlways recoverable through retry

You begin with 3 Momentum. Any held points return when you solve that checkpoint. Momentum never falls below zero and never changes assessment marks. Complete the mission to open one transparent reward draw.

What you will practise

  1. Recommend a cleaning action that matches a stated data quality problem.SLO3
  2. Evaluate a cleaning process by comparing the original, rule, and result.SLO5
  3. Explain why an analyst should not silently guess a missing or conflicting value.SLO5

3 terms for this mission

Completeness
Whether required values are present.
Consistency
Whether the same rule or format is used across records.
Data cleansing
A documented process for finding, correcting, or flagging data quality problems.

All businesses, people, and data in this mission are fictional.