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

Salesforce Certified Platform Data Architect (Plat-Arch-201) Exam - Topic 5 Question 69 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Data Architect (Plat-Arch-201) exam
Question #: 69
Topic #: 5
[All Salesforce Certified Platform Data Architect (Plat-Arch-201) Questions]

Universal Containers (UC) has a requirement to create an Account plan object that is related to the Account object. Each Account plan needs to have an Account object, but the accessibility requirement of the Account plan is different from the Account object. What should an Architect recommend?

Show Suggested Answer Hide Answer
Suggested Answer: D

Creating an account plan object with a lookup relationship to Account with validation rules to enforce the Account association can help UC meet their requirement. A lookup relationship allows different accessibility requirements for the account plan object and the account object, as well as different ownership and sharing settings. A validation rule can ensure that each account plan has an account associated with it.


Contribute your Thoughts:

0/2000 characters
Alyce
5 days ago
C is just asking for trouble, no validation? No way!
upvoted 0 times
...
Reyes
11 days ago
B seems like the best option, sharing rules will ensure proper access.
upvoted 0 times
...
Lenora
16 days ago
D is the way to go, validation rules are key here.
upvoted 0 times
...
Cristy
21 days ago
I lean towards option D because it combines the flexibility of a lookup with validation rules. That way, we ensure the Account plan is always linked to an Account.
upvoted 0 times
...
Rana
26 days ago
I practiced a similar question where lookup relationships were involved. I think option C might not enforce the association properly, which could lead to issues later.
upvoted 0 times
...
Janine
1 month ago
I’m not entirely sure, but I feel like option B could work since it allows for additional sharing rules. It seems like a good compromise.
upvoted 0 times
...
France
1 month ago
I remember we discussed the differences between master-detail and lookup relationships in class. I think option A might be too restrictive for accessibility.
upvoted 0 times
...
Glory
1 month ago
The master-detail relationship in option A is an interesting approach, but I'm not sure it's necessary here. The lookup with validation in option D seems like the most straightforward way to meet the requirements.
upvoted 0 times
...
Antonio
2 months ago
I'm leaning towards option C. It seems simpler to just create the lookup relationship without any validation. As long as the business requirements are clear, that could be a viable solution.
upvoted 0 times
...
Jeannetta
2 months ago
Option B with the additional sharing rules could work, but I'm worried that might get messy and hard to maintain over time. The lookup relationship with validation in option D feels cleaner.
upvoted 0 times
...
Leslee
2 months ago
I'm a bit confused on the difference between the accessibility requirements of the Account plan versus the Account object. Can someone clarify that for me?
upvoted 0 times
...
Arlie
2 months ago
I think option D is the way to go here. Creating a lookup relationship with validation rules to enforce the Account association seems like the most straightforward and secure approach.
upvoted 0 times
...

Save Cancel