Deal of The Day! 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 Development Lifecycle and Deployment Architect (Plat-Arch-202) Exam - Topic 8 Question 67 Discussion

Universal Containers uses multiple Salesforce orgs for its different lines of business (LOBs). In a recent analysis, the architect found that UC could have a more complete view of its customers by gathering customer data from different orgs.What two options can an architect recommend to accomplish the customer 360-degree view?Choose 2 answers
C) Implement a Single Package multi-org strategy by developing and deploying to all orgs a managed package which reads and consolidates customer 360-degree view from the different orgs. and D) Implement a Hub-and-Spoke multi-org strategy by consolidating customer data In a single org, which will be the master of customer data, and using integration strategies to let the LOBs orgs read and write from it.
A) Implement a Complete Graph multi-org strategy by allowing each org to connect directly to every other, reading and writing customer data from the orgs where it has been originally created.
B) Migrate from multi-org to single-org strategy, consolidating customer data in the process.

Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Exam - Topic 8 Question 67 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) exam
Question #: 67
Topic #: 8
[All Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Questions]

Universal Containers uses multiple Salesforce orgs for its different lines of business (LOBs). In a recent analysis, the architect found that UC could have a more complete view of its customers by gathering customer data from different orgs.

What two options can an architect recommend to accomplish the customer 360-degree view?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: C, D

by Helga at Nov 24, 2025, 04:33 AM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Kristel
5 months ago
Consolidation is crucial. D offers a clear path forward.
upvoted 0 times
...
Anastacia
5 months ago
C could work too, but it might be complex to manage.
upvoted 0 times
...
Micaela
5 months ago
I prefer B. A single org simplifies everything.
upvoted 0 times
...
Marsha
5 months ago
Option A seems risky. Too many connections could complicate things.
upvoted 0 times
...
Devora
5 months ago
I agree, D makes sense for a master data approach.
upvoted 0 times
...
Lauran
5 months ago
I think C could work too, but it might be complicated.
upvoted 0 times
...
Cherri
6 months ago
A multi-org strategy can get messy, though.
upvoted 0 times
...
Ricki
6 months ago
Wait, isn't migrating to a single org risky?
upvoted 0 times
...
Jesusa
6 months ago
C and D are both solid options, but I think D has the edge. Centralizing customer data and using integration to sync it with the LOB orgs is a smart way to go.
upvoted 0 times
...
Shizue
7 months ago
Haha, migrating to a single org? Good luck with that! I'd go with D - the hub-and-spoke strategy seems like the most straightforward way to get that 360-degree view.
upvoted 0 times
...
Ludivina
7 months ago
A is an interesting idea, but I'm not sure it's the most practical solution. Allowing direct connections between orgs could get messy and hard to manage.
upvoted 0 times
...
Crissy
7 months ago
D looks like the best choice to me. Consolidating customer data in a single master org and using integration to sync with the LOB orgs seems like the most efficient and secure approach.
upvoted 0 times
...
Mitsue
7 months ago
C and D seem like the most viable options. I'm leaning towards C since it allows for a more centralized and controlled approach to customer data consolidation.
upvoted 0 times
...
Johnna
7 months ago
I feel like option C could work too, especially if we’re using managed packages to pull data together. That was a topic in our last review session.
upvoted 0 times
...
Quentin
7 months ago
I’m a bit confused about the Complete Graph strategy in option A. It seems complex, but I can't recall the details.
upvoted 0 times
...
Jeanice
8 months ago
I think option D sounds familiar; it’s like the Hub-and-Spoke model we practiced. It seems to make sense for consolidating data.
upvoted 0 times
...
Izetta
8 months ago
I remember studying multi-org strategies, but I'm not entirely sure which one would be best for a complete customer view.
upvoted 0 times
...
Edmond
8 months ago
The Hub-and-Spoke strategy seems like the most straightforward option to me. It allows you to maintain a single source of truth for customer data while still giving the LOBs the ability to access and update it. I think that's the way to go.
upvoted 0 times
...
Bernadine
8 months ago
I'm a bit confused by all the different multi-org strategies. I think I need to do some more research on the pros and cons of each one before I can make a decision. Maybe I'll start by looking up some examples or case studies to get a better understanding.
upvoted 0 times
...
Karan
8 months ago
Okay, I think I've got it. The Complete Graph strategy sounds like it could work, but it might be a bit messy to have each org directly connected to every other one. The Single Package strategy could work, but it might be a bit more complex to develop and deploy. I'm going to go with the Hub-and-Spoke option.
upvoted 0 times
...
Solange
8 months ago
I think option D is the best. Centralized data is key.
upvoted 0 times
...
Deangelo
9 months ago
I agree, D is solid!
upvoted 0 times
...
Gregoria
9 months ago
Option D seems like the best choice for a master data approach.
upvoted 0 times
...
Amie
9 months ago
Hmm, I'm leaning towards the Hub-and-Spoke strategy. It seems like the most straightforward way to maintain a 360-degree view while still allowing the LOBs to access and update the data. I'll need to read through the options carefully, though.
upvoted 0 times
...
Kallie
10 months ago
This is a tricky one. I'm not sure if I fully understand the different multi-org strategies, but I think the key is to find a way to consolidate the customer data without having to migrate everything to a single org.
upvoted 0 times
Cassie
4 months ago
I like the idea of a managed package from option C. It seems flexible.
upvoted 0 times
...
Audra
4 months ago
But what about option A? Direct connections could be efficient too.
upvoted 0 times
...
Merri
4 months ago
I agree! It keeps the LOBs intact while centralizing data.
upvoted 0 times
...
Yvonne
9 months ago
I think option D sounds solid. Hub-and-Spoke could work well.
upvoted 0 times
...
Gabriele
9 months ago
True, but it might get messy with too many connections.
upvoted 0 times
...
...

Save Cancel