Universal Containers has a support process that allows users to request support from its engineering team using a custom object, Engineering_Support__c.
Users should be able to associate multiple Engineering_Support__c records to a single Opportunity record. Additionally, aggregate information about the Engineering_Support__c records should be shown on the Opportunity record.
What should a developer implement to support these requirements?
To associate multiple Engineering_Support__c records to a single Opportunity record and show aggregate information about the Engineering_Support__c records on the Opportunity record, a master-detail relationship should be implemented. The correct setup is a master-detail field from Engineering_Support__c to Opportunity. This establishes Opportunity as the master and Engineering_Support__c as the detail, enabling the creation of roll-up summary fields on Opportunity to aggregate data from Engineering_Support__c records.
I think the correct wording is from "child" to "master"... So, being that in this case we need Engineering_Support__c to be the child and Opportunity to be the master, in order to have one Opp related to many ES's and one ES to only one Opp. In order to setup this relationship you have to navigate to the ES object and do the setup there, you always to the setup in the object that will be on the detail side (child). Also, in order to setup a rollup summary field on the Opp that aggregates data from the ESs it's a requierment that Opp is the master and ES the child, to see it available.
Option A is the correct choice because when a Master-detail field is created from the parent Opportunity object to the child Engineering_Support__c object, it enforces a one-to-many relationship where each Engineering_Support__c record can be associated with only one Opportunity record. This ensures that each Engineering_Support__c record is related to a specific Opportunity record, and multiple Engineering_Support__c records can be associated with a single Opportunity record.
Your Point is correct that Opportunity should be the parent, but option D is correct as We have to create M-D Relation from Engineering_Support__c to Opportunity
I thought standard object cannot be detailed of the master details relationship
Only User and Lead Object do not support this type of relationship, the rest yes!
if it's going to be shown in the Opportunity then the field is a roll-up summary on the master. isn't the supposed to be letter A?
Why would be the D? Standard Objects can't be on the detail side, either the question is wrong or the answers are wrong.
Nvm, D is absolutely correct.
When we create M-D field we can see this onformation: Master-Detail Relationship: Creates a special type of parent-child relationship between this object (the child, or "detail") and another object (the parent, or "master") where....