Examkin

Question

Difficulty: MediumStandard and Custom Object Management

A Salesforce administrator at an agricultural technology company is designing a custom data model. The management team requests a relationship between the standard Contract object and a new custom object named Crop_Inspection__c. The requirement specifies that Crop_Inspection__c must serve as the master object and Contract must serve as the detail object so that inspection records directly control contract access and lifecycle. Which statement correctly explains why this configuration cannot be implemented in Salesforce?

  1. A
    Roll-up summary fields can only be created on parent objects connected via a Lookup relationship rather than a Master-Detail relationship.
  2. Standard objects cannot be placed on the detail side of a Master-Detail relationship with a custom object.Answer
  3. C
    Deleting a detail record in a Master-Detail relationship automatically causes the associated master record to be permanently deleted.
  4. D
    Defining a Master-Detail relationship requires configuring available picklist values under Record Type assignments prior to relationship creation.

Answer

Standard objects cannot be placed on the detail side of a Master-Detail relationship with a custom object.
In Salesforce, standard objects cannot be on the detail side of a Master-Detail relationship with a custom object. While standard objects can act as the master in a Master-Detail relationship with custom objects, they cannot inherit ownership and security from a custom object as a detail record.

Step-by-Step Solution

1
Analyze the requested data model structure.
The requirement asks for the standard object (Contract) to act as the detail record and the custom object (Crop_Inspection__c) to act as the master record.
Understanding the proposed roles for standard and custom objects is essential to evaluate platform limitations.
2
Evaluate Salesforce platform rules for Master-Detail relationships.
Salesforce allows custom objects to be on the detail side of a relationship with standard or custom master objects, but standard objects can NEVER be on the detail side of a Master-Detail relationship.
Standard objects have built-in security and ownership models that cannot be overridden by being a detail child of a custom object.
3
Select the correct architectural explanation.
The statement regarding standard objects not being allowed on the detail side accurately reflects platform capabilities.
This platform rule directly prevents the proposed configuration.

Key Concept

Standard and Custom Object Master-Detail Limitations
Rate this question

Topics

Standard and Custom Object Management

More questions from this topic