Examkin

Soru

Zorluk: ZorCustom Fields and Data Types

An administrator at a medical equipment manufacturer is configuring custom fields on the Equipment_Inspection__c custom object to meet two distinct business requirements:

1. Display the calculated sum of inspection costs from related Inspection_Item__c records, which are currently linked to Equipment_Inspection__c through a Lookup relationship.
2. Ensure custom Lead fields created to track specialized customer inspection requirements automatically pass data to target records during Lead conversion.

Which two considerations or platform limitations must the administrator keep in mind when configuring these custom fields? (Select 2)

  1. Roll-up summary fields cannot be created on a parent object linked to child records via a Lookup relationship; the relationship must be Master-Detail or managed via flow automation.Cevap
  2. Custom Lead fields can only be mapped to custom fields on the target Account, Contact, or Opportunity objects during Lead conversion, not to standard fields.Cevap
  3. C
    Deleting an Equipment Inspection parent record automatically deletes all associated Inspection Item child records connected via a Lookup relationship.
  4. D
    Creating a new custom picklist field automatically assigns all picklist values to all existing Record Types on the object without administrator intervention.
  5. E
    Custom Lead fields will automatically map to standard fields on converted records if the field labels match exactly.

Cevap

The administrator must account for the platform rule that native roll-up summary fields can only be created on parent objects in a Master-Detail relationship (or handled via automation for Lookup relationships), and the rule that custom Lead fields can only map to custom target fields on the Account, Contact, or Opportunity objects during conversion.
The correct selections address key platform rules for custom fields: native roll-up summary fields are exclusively available when objects are bound by a Master-Detail relationship, and Lead field mapping requires mapping custom Lead fields explicitly to custom target fields on the destination objects.

Adım Adım Çözüm

1
Analyze requirement 1 regarding calculating total costs from child records over a Lookup relationship.
Identify that native Roll-Up Summary fields are restricted to Master-Detail relationships.
Lookup relationships do not support native declarative Roll-Up Summary fields unless the relationship is converted to Master-Detail or summary values are aggregated using Record-Triggered Flows.
2
Analyze requirement 2 regarding custom field data flow during Lead conversion.
Identify Lead custom field mapping constraints.
Custom fields on the Lead object must be explicitly mapped to corresponding custom fields on Account, Contact, or Opportunity; mapping directly to standard target fields is not supported.
3
Evaluate potential distractors regarding relationship deletion behaviors, record type picklists, and automatic mapping.
Eliminate incorrect choices based on core Salesforce field and data structure rules.
Lookup relationships do not cascade delete child records, picklist values must be configured per Record Type manually, and Lead mapping is never automatic by label matching.

Anahtar Kavram

Custom Field Capabilities and Limitations across Relationships and Lead Conversion
Bu soruyu puanla

Konular

Custom Fields and Data Types

Bu konudan daha fazla soru