Question

Difficulty: HardStandard and Custom Object Management

An administrator at a medical technology company is configuring a custom data model for tracking equipment maintenance. The business requires that every maintenance log record must be linked to a master diagnostic equipment record, and deleting a diagnostic equipment record must automatically remove all associated maintenance log records. Additionally, management needs to view the total cost of all maintenance performed directly on the master diagnostic equipment record. Which two configuration steps should the administrator take to meet these requirements?

  1. Create a Master-Detail relationship field on the Equipment Maintenance object referencing the Diagnostic Machine object.Answer
  2. Create a Roll-Up Summary field on the Diagnostic Machine object to aggregate total costs from related Equipment Maintenance records.Answer
  3. C
    Create a Lookup relationship field on the Equipment Maintenance object and build a Roll-Up Summary field on the Diagnostic Machine object.
  4. D
    Create a Lookup relationship field on the Equipment Maintenance object and enable standard cascading deletion on the lookup definition.

Answer

The administrator must create a Master-Detail relationship field on the Equipment Maintenance object referencing the Diagnostic Machine object, and create a Roll-Up Summary field on the Diagnostic Machine object to aggregate cost values.
Establishing a Master-Detail relationship on the child object (Equipment Maintenance) ensures that child records inherit ownership and are automatically deleted if the parent Diagnostic Machine record is deleted. Furthermore, Master-Detail relationships enable the creation of standard Roll-Up Summary fields on the parent master object to aggregate numeric values such as total maintenance costs.

Step-by-Step Solution

1
Analyze record dependency and cascading deletion requirements.
Automatic cascading deletion requires a Master-Detail relationship rather than a Lookup relationship.
Master-Detail relationships strictly enforce parent record presence and automatically delete child records when the master record is deleted.
2
Analyze total cost aggregation requirement on the parent object.
A Roll-Up Summary field must be created on the parent Diagnostic Machine object.
Roll-Up Summary fields allow declarative SUM aggregation of child record numeric fields directly on the master object in a Master-Detail relationship.

Key Concept

Standard and Custom Object Relationships and Aggregations
Rate this question