Salesforce Data-Architect Exam With Confidence Using Practice Dumps

A required Lookup relationship ensures that the Shipment record must have a value for each of the three parent records, and also prevents the deletion of those parent records if they are referenced by a Shipment record. A Master-Detail relationship would not allow separate sharing models for each custom object, and a VLOOKUP formula field would not enforce the relationship or prevent deletion

 creating multiple similar products and distributing the skew across those products can be a way to mitigate issues related to lookup skew. The article explains that lookup skew happens when a very large number of records are associated with a single record in the lookup object, and this can cause record locking and performance issues. The article suggests creating multiple copies of the same product record and assigning different child records to each copy, so that the number of child records per parent record is reduced.

 Changing the master-detail relationship to a lookup relationship is the best solution for allowing the creation of generic discount requests without the custom product object as its master record. A lookup relationship allows you to create child records without requiring a parent record. It also gives you more flexibility in defining the sharing and security settings for each object