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 Development Lifecycle and Deployment Architect (Plat-Arch-202) Exam - Topic 4 Question 55 Discussion

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

Universal Containers CUC) is an enterprise financial company that operates in EMEA, AMER, and APAC. Because of regulatory requirements, UC has a separate Salesforce org for each region. Each org has its own customizations that fit for the region needs, but there are also standard processes that apply to all regions requirements.

As the deployment architect, what should be considered for the multi-org deployment strategy?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

0/2000 characters
Shizue
3 months ago
Wait, are we really considering unmanaged packages? That seems sketchy!
upvoted 0 times
...
Wei
3 months ago
I think the package development model is the best option here.
upvoted 0 times
...
Isreal
3 months ago
Unmanaged packages? Really? That sounds risky.
upvoted 0 times
...
Stephaine
4 months ago
I disagree, change sets can work too if done right.
upvoted 0 times
...
Margot
4 months ago
Managed packages are the way to go for multi-org setups!
upvoted 0 times
...
Adela
4 months ago
Change sets seem straightforward, but I recall there being limitations with them, especially when it comes to deploying across multiple orgs.
upvoted 0 times
...
Chana
4 months ago
I feel like the package development model could be a solid choice since it allows for better organization of components, but I’m not clear on how it handles regional differences.
upvoted 0 times
...
Miesha
4 months ago
I think unmanaged packages might be easier for quick deployments, but they don’t allow for version control, which could be a problem.
upvoted 0 times
...
Beckie
5 months ago
I remember we discussed managed packages as a way to maintain consistency across multiple orgs, but I'm not entirely sure if they are the best option for all regions.
upvoted 0 times
...
Yvonne
5 months ago
Change sets seem like the simplest approach, but I'll need to make sure that fits the multi-org scenario.
upvoted 0 times
...
Tamra
5 months ago
Package development model? I'm not super familiar with that, but it could be an interesting option to explore.
upvoted 0 times
...
Joseph
5 months ago
Okay, I've got a strategy. I'll focus on the requirements around customizations and standard processes across regions.
upvoted 0 times
...
Howard
5 months ago
Hmm, I'm a bit unsure about the differences between managed and unmanaged packages. I'll need to review that before deciding.
upvoted 0 times
...
Laurene
5 months ago
This looks like a tricky one. I'll need to think through the pros and cons of each approach carefully.
upvoted 0 times
...
Charisse
10 months ago
Hey, I heard they're also considering smoke signals and carrier pigeons for the deployment strategy. Old-school, but hey, it might work!
upvoted 0 times
Gayla
9 months ago
D) Deploy metadata to production orgs using change sets.
upvoted 0 times
...
Lemuel
10 months ago
B) Deploy metadata to production orgs using unmanaged packages.
upvoted 0 times
...
Hester
10 months ago
A) Deploy metadata to production orgs using managed packages.
upvoted 0 times
...
...
Herman
10 months ago
Unmanaged packages? Are you kidding me? That's just asking for trouble with all these regional customizations. Nope, not going there.
upvoted 0 times
...
France
10 months ago
Change sets? Really? That sounds like a nightmare to manage across multiple orgs. I'll pass on that one.
upvoted 0 times
...
Arlette
10 months ago
I'm leaning towards the package development model. It gives me more flexibility to customize for each region's needs while still having a consistent framework.
upvoted 0 times
Marica
9 months ago
D) Deploy metadata to production orgs using change sets.
upvoted 0 times
...
Jina
9 months ago
C) Deploy metadata to production orgs using package development model.
upvoted 0 times
...
Natalie
9 months ago
B) Deploy metadata to production orgs using unmanaged packages.
upvoted 0 times
...
Detra
10 months ago
A) Deploy metadata to production orgs using managed packages.
upvoted 0 times
...
...
Fatima
11 months ago
Managed packages seem like the way to go for maintaining standard processes across regions. Less complexity than unmanaged packages or change sets.
upvoted 0 times
Helga
10 months ago
C) Deploy metadata to production orgs using package development model.
upvoted 0 times
...
Cassi
10 months ago
A) Deploy metadata to production orgs using managed packages.
upvoted 0 times
...
...
Janine
11 months ago
But what about using change sets for simpler deployments?
upvoted 0 times
...
Cristal
11 months ago
I agree with My, managed packages provide better control and versioning.
upvoted 0 times
...
My
11 months ago
I think we should consider using managed packages for deployment.
upvoted 0 times
...

Save Cancel