Examkin

Question

Difficulty: Very hardCustom Fields and Data Types

An administrator at a global logistics firm is updating custom field architecture and field mapping configurations across custom objects and the Lead object. The administrator needs to convert existing relationship fields, configure custom lead mapping for lead conversion, and set up summary reporting on parent records.

Which two statements accurately describe the requirements and constraints when managing custom field conversions and relationship field capabilities in Salesforce?

  1. Converting a Lookup relationship field to a Master-Detail relationship field requires that all existing records on the child object have a populated value in the lookup field.Answer
  2. Converting a Master-Detail relationship field to a Lookup relationship field is prevented if any Roll-up Summary fields on the parent object reference the detail object.Answer
  3. C
    Roll-up summary fields can be created on a parent object regardless of whether the child object is connected using a Lookup or a Master-Detail relationship.
  4. D
    Custom fields created on the Lead object can be mapped directly to existing standard fields on the Contact or Opportunity object during lead conversion.
  5. E
    Creating a new custom picklist field automatically assigns and enables all picklist values for all existing record types on that object.

Answer

Converting a Lookup relationship field to a Master-Detail relationship requires that all existing child records have a populated lookup field value. Furthermore, converting a Master-Detail relationship to a Lookup relationship is blocked if any Roll-up Summary fields on the parent object reference the child object.
Converting a Lookup relationship to a Master-Detail relationship is only permitted if every existing record on the child object contains a valid parent reference, as Master-Detail relationships require every detail record to have a master record. Additionally, converting a Master-Detail relationship to a Lookup relationship is prohibited if the master object contains Roll-up Summary fields that aggregate data from the detail object, because Roll-up Summary functionality is strictly dependent on Master-Detail architecture.

Step-by-Step Solution

1
Analyze relationship conversion requirements from Lookup to Master-Detail.
Identify that because Master-Detail relationships enforce mandatory parentage on detail records, all existing child records must have a populated lookup field before conversion is allowed.
Salesforce prevents orphaned records in Master-Detail relationships.
2
Analyze relationship conversion restrictions from Master-Detail to Lookup.
Identify that Roll-up Summary fields rely on Master-Detail relationship behavior.
If Roll-up Summary fields exist on the master object, the Master-Detail relationship cannot be changed to a Lookup until those Roll-up Summary fields are deleted.
3
Evaluate relationship limits for Roll-up Summary fields, Lead field mapping rules, and record type picklist assignments to eliminate distractors.
Confirm that Roll-up Summary fields require Master-Detail relationships, Lead custom fields can only map to custom fields on target objects, and picklist values must be manually assigned per record type.
These restrictions represent fundamental platform boundaries in Salesforce field configuration.

Key Concept

Custom Field Data Type Conversion and Relationship Field Constraints
Rate this question

Topics

Custom Fields and Data Types

More questions from this topic