Objects and Applications19% of the exam
Master-detail, lookup and junction object relationships
How to choose between master-detail, lookup, hierarchical and junction designs from ownership, sharing, deletion, roll-up and data-volume requirements, how to convert a lookup that already holds data, and what blocks deleting an object that sits in a relationship.
Given a scenario, determine the appropriate solution to enhance or extend objects (master-detail, lookup, junction object, related list, record type, Schema Builder, and Object Creator).
~8 min read · 11 practice questions ·
What the exam expects
- Choose master-detail, lookup, two lookups, a junction or a hierarchical relationship from the requirements.
- Add master-detail to an object that holds records; predict what conversion does to sharing and reports.
- Roll up and report across multilevel master-detail relationships.
- Build a junction object: primary master, related lists, icons, roll-ups.
- Diagnose blocked object deletion and missing field history.
Key terms:
- Master-detail: the master controls the detail's owner, security and deletion.
- Lookup: a looser link; the child keeps its own owner and sharing.
- Junction object: a custom object with two master-detail relationships (many-to-many).
- Primary master: the junction's first master-detail relationship.
- Hierarchical relationship: a User-only lookup that can't loop back to the same user.
Key facts
Relationships per custom object
- Detail
- Up to 2 master-detail and up to 40 total
Child volume best practice
- Detail
- Don't exceed 10,000 child records for a master-detail relationship
Object already has data
- Detail
- Create a lookup, fill every record, convert to master-detail
Master-detail to lookup
- Detail
- Blocked while the master has roll-up summary fields
Delete this record also
- Detail
- Cascade-delete, disabled by default; contact Salesforce to enable
Junction primary master
- Detail
- First master-detail created; sets look and feel, Owner value and division
Junction roll-ups
- Detail
- Can be created on both masters
Master-side custom object
- Detail
- Can't be deleted; deleting the detail side converts the field to a lookup
- Why can't detail-side custom objects use queues or manual sharing?
- When can a lookup be converted to master-detail?
- Why might custom reports stop working after a relationship conversion?
- What does field history on a child show when its lookup parent is deleted?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform Administrator II pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 29 lessons of the Platform Administrator II guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams