Salesforce Exam Data-Architect Topic 4 Question 34 Discussion

Actual exam question for Salesforce's Salesforce Certified Data Architect exam

Question #: 34
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?

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 Agustin at Apr 23, 2024, 11:52 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Dusti

3 months ago

I bet the data architect who suggested Option D is the same person who thought 'Clear the value' was a good idea for solving the Y2K problem.

upvoted 0 times

...

Derrick

3 months ago

Option A? What, are they going to create a million similar products? That's just crazy talk.

upvoted 0 times

James

2 months ago

User2: Agreed, that would be way too much to manage. Maybe changing the lookup relationship to master-detail would be a better solution.

upvoted 0 times

...

Ashley

2 months ago

User1: Yeah, creating a million similar products doesn't sound like a good idea.

upvoted 0 times

...

Bea

3 months ago

Good point, C could handle millions of customers more efficiently.

upvoted 0 times

...

Deandrea

3 months ago

This is a classic case of lookup skew. Creating a custom object to manage the relationship is a smart solution.

upvoted 0 times

Ernest

2 months ago

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

upvoted 0 times

...

Melvin

2 months ago

That's a good suggestion. It can help with the lookup skew issue.

upvoted 0 times

...

Carylon

2 months ago

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

upvoted 0 times

...

Lea

3 months ago

I actually think C is better, creating a custom object to manage relationships makes it more scalable.

upvoted 0 times

...

Jolanda

3 months ago

Option D is just weird. Why would you clear the value of the lookup field? That doesn't solve the skew issue at all.

upvoted 0 times

France

3 months ago

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

upvoted 0 times

...

Arlene

3 months ago

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

upvoted 0 times

...

Mozell

3 months ago

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

upvoted 0 times

...

Jeannetta

3 months ago

I agree with Jennifer. A master-detail relationship is a better approach than creating multiple similar products.

upvoted 0 times

Zona

3 months ago

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

upvoted 0 times

...

Juliann

3 months ago

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

upvoted 0 times

...

Ernie

3 months ago

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

upvoted 0 times

...

Delpha

3 months ago

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

upvoted 0 times

...

Tammara

3 months ago

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

upvoted 0 times

...

Louvenia

3 months ago

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

upvoted 0 times

...

Jennifer

4 months ago

Option B makes the most sense. A master-detail relationship will help manage the skew better than a lookup.

upvoted 0 times

Bulah

3 months ago

I agree, a master-detail relationship would definitely help in this scenario.

upvoted 0 times

...

Regenia

3 months ago

Option B makes the most sense. A master-detail relationship will help manage the skew better than a lookup.

upvoted 0 times

...

Nicolette

4 months ago

I thought about A too, distributing the skew could work, but seems like a workaround.

upvoted 0 times

...

Bea

4 months ago

What do you think is the best solution? I'm leaning towards option A.

upvoted 0 times

...

Lea

4 months ago

Yeah, it's tricky with the lookup skew problem.

upvoted 0 times

...

Nicolette

4 months ago

Hey, did you see the question about NTO and their product-customer relationship issue?

upvoted 0 times

...

Theola

5 months ago

Or changing the lookup relationship to a master-detail relationship might also work.

upvoted 0 times

...

Gaynell

5 months ago

I think creating multiple similar products and distributing the skew across them could help.

upvoted 0 times

...

Eleonore

5 months ago

Yes, that's a concern. What do you think the data architect should suggest to mitigate lookup skew issues?

upvoted 0 times

...

Theola

5 months ago

But won't having millions of customers looking up a single product result in lookup skew issues?

upvoted 0 times

...

Gaynell

5 months ago

I agree with the solution architect. It makes sense to model products as a custom object and customers as person accounts.

upvoted 0 times

...

Eleonore

5 months ago

I think the solution architect's recommendation is to create a custom object for the product and create a lookup relationship. What do you think?

upvoted 0 times

...