Examkin

Question

Difficulty: HardCustom Fields and Data Types

An administrator at a renewable energy company is configuring custom fields on a custom object named Installation_Site__c and updating Lead conversion settings. The administrator needs to fulfill two specific business requirements:

1. Display the sum of all estimated costs from related Maintenance_Log__c records on the parent Installation_Site__c record. Currently, Installation_Site__c and Maintenance_Log__c are connected by a Lookup relationship.
2. Ensure that when a Lead record is converted, the data stored in the custom picklist field Solar_Array_Type__c on the Lead object is populated into a custom field on the resulting Account record.

Which set of administrative actions must be taken to successfully satisfy both requirements?

  1. Convert the existing Lookup relationship on Maintenance_Log__c to a Master-Detail relationship before creating a Roll-Up Summary field on Installation_Site__c, and manually map the custom Lead field to the target custom field on the Account object in Lead Custom Field Mappings.Answer
  2. B
    Create a Roll-Up Summary field directly on Installation_Site__c using the existing Lookup relationship, and rely on standard Salesforce auto-mapping for Lead custom fields that share identical API names across objects.
  3. C
    Convert the Lookup relationship on Maintenance_Log__c to a Master-Detail relationship, but skip explicit Lead field mapping because custom fields on the Lead object automatically map to Account custom fields upon conversion.
  4. D
    Convert the relationship to Master-Detail and map the custom Lead field to the Account object, but configure the picklist values at the object level without assigning them to the relevant Account Record Types.

Answer

The administrator must convert the Lookup relationship on Maintenance_Log__c to a Master-Detail relationship before creating the Roll-Up Summary field on Installation_Site__c, and explicitly map the custom Lead field to the corresponding custom Account field within Lead Custom Field Mappings.
To summarize child record values onto a parent record using a Roll-Up Summary field, the underlying relationship must be a Master-Detail relationship. Converting the existing Lookup relationship to Master-Detail satisfies this requirement. Additionally, custom fields on the Lead object do not transfer values automatically upon conversion; administrators must explicitly define custom field mappings from the Lead object to destination Account, Contact, or Opportunity custom fields.

Step-by-Step Solution

1
Analyze relationship requirements for Roll-Up Summary fields
Roll-Up Summary fields can only aggregate data from detail records in a Master-Detail relationship. Since the objects currently use a Lookup relationship, it must first be converted to a Master-Detail relationship.
Salesforce declarative architecture prohibits Roll-Up Summary fields on Lookup relationships.
2
Determine Lead custom field mapping configuration requirements
Identify that custom Lead fields require explicit manual mapping to target custom fields on Account, Contact, or Opportunity objects in Setup.
Salesforce standard conversion logic only auto-maps standard Lead fields; custom Lead fields are ignored during conversion unless mapped.
3
Combine prerequisites to select the complete administrative solution
The correct procedure requires converting the relationship type to Master-Detail, defining the Roll-Up Summary field, and creating explicit Lead custom field mappings.
Both declarative field limits and lead conversion mapping requirements must be simultaneously satisfied.

Key Concept

Custom Field Capabilities, Roll-Up Summary Relationship Prerequisites, and Lead Conversion Custom Field Mapping
Rate this question

Topics

Custom Fields and Data Types

More questions from this topic