Salesforce Exam Data Architect Topic 5 Question 41 Discussion

Actual exam question for Salesforce's Data Architect exam

Question #: 41
Topic #: 5

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?

ACreate multiple similar products and distribute the skew across those products.

BChange the lookup relationship to master-detail relationship.

CCreate a custom object to maintain the relationship between products and customers.

DSelect Clear the value of this field option while configuring the lookup relationship.

Show Suggested 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.

by Whitney at Jul 09, 2024, 09:13 PM

Limited Time Offer

25%

Off

Get Premium Data Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Ula

3 months ago

I'm going to have to go with option C. It's the only one that really addresses the root of the problem. Plus, it'll give me an excuse to create a fancy custom object. Win-win!

upvoted 0 times

...

My

3 months ago

Oh boy, this question is giving me flashbacks to that time I accidentally created a million-record lookup table. Nightmare fuel! Option B for sure, though I'd throw in a little prayer just to be safe.

upvoted 0 times

Marge

2 months ago

Yeah, definitely don't want to deal with that nightmare again. Option B it is!

upvoted 0 times

...

Markus

3 months ago

I agree, option B seems like the best choice to avoid lookup skew.

upvoted 0 times

...

Jesusa

3 months ago

D? Really? Clearing the value of the lookup field? That's just sweeping the problem under the rug. Let's be proactive and actually fix the underlying issue. I'm with Fannie on this one.

upvoted 0 times

Linette

2 months ago

C) Create a custom object to maintain the relationship between products and customers.

upvoted 0 times

...

Stephanie

3 months ago

B) Change the lookup relationship to master-detail relationship.

upvoted 0 times

...

Trinidad

3 months ago

A) Create multiple similar products and distribute the skew across those products.

upvoted 0 times

...

Kenda

4 months ago

I agree with Gabriele. Option B seems like the best choice to mitigate lookup skew issues.

upvoted 0 times

...

Adela

4 months ago

Hmm, I'm not sure about that. Creating multiple similar products seems like a lot of work and could get messy. I'd go with option C - a custom object to manage the relationship. That feels like a cleaner approach.

upvoted 0 times

Margot

3 months ago

Clearing the value of the field might not be the best solution. Option C seems like a more organized approach.

upvoted 0 times

...

Alexia

3 months ago

I think changing the relationship to master-detail could also help with the lookup skew issue.

upvoted 0 times

...

Ona

3 months ago

I agree, creating multiple products could be messy. Option C sounds like a cleaner approach.

upvoted 0 times

...

Gabriele

4 months ago

But wouldn't changing to master-detail relationship provide better data integrity and control?

upvoted 0 times

...

Wendell

4 months ago

I disagree, I believe option A is better. Creating multiple similar products can help distribute the skew.

upvoted 0 times

...

Fannie

4 months ago

I think option B is the way to go. Converting the lookup to a master-detail relationship will definitely help with the lookup skew issue. It's a simple and effective solution.

upvoted 0 times

Alpha

4 months ago

Yes, converting the lookup to a master-detail relationship will definitely help distribute the skew across the products.

upvoted 0 times

...

Marge

4 months ago

I agree, option B seems like the best solution to handle the lookup skew.

upvoted 0 times

...

Gabriele

4 months ago

I think we should go with option B and change the lookup relationship to master-detail.

upvoted 0 times

...