Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Data-Architect Topic 4 Question 39 Discussion

Actual exam question for Salesforce's Salesforce Certified Data Architect exam
Question #: 39
Topic #: 4
[All Salesforce Certified Data Architect Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: A

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.


Contribute your Thoughts:

Brett
2 months ago
Hmm, maybe Option B. It's kind of like a reverse lookup, which could help distribute the data load. *chuckles* Or we could just tell the customers to stop buying the product altogether, that'll fix the skew!
upvoted 0 times
Kristel
14 days ago
Yeah, creating a master-detail relationship could really help distribute the data more evenly.
upvoted 0 times
...
Michell
17 days ago
Haha, telling customers to stop buying the product might not be the best solution!
upvoted 0 times
...
Galen
18 days ago
Option B sounds like a good idea. It could definitely help with the data load.
upvoted 0 times
...
Sherman
20 days ago
Yeah, creating a master-detail relationship could definitely help with the lookup skew issue.
upvoted 0 times
...
Cecily
1 months ago
Haha, telling customers to stop buying the product might not be the best solution!
upvoted 0 times
...
Angelica
1 months ago
Option B sounds like a good idea. It could help balance the data load.
upvoted 0 times
...
...
Luke
2 months ago
Option D? Really? Clearing the lookup field value? That just sounds like a band-aid solution to me.
upvoted 0 times
In
1 months ago
B) Change the lookup relationship to master-detail relationship.
upvoted 0 times
...
Carla
1 months ago
A) Create multiple similar products and distribute the skew across those products.
upvoted 0 times
...
...
Brigette
2 months ago
Option A is a bit of a weird one. Splitting up the products seems like it could just create more problems than it solves.
upvoted 0 times
Howard
18 days ago
Option A is a bit of a weird one. Splitting up the products seems like it could just create more problems than it solves.
upvoted 0 times
...
Dean
20 days ago
C) Create a custom object to maintain the relationship between products and customers.
upvoted 0 times
...
Lizette
21 days ago
B) Change the lookup relationship to master-detail relationship.
upvoted 0 times
...
Monroe
26 days ago
A) Create multiple similar products and distribute the skew across those products.
upvoted 0 times
...
...
Minna
2 months ago
That's true, but changing to master-detail relationship seems like a more efficient solution.
upvoted 0 times
...
Jacquelyne
2 months ago
I'm leaning towards Option C. A custom object to manage the product-customer relationship could provide more flexibility and control.
upvoted 0 times
Cory
1 months ago
I think creating multiple similar products could also work to distribute the skew. But Option C does seem more organized.
upvoted 0 times
...
Robt
2 months ago
Option C sounds like a good idea. It would definitely help manage the relationship better.
upvoted 0 times
...
...
Olene
3 months ago
Option B seems like the way to go. Master-detail relationships are designed to handle large volumes of records, so that should help with the lookup skew.
upvoted 0 times
Lyndia
2 months ago
That's a good point. Master-detail relationships are better suited for handling large volumes of records.
upvoted 0 times
...
Julieta
2 months ago
B) Change the lookup relationship to master-detail relationship.
upvoted 0 times
...
...
Sharika
3 months ago
But wouldn't creating multiple similar products also help distribute the skew?
upvoted 0 times
...
Janey
3 months ago
I agree with Minna, that would help mitigate the lookup skew issue.
upvoted 0 times
...
Minna
3 months ago
I think we should go with option B, changing the lookup relationship to master-detail.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77