Examkin

Question

Difficulty: Very hardCustom Fields and Data Types

A Salesforce administrator at a biotechnology company is auditing custom field architecture on a custom Clinical Trial object and refining the Lead conversion process. The administrator needs to convert an existing custom Lookup relationship on Clinical Trial to a Master-Detail relationship, configure field data retention for prospect leads, and calculate total trial budgets. Which two statements accurately describe the technical requirements and platform behaviors associated with these custom field and relationship configurations? (Select 2)

  1. To convert a custom Lookup relationship field to a Master-Detail relationship, every existing detail record must have a populated value in that lookup field prior to conversion.Answer
  2. Custom fields on the Lead object must be explicitly mapped to custom fields on the Account, Contact, or Opportunity objects within Lead Conversion Field Mapping to transfer data upon lead conversion.Answer
  3. C
    A standard Roll-Up Summary field can be created on a parent object to aggregate numeric custom field data from child records linked via a custom Lookup relationship.
  4. D
    Custom fields created on the Lead object automatically map to custom fields on the Contact object if both custom fields share identical API names and compatible data types.
  5. E
    Creating a new custom Record Type on an object automatically assigns and enables all existing custom picklist field values for that Record Type.

Answer

The correct statements are that all existing detail records must have a populated lookup value before converting a lookup relationship to master-detail, and custom lead fields require explicit administrator mapping to custom fields on Account, Contact, or Opportunity objects for data to transfer during lead conversion.
The correct choices identify fundamental platform rules for custom fields and object relationships. First, converting a custom lookup relationship to a master-detail relationship requires every child record to have a populated lookup field value because master-detail relationships enforce required parent records. Second, custom fields on the Lead object do not convert automatically; an administrator must explicitly map custom Lead fields to target custom fields on the Account, Contact, or Opportunity objects.

Step-by-Step Solution

1
Evaluate relationship field type conversion prerequisites.
Converting a Lookup field to a Master-Detail field requires that every existing record on the child object contains a valid parent record reference, as Master-Detail records cannot exist without a parent.
Master-Detail relationships enforce mandatory parentage and cascading deletion behaviors.
2
Evaluate Lead conversion custom field mapping rules.
Lead conversion requires manual mapping of custom Lead fields to custom target fields on Account, Contact, or Opportunity.
Automatic field mapping only occurs for standard Lead fields; matching API names do not trigger auto-mapping.
3
Verify Roll-Up Summary field capabilities across relationship types.
Roll-Up Summary fields are restricted to Master-Detail relationships.
Lookup relationships do not support native declarative roll-up summary fields.

Key Concept

Custom Field Data Types and Relationship Conversion Limits
Rate this question

Topics

Custom Fields and Data Types

More questions from this topic