CRT-211 · Question #154
Cloud Kicks has been tracking how many participants wear the company's shoes in each marathon. The administrator creates two custom objects: Races and Runners. There is a master- detail relationship…
The correct answer is A. Change the field type to a Lookup Relationship. Changing the field type to a Lookup Relationship will allow deleting the Relationship field without deleting the Runners records. A lookup relationship creates a loose association between two objects, where the child records do not depend on the parent records for their…
Question
Cloud Kicks has been tracking how many participants wear the company's shoes in each marathon. The administrator creates two custom objects: Races and Runners. There is a master- detail relationship between them as well as a Roll-up Summary field on the Races object to show the count of runners in each race. Requirements have changed, and the administrator wants to delete the Master-detail Relationship field without deleting the Runners records. What action should an administrator take before the Relationship field can be deleted?
Options
- AChange the field type to a Lookup Relationship.
- BSelect the Allow Reparenting' checkbox on the Master-detail field.
- CUncheck 'Delete this record also' to turn off cascading deletes.
- DDelete the Roll-up Summary field on the parent.
How the community answered
(31 responses)- A77% (24)
- B13% (4)
- C3% (1)
- D6% (2)
Explanation
Changing the field type to a Lookup Relationship will allow deleting the Relationship field without deleting the Runners records. A lookup relationship creates a loose association between two objects, where the child records do not depend on the parent records for their existence. A lookup relationship can be deleted without affecting the child records, unlike a master-detail relationship that enforces cascading deletes.
Topics
Community Discussion
No community discussion yet for this question.