androidengineers.Book a session

Data readiness and migration

Lab: produce a data-readiness report

exerciseSelf-paced

Assignment

Create 25 synthetic records containing duplicates, missing owners, two formats, stale versions, and one deletion event.

Build sequence

  1. Profile completeness and permissions by source category.
  2. Define transformation and rejection rules with provenance fields.
  3. Run ingestion twice and reconcile source, accepted, rejected, and indexed IDs.
  4. Apply updates and deletions and inspect derived records.

Acceptance checks

  • Every source record has an accounted-for outcome.
  • Repeated ingestion does not duplicate records.
  • The report identifies which data gaps block a pilot and who can resolve them.

Evidence to keep

Submit the working artifact or decision document described above, the inputs used, and the observed results for every acceptance check. Include one failed attempt and the change you made after investigating it. Label fixture-based outcomes separately from live-system measurements. These artifacts become part of your final portfolio review.

YOUR LEARNING JOURNEY

0 of 119 available lessons completed

Progress saved in this browser. No account needed.
Lab: produce a data-readiness report | Forward Deployed Engineer | Android Engineers