Examkin

Question

Difficulty: Very hardObject Relationships (Lookup, Master-Detail, Many-to-Many)

An administrator at Cloud Kicks is designing a custom object schema for tracking Customer Invoices related to Accounts. The business analyst presents three mandatory requirements:
1. Deleting an Account record must not delete its associated Invoice records.
2. The total dollar amount of all related Invoices must be displayed on the Account record using a standard declarative roll-up field without writing custom code or Apex triggers.
3. Invoices must maintain independent Organization-Wide Defaults (OWD) and sharing access from Accounts.

Which architectural constraint prevents fulfilling all three requirements using standard declarative relationship features alone?

  1. Standard roll-up summary fields require a Master-Detail relationship, which automatically cascades record deletion to child records and forces child records to inherit the parent object's sharing permissions.Answer
  2. B
    Lookup relationships support standard roll-up summary fields only when the lookup field is configured as a required field on the child object layout.
  3. C
    Master-Detail relationships allow child records to maintain independent Organization-Wide Defaults if the 'Allow Reparenting' setting is enabled on the relationship field.
  4. D
    Converting a Lookup relationship to a Master-Detail relationship preserves existing custom sharing rules and role hierarchy access settings on the child object.

Answer

Standard roll-up summary fields require a Master-Detail relationship, which automatically cascades record deletion to child records and forces child records to inherit the parent object's sharing permissions.
Standard declarative roll-up summary fields are strictly supported only on Master-Detail relationships. However, Master-Detail relationships enforce two mandatory platform behaviors: deleting the master record cascades deletion to all detail records, and detail records inherit their access controls ('Controlled by Parent') from the master record. Because requirements 1 and 3 mandate independent security and preservation of records upon deletion, standard declarative tools alone cannot satisfy all three criteria without custom automation such as Record-Triggered Flows or Apex.

Step-by-Step Solution

1
Analyze Requirement 1 and Requirement 3 regarding record deletion behavior and security access controls.
Requirements 1 and 3 require that child records survive parent deletion and maintain independent sharing settings, which are characteristics of a Lookup relationship.
Lookup relationships allow independent security settings (OWD) and prevent cascading deletion of child records.
2
Analyze Requirement 2 regarding parent object summary calculations.
Requirement 2 demands a standard declarative roll-up summary field on the Account object.
Standard declarative roll-up summary fields are functionally restricted to Master-Detail relationships.
3
Evaluate platform relationship constraints against all three requirements.
Configuring a Master-Detail relationship enables standard roll-up summaries, but automatically enforces cascade deletion and forces child security to be 'Controlled by Parent'.
Standard declarative features cannot simultaneously support roll-up summary fields while preserving independent security and deletion behavior.

Key Concept

Master-Detail vs. Lookup Relationship Capabilities and Constraints
Estimated Time:2m 0s
Rate this question

Topics

Object Relationships (Lookup, Master-Detail, Many-to-Many)

More questions from this topic