Data Modeling/Database Design25% of the exam

Ownership, parent-child and lookup data skew

How ownership, parent-child (account) and lookup skew cause long sharing recalculations and record-lock errors, the 10,000-record guidance, where to place an unavoidable skewed owner, how to break lookup skew, and how group membership locking and granular locking affect realignments.

Official exam objective
Given a customer scenario, recommend approaches and techniques to avoid data skew (record locking, sharing calculation issues, and excessive child to parent relationships).

~7 min read · 15 practice questions ·

What the exam expects

  • Recognise ownership, parent-child and lookup skew from record counts and symptoms (long sharing recalculation, UNABLE_TO_LOCK_ROW errors).
  • Place an unavoidable skewed owner: no role, or its own top-level role that never moves, outside sharing-rule source groups.
  • Spread children so no parent holds more than about 10,000 records.
  • Break lookup skew with picklists, blank lookups, more lookup records, shorter saves and smaller batches.
  • Plan realignments around group membership locking and granular locking.

Key terms: ownership skew (one user owns more than 10,000 records of an object); parent-child skew (10,000 or more children under one parent account); lookup skew (very many records look up to one record); record lock (held on a lookup target while a record saves); granular locking (lets unrelated group operations run at the same time).

Key facts

Ownership skew
Detail
One user owns more than 10,000 records of an object
Skewed owner with a role
Detail
Separate top-level role, never moved, not in sharing-rule source groups
Criteria rules on skewed data
Detail
Use fields that rarely change
Parent-child skew
Detail
10,000 or more children under one account
Skewed account owner change
Detail
May re-examine sharing on every child
Lookup lock
Detail
Target record locked on each insert or update
Integration during business hours
Detail
Reduce batch size
Granular locking
Detail
Enabled by default
Partner account owner change
Detail
Counts as role reparenting
Sources for this section (6)
  • Why does parking 200,000 contacts under one account slow sharing changes?
  • When should a skewed lookup become a blank value instead of a picklist?
  • Why does changing a large partner account's owner block other admins' role changes?
  • What three things should a skewed owner that needs a role avoid?

The questions are free to read. Answers with their sources and self-grading are included with the pack.

Keep reading with the Platform Data Architect pack

  • Core concepts
  • Exam traps
  • Worked scenario

The pack includes:

  • All 21 lessons of the Platform Data Architect guide, with reading progress
  • Interactive decision walks and step-by-step sequence steppers
  • Inline practice questions and one-click topic practice (15 questions for this lesson)
  • An official source cited for every claim
  • An AI tutor that answers from the guide
  • Unlimited timed practice exams

Practice for the Platform Data Architect exam