Salesforce Exam Data Architect Topic 4 Question 39 Discussion

Actual exam question for Salesforce's Data Architect exam

Question #: 39
Topic #: 4

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 Tammy at Jun 20, 2024, 08:30 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Brett

5 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

4 months ago

Yeah, creating a master-detail relationship could really help distribute the data more evenly.

upvoted 0 times

...

Michell

4 months ago

Haha, telling customers to stop buying the product might not be the best solution!

upvoted 0 times

...

Galen

4 months ago

Option B sounds like a good idea. It could definitely help with the data load.

upvoted 0 times

...

Sherman

4 months ago

Yeah, creating a master-detail relationship could definitely help with the lookup skew issue.

upvoted 0 times

...

Cecily

4 months ago

Haha, telling customers to stop buying the product might not be the best solution!

upvoted 0 times

...

Angelica

4 months ago

Option B sounds like a good idea. It could help balance the data load.

upvoted 0 times

...

Luke

5 months ago

Option D? Really? Clearing the lookup field value? That just sounds like a band-aid solution to me.

upvoted 0 times

In

4 months ago

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

upvoted 0 times

...

Carla

4 months ago

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

upvoted 0 times

...

Brigette

5 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

4 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

...

Dean

4 months ago

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

upvoted 0 times

...

Lizette

4 months ago

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

upvoted 0 times

...

Monroe

4 months ago

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

upvoted 0 times

...

Minna

5 months ago

That's true, but changing to master-detail relationship seems like a more efficient solution.

upvoted 0 times

...

Jacquelyne

5 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

4 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

5 months ago

Option C sounds like a good idea. It would definitely help manage the relationship better.

upvoted 0 times

...

Olene

6 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