A Salesforce Administrator needs to model a relationship between a custom object named Subscription__c and a custom object named Server__c. A single subscription can be assigned to multiple servers, and a server can host multiple subscriptions. The business requires tracking assignment metadata, such as Activation Date, on each association. Additionally, if either a Subscription__c or Server__c record is deleted, the association record must be automatically removed. Which TWO configuration steps should the administrator perform to satisfy these business requirements? (Select 2 answers)
- Create a custom junction object containing two Master-Detail relationship fields pointing to Subscription__c and Server__c.Answer
- Create custom fields, such as Activation Date, directly on the newly created junction object.Answer
- CCreate a custom junction object with two Lookup relationship fields configured to restrict record deletion.
- DCreate a Roll-Up Summary field on the Subscription__c object referencing a direct Lookup relationship field on Server__c.
Answer
The administrator must create a custom junction object containing Master-Detail relationships to both Subscription__c and Server__c, and add the necessary custom metadata fields directly onto that junction object.
To model a Many-to-Many relationship with automatic deletion cascading and custom fields per association, an administrator must create a custom junction object. Linking this junction object to both parent objects via Master-Detail relationships ensures that deleting either parent record automatically deletes the junction record. Custom fields for metadata like Activation Date can be created directly on the junction object.
Step-by-Step Solution
Key Concept
Many-to-Many Relationships via Junction Objects