SF-Data-Arch Data Modeling and Database Design Practice Question
Universal Containers requires a data model where a Child object must have exactly one Parent object that is mandatory. If the Parent is deleted, the Child must be deleted. Which relationship should the Architect select?
⚠ Common exam trap
Candidates might choose a Lookup relationship with required configuration, missing that only Master-Detail relationships guarantee strict lifecycle dependency and cascade deletion.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Master-Detail relationship
A Master-Detail relationship creates a tight coupling where the child's lifecycle is strictly governed by the parent. Deleting the parent automatically triggers a cascade delete of all associated children. This is essential for maintaining referential integrity in parent-child hierarchies where the child cannot exist in isolation, ensuring the database remains clean and logically consistent without requiring custom automation for cleanup tasks.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Lookup relationship
Why it's wrong here
A standard lookup relationship allows the child record to exist without a parent. Deleting the parent does not force a deletion of the child record, and the lookup field can be set to null, which violates the requirement for a mandatory association and automatic deletion.
- ✗
Self-relationship
Why it's wrong here
A self-relationship is used when an object references another record of the same type. This does not inherently enforce a parent-child lifecycle or cascade delete behavior. It is designed for structures like hierarchical accounts or reporting lines rather than enforcing mandatory parent-child dependency requirements.
- ✓
Master-Detail relationship
Why this is correct
Master-Detail relationships enforce a strict ownership model where the child record is dependent on the parent. The relationship field is mandatory, and the system automatically enforces a cascade delete when the parent is deleted, directly satisfying the requirement for mandatory association and lifecycle management.
- ✗
External lookup relationship
Why it's wrong here
External lookup relationships connect Salesforce objects to external systems via an External ID. They do not support cascade delete behavior or the mandatory field requirements necessary for internal parent-child lifecycle management. They are designed for data integration scenarios, not for managing internal relational dependencies.
About these practice questions
One of 222 original SF-Data-Arch practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-Data-Arch practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Data-Arch exam.