Examkin

Question

Difficulty: HardStandard and Custom Object Management

An administrator at a global telecommunications company needs to track service warranties using a custom object named Equipment_Warranty__c. The object currently has an existing Lookup relationship to the standard Asset object. The business requires calculating the sum of claim amounts directly on the Asset record using a Roll-Up Summary field and ensuring that deleting an Asset automatically deletes all associated Equipment_Warranty__c records. However, several existing Equipment_Warranty__c records currently have null values in their Asset lookup field. Which sequence of actions must the administrator perform to satisfy these business requirements?

  1. Populate the Asset field on all existing Equipment_Warranty__c records, convert the relationship to Master-Detail, and then create the Roll-Up Summary field on the Asset object.Answer
  2. B
    Create the Roll-Up Summary field on the Asset object directly using the existing Lookup relationship without converting the field type.
  3. C
    Convert the Lookup field to a Master-Detail relationship immediately, allowing Salesforce to automatically reassign orphan Equipment_Warranty__c records to a default Asset.
  4. D
    Configure Dynamic Forms field visibility on the Equipment_Warranty__c page layout to make the Asset field mandatory before creating a summary formula field.

Answer

Populate the Asset field on all existing Equipment_Warranty__c records, convert the relationship to Master-Detail, and then create the Roll-Up Summary field on the Asset object.
The requirement to calculate aggregated child values via native Roll-Up Summary fields and enforce automatic cascading deletion necessitates a Master-Detail relationship. Converting a Lookup field to a Master-Detail field requires that every existing record has a populated parent lookup value. Therefore, populating all null values, converting the relationship, and creating the Roll-Up Summary field is the correct sequence.

Step-by-Step Solution

1
Analyze requirement dependencies
Roll-Up Summary fields and cascading record deletion both require a Master-Detail relationship between the parent (Asset) and child (Equipment_Warranty__c) objects.
Standard lookup relationships do not support native roll-up summary functionality or automatic deletion of child records.
2
Evaluate data prerequisites for relationship conversion
Identify that existing child records with null lookup values will prevent changing the relationship type to Master-Detail.
Master-Detail fields are mandatory on child records; Salesforce enforces that every existing record must have a parent populated before conversion.
3
Execute conversion and configuration sequence
Populate all blank Asset values, convert the field to Master-Detail, and construct the Roll-Up Summary field on the Asset object.
Once all records have valid parent pointers and the field is converted to Master-Detail, Roll-Up Summary fields can be successfully created on the parent.

Key Concept

Converting Lookup Relationships to Master-Detail and Roll-Up Summary Field Eligibility
Estimated Time:2m 0s
Rate this question

Topics

Standard and Custom Object Management

More questions from this topic