Northern Trail Outfitters (NTO) wants to capture a list of customers that have bought a particular product. The solution architect has recommended to create a custom object for product, and to create a lookup relationship between its customers and its products.
Products will be modeled as a custom object (NTO_ Product__ c) and customers are modeled
as person accounts. Every NTO product may have millions of customers looking up a single product, resulting in a lookup skew.
What should a data architect suggest to mitigate Issues related to lookup skew?
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.
Ula
14 days agoMy
15 days agoJesusa
17 days agoStephanie
20 hours agoTrinidad
9 days agoKenda
30 days agoAdela
1 months agoMargot
21 hours agoAlexia
7 days agoOna
12 days agoGabriele
1 months agoWendell
1 months agoFannie
1 months agoAlpha
28 days agoMarge
30 days agoGabriele
1 months ago