Examkin

Question

Difficulty: HardStandard and Custom Object Management

An administrator at a wealth management firm is configuring a custom object named Portfolio__c linked to the standard Account object. Compliance regulations mandate that deleting an Account record must NOT result in the deletion of associated Portfolio__c records. However, business leadership requires a standard roll-up calculation on the Account record to display the sum of total asset values from related Portfolio__c records. Which relationship architectural consideration must the administrator present to leadership?

  1. Standard Roll-Up Summary fields are strictly supported on Master-Detail relationships, which force cascading record deletion; a Lookup relationship with automated record updates (such as Flow) is required to meet both constraints.Answer
  2. B
    A Lookup relationship should be defined, as standard Roll-Up Summary fields can be configured natively on standard parent objects regardless of relationship type.
  3. C
    A Master-Detail relationship should be created because detail records are automatically preserved and unlinked whenever the parent Account record is deleted.
  4. D
    A Master-Detail relationship should be selected and configured with custom record type picklists to block the standard Account deletion behavior.

Answer

Standard Roll-Up Summary fields are strictly supported on Master-Detail relationships, which force cascading record deletion; a Lookup relationship with automated record updates (such as Flow) is required to meet both constraints.
The solution correctly identifies the fundamental trade-off between Salesforce relationship types. Standard Roll-Up Summary fields require a Master-Detail relationship, but Master-Detail relationships enforce cascading deletion of child records when the master is deleted. To comply with the non-deletion business constraint, the administrator must implement a Lookup relationship and use Flow automation or apex/custom tooling to handle summary calculations on the parent Account.

Step-by-Step Solution

1
Analyze the deletion retention requirement
Identified that child Portfolio__c records must survive if the parent Account is deleted.
Master-Detail relationships automatically execute cascading deletes on child records when a parent record is deleted.
2
Evaluate standard Roll-Up Summary field capabilities
Determined that standard Roll-Up Summary fields are exclusively supported on the master object in a Master-Detail relationship.
Lookup relationships do not support standard native declarative Roll-Up Summary fields.
3
Synthesize architectural recommendation
Selected a Lookup relationship to guarantee child record retention and recommended declarative automation (Flow) to calculate totals.
This combination satisfies both the non-deletion compliance rule and the summary reporting requirement.

Key Concept

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

Topics

Standard and Custom Object Management

More questions from this topic