Courseiva

SF-Data-Arch Data Modeling and Database Design Practice Question

A Salesforce architect is designing a data model for a custom object 'Invoice__c' that will have a master-detail relationship to 'Account'. The architect needs to ensure that the data model supports efficient reporting and aggregation. Which two considerations are critical when designing this master-detail relationship? (Choose two.)

⚠ Common exam trap

The trap here is assuming that child objects in a master-detail relationship can have their own sharing rules or that lookup relationships support roll-up summaries, which they do not.

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

✓

The child object inherits the sharing settings of the parent object.

Master-detail relationships enforce sharing inheritance from parent to child and enable roll-up summary fields on the parent for aggregation. These two features are critical for designing efficient reporting and security. The other options describe limitations or incorrect behaviors, such as independent sharing rules or ease of conversion, which do not apply to master-detail relationships.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    The child object inherits the sharing settings of the parent object.

    Why this is correct

    In a master-detail relationship, the child record's sharing is automatically determined by the parent's sharing settings. This means that if a user has access to the Account, they will have access to its Invoice records, unless overridden by other sharing mechanisms. This inheritance simplifies security management and is a critical consideration for data access design, making it a correct choice.

  • ✗

    The master-detail relationship can be converted to a lookup relationship at any time without restrictions.

    Why it's wrong here

    Converting a master-detail relationship to a lookup is possible only if certain conditions are met, such as no roll-up summary fields on the parent and no children with master-detail relationships to the child. It is not always possible without restrictions. This option is incorrect because it overstates the flexibility of conversion, which is limited by dependencies.

  • ✗

    The child object can have its own sharing rules independent of the parent.

    Why it's wrong here

    In a master-detail relationship, the child object cannot have its own sharing rules because it inherits the parent's sharing settings. This is by design to maintain tight coupling and simplify security. Therefore, this option is incorrect as it contradicts the fundamental behavior of master-detail relationships, which do not allow independent sharing rules on the child.

  • ✓

    Roll-up summary fields can be created on the parent object to aggregate child records.

    Why this is correct

    Master-detail relationships allow the creation of roll-up summary fields on the parent object to calculate values such as count, sum, min, or max of child records. This is essential for reporting and aggregation, as it provides real-time summarized data without additional automation. This capability is a key advantage of master-detail relationships and is a critical consideration for efficient reporting.

  • ✗

    The child object must have a lookup relationship to the parent instead of master-detail for roll-up summaries.

    Why it's wrong here

    Roll-up summary fields are only available on master-detail relationships, not on lookup relationships. Lookup relationships do not support roll-up summaries; they require automation like Apex or Flow to achieve similar aggregation. This option is incorrect because it suggests the opposite of the actual requirement, which is that master-detail is needed for roll-up summaries.

About these practice questions

This SF-Data-Arch question is part of Courseiva's 222-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

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.