New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Certified Platform Data Architect (Plat-Arch-201) Exam - Topic 4 Question 34 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Data Architect (Plat-Arch-201) exam
Question #: 34
Topic #: 4
[All Salesforce Certified Platform Data Architect (Plat-Arch-201) 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.


by Agustin at Apr 23, 2024, 11:52 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Platform Data Architect (Plat-Arch-201) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Dana
3 months ago
Definitely need to avoid that lookup skew issue!
upvoted 0 times
...
Matt
3 months ago
Wait, can you really just clear the lookup field? That seems risky.
upvoted 0 times
...
Shalon
3 months ago
C sounds like a smart way to handle relationships!
upvoted 0 times
...
Carin
4 months ago
I disagree, a master-detail might be better for data integrity.
upvoted 0 times
...
Dong
4 months ago
A is a solid option to spread out the load.
upvoted 0 times
...
Hassie
4 months ago
I vaguely recall something about clearing field values in lookups, but I'm not confident that would actually solve the skew issue.
upvoted 0 times
...
Earnestine
4 months ago
I practiced a question similar to this, and I think creating a custom object to manage the relationship sounds like a solid approach to avoid skew.
upvoted 0 times
...
Margarett
4 months ago
I'm not entirely sure, but I feel like changing the lookup to a master-detail relationship might not be the best option since it could limit flexibility.
upvoted 0 times
...
Lorrie
5 months ago
I remember we discussed lookup skew in class, and I think creating multiple similar products could help distribute the load.
upvoted 0 times
...
Jerilyn
5 months ago
This is a tough one, but I think option C might be the best approach. Creating a custom object to manage the relationship between products and customers could be a good way to mitigate the lookup skew issue.
upvoted 0 times
...
Portia
5 months ago
Okay, I think I've got a handle on this. The key is to find a way to distribute the load across multiple products, so option A seems like the most straightforward solution. Creating multiple similar products could help spread out the lookup skew.
upvoted 0 times
...
Jodi
5 months ago
This looks like a tricky question. I'm not sure if I fully understand the concept of lookup skew, but I think option B might be the way to go. Changing the relationship to master-detail could help mitigate the issue.
upvoted 0 times
...
Sherita
5 months ago
Hmm, I'm a bit confused by this question. The lookup skew seems like a complex problem, and I'm not sure if any of these options are the best solution. I might need to do some more research on lookup skew before attempting to answer this.
upvoted 0 times
...
German
5 months ago
Ah, I think I've got this one! The description of discretionary, broadly defined criteria points to a recognition program, which is option A. Feeling pretty confident about this.
upvoted 0 times
...
Truman
5 months ago
I'm a bit unsure about this one. I know password policies can be complex, so I'll need to reason through the implications of the question carefully.
upvoted 0 times
...
Mira
5 months ago
I'm feeling pretty confident about this one. The descriptions seem clear, and I think I can logically work through the connections to the answer choices.
upvoted 0 times
...
Dusti
2 years 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
2 years ago
Option A? What, are they going to create a million similar products? That's just crazy talk.
upvoted 0 times
James
2 years ago
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 years ago
Yeah, creating a million similar products doesn't sound like a good idea.
upvoted 0 times
...
...
Bea
2 years ago
Good point, C could handle millions of customers more efficiently.
upvoted 0 times
...
Deandrea
2 years 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 years ago
C) Create a custom object to maintain the relationship between products and customers.
upvoted 0 times
...
Melvin
2 years ago
That's a good suggestion. It can help with the lookup skew issue.
upvoted 0 times
...
Carylon
2 years ago
B) Change the lookup relationship to master-detail relationship.
upvoted 0 times
...
...
Lea
2 years ago
I actually think C is better, creating a custom object to manage relationships makes it more scalable.
upvoted 0 times
...
Jolanda
2 years 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
2 years ago
C) Create a custom object to maintain the relationship between products and customers.
upvoted 0 times
...
Arlene
2 years ago
B) Change the lookup relationship to master-detail relationship.
upvoted 0 times
...
Mozell
2 years ago
A) Create multiple similar products and distribute the skew across those products.
upvoted 0 times
...
...
Jeannetta
2 years ago
I agree with Jennifer. A master-detail relationship is a better approach than creating multiple similar products.
upvoted 0 times
Zona
2 years ago
B) Change the lookup relationship to master-detail relationship.
upvoted 0 times
...
Juliann
2 years ago
A) Create multiple similar products and distribute the skew across those products.
upvoted 0 times
...
Ernie
2 years ago
B) Change the lookup relationship to master-detail relationship.
upvoted 0 times
...
Delpha
2 years ago
B) Change the lookup relationship to master-detail relationship.
upvoted 0 times
...
Tammara
2 years ago
A) Create multiple similar products and distribute the skew across those products.
upvoted 0 times
...
Louvenia
2 years ago
A) Create multiple similar products and distribute the skew across those products.
upvoted 0 times
...
...
Jennifer
2 years ago
Option B makes the most sense. A master-detail relationship will help manage the skew better than a lookup.
upvoted 0 times
Bulah
2 years ago
I agree, a master-detail relationship would definitely help in this scenario.
upvoted 0 times
...
Regenia
2 years ago
Option B makes the most sense. A master-detail relationship will help manage the skew better than a lookup.
upvoted 0 times
...
...
Nicolette
2 years ago
I thought about A too, distributing the skew could work, but seems like a workaround.
upvoted 0 times
...
Bea
2 years ago
What do you think is the best solution? I'm leaning towards option A.
upvoted 0 times
...
Lea
2 years ago
Yeah, it's tricky with the lookup skew problem.
upvoted 0 times
...
Nicolette
2 years ago
Hey, did you see the question about NTO and their product-customer relationship issue?
upvoted 0 times
...
Theola
2 years ago
Or changing the lookup relationship to a master-detail relationship might also work.
upvoted 0 times
...
Gaynell
2 years ago
I think creating multiple similar products and distributing the skew across them could help.
upvoted 0 times
...
Eleonore
2 years ago
Yes, that's a concern. What do you think the data architect should suggest to mitigate lookup skew issues?
upvoted 0 times
...
Theola
2 years ago
But won't having millions of customers looking up a single product result in lookup skew issues?
upvoted 0 times
...
Gaynell
2 years 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
2 years 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
...

Save Cancel