SF-Data-Arch Data Modeling and Database Design Practice Question
A Salesforce architect is designing a data model for a custom object that must support a strict one-to-many relationship where each child record must have a parent, and the parent's sharing settings should automatically control child record access. The architect also needs to ensure that deleting a parent cascades to delete all related children. Which relationship type should be used?
⚠ Common exam trap
The trap here is assuming that a lookup relationship with a required field and cascade delete can replicate master-detail sharing inheritance and mandatory parent enforcement.
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 is the only standard relationship that enforces a required parent, inherits the parent's sharing settings, and automatically deletes children when the parent is deleted. The other options either lack sharing inheritance, are limited to User, or model a different cardinality. Therefore, the master-detail relationship meets all stated requirements without custom automation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Hierarchical relationship
Why it's wrong here
A hierarchical relationship is a special lookup used only on the User object to model a manager-subordinate structure. It cannot be used on custom objects to create a general one-to-many relationship. This option is incorrect because it is limited to User and does not support the required sharing inheritance or cascade delete behavior for arbitrary custom objects.
- ✓
Master-detail relationship
Why this is correct
Master-detail relationships enforce that every child record must have a parent, inherit the parent's sharing settings, and automatically cascade delete child records when the parent is deleted. This exactly matches the requirements for strict one-to-many, controlled sharing, and cascade deletion. It is the correct choice because it provides all three needed behaviors natively without workarounds.
- ✗
Lookup relationship with required field and cascade delete
Why it's wrong here
A lookup relationship with a required field enforces that a parent is specified, but it does not automatically inherit sharing or provide cascade delete. Cascade delete can be set, but sharing inheritance is not guaranteed. This option fails because the scenario explicitly requires parent-controlled sharing and automatic cascade deletion, which are core behaviors of master-detail relationships, not lookups.
- ✗
Many-to-many relationship via junction object
Why it's wrong here
A many-to-many relationship uses a junction object with two master-detail relationships to connect two objects. It is designed for many-to-many scenarios, not strict one-to-many. While it can enforce required parents and cascade delete, it introduces unnecessary complexity and does not match the stated one-to-many requirement, making it the wrong choice here.
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.