Question

Difficulty: MediumObject Relationships (Lookup, Master-Detail, Many-to-Many)

An administrator needs to configure a relationship between a custom object named Asset_Maintenance__c and the standard Account object. The business requires that Asset_Maintenance__c records can exist independently without requiring an Account to be assigned. Additionally, management requests a native summary count of all related maintenance records displayed on the Account record page. Which assessment of this design requirement is correct?

  1. A Lookup relationship must be used to allow independent records, but standard Roll-Up Summary fields will not be supported on the Account object.Answer
  2. B
    A Lookup relationship should be configured, which will allow the administrator to create a standard Roll-Up Summary field on the Account object.
  3. C
    A Master-Detail relationship should be used because deleting an Account record will preserve all associated Asset_Maintenance__c records.
  4. D
    A Master-Detail relationship should be configured because it allows child records to be created without selecting a parent record.

Answer

A Lookup relationship must be used to allow independent records, but standard Roll-Up Summary fields will not be supported on the Account object.
Choosing a Lookup relationship satisfies the requirement that child records can exist without a parent Account. However, because native Roll-Up Summary fields in Salesforce require a Master-Detail relationship, the administrator cannot use a standard Roll-Up Summary field on Account for a Lookup relationship.

Step-by-Step Solution

1
Evaluate the requirement for record independence
Since child records must exist without a parent Account, a Lookup relationship is required because Master-Detail relationships mandate a parent record.
Master-Detail fields are mandatory on detail record creation.
2
Evaluate the Roll-Up Summary field requirement
Native Salesforce Roll-Up Summary fields are exclusively available on the master object in a Master-Detail relationship.
Lookup relationships do not support native Roll-Up Summary fields.
3
Synthesize the architecture limitations
To meet the independence requirement, a Lookup relationship must be chosen, acknowledging that native Roll-Up Summary functionality will not be natively supported on Account.
Salesforce object architecture rules prohibit native roll-ups over lookup fields.

Key Concept

Lookup vs. Master-Detail relationship capabilities and Roll-Up Summary field limitations
Rate this question