Examkin

Question

Difficulty: MediumCustom Fields and Data Types

An administrator at a medical device company is configuring custom fields on the Lead object and a custom object named Equipment_Service_Contract__c. The administrator must ensure custom field data captured on prospects is properly transferred during lead conversion and that field availability and relationship behaviors are configured correctly across object record types. Which TWO administration considerations and data type behaviors are accurate for these custom field configurations?

  1. Custom lead fields must be explicitly mapped to custom fields on the Account, Contact, or Opportunity object in Lead Field Mapping settings to transfer data upon lead conversion.Answer
  2. B
    Roll-up summary fields can be created on a parent custom object to aggregate currency fields from child records linked via a standard Lookup relationship.
  3. When adding a custom picklist field to an object with existing record types, the new picklist values must be assigned to each record type to be available to users.Answer
  4. D
    Custom lead fields automatically map to custom fields on converted records if both fields share the exact same API name and data type.
  5. E
    Deleting a parent record in a Master-Detail relationship retains the child contract records while clearing the master lookup field value.

Answer

The two correct requirements are: 1) Custom lead fields require explicit Lead Field Mapping setup to pass data to converted Account, Contact, or Opportunity custom fields, and 2) Custom picklist values must be explicitly assigned to individual Record Types on the object before users can select them.
Custom lead fields require explicit Lead Field Mapping in Salesforce setup to map values to target custom fields on Account, Contact, or Opportunity records upon lead conversion. Additionally, when an object uses Record Types, creating a new custom picklist field requires the administrator to assign which picklist values are enabled for each specific Record Type so users can see and select them on page layouts.

Step-by-Step Solution

1
Analyze Lead conversion mapping requirements for custom fields.
Confirm that custom lead fields require explicit administrative mapping under Object Manager > Lead > Fields & Relationships > Map Lead Fields.
Automatic field mapping by matching API name does not occur in Salesforce.
2
Evaluate picklist field creation behavior when Record Types exist.
Recognize that creating a picklist field does not automatically enable its values on existing object record types.
Picklist value visibility and selection availability are controlled per record type.
3
Verify relationship and roll-up constraints.
Confirm roll-up summaries are exclusive to Master-Detail relationships, and deleting a Master record deletes detail children.
Lookup relationships do not support native roll-up summary fields.

Key Concept

Custom Field Administration, Picklist Record Type Assignment, and Lead Mapping
Estimated Time:1m 30s
Rate this question

Topics

Custom Fields and Data Types

More questions from this topic