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 6 Question 66 Discussion

What are the three considerations that the architect should recommend for Change Setdeployment?Choose 3 answers
A) Change Sets cannot be automated.. and D) Change Sets cannot be rolled back. and E) Change Sets cannot be reused between Production Salesforce orgs.
B) Change Sets cannot be validated before deployment
C) Change Sets cannot be used for orgs affiliated with same production org.

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

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

What are the three considerations that the architect should recommend for Change Set

deployment?

Choose 3 answers

Show Suggested Answer Hide Answer
Suggested Answer: A, D, E

by Gertude at Nov 23, 2025, 12:20 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
Tracey
5 months ago
Overall, A, B, and D seem like the best choices.
upvoted 0 times
...
Gabriele
5 months ago
E is also valid. Reusability is a big plus.
upvoted 0 times
...
Candida
5 months ago
I feel C is misleading. Change Sets can be used in some cases.
upvoted 0 times
...
Dana
5 months ago
D should definitely be included. No rollback is risky.
upvoted 0 times
...
Selma
5 months ago
I think A is important. Automation is key.
upvoted 0 times
...
Judy
5 months ago
E seems off, I've reused Change Sets before.
upvoted 0 times
...
Kenneth
6 months ago
D is a big issue, rolling back is crucial!
upvoted 0 times
...
Paulina
6 months ago
Totally agree with B! Validation is a pain.
upvoted 0 times
...
Cecily
6 months ago
A) Change Sets cannot be automated.
upvoted 0 times
...
Leoma
7 months ago
Hmm, I'm not sure about this one. I better go review the Salesforce documentation again just to be safe.
upvoted 0 times
...
Agustin
7 months ago
I'm with Teri on this one. Change Sets are so 2010. Real pros use modern tools, not this outdated stuff.
upvoted 0 times
...
Teri
7 months ago
Haha, who even uses Change Sets these days? Just use Metadata API and Git like a real architect!
upvoted 0 times
...
Mable
7 months ago
I agree with Hoa. The correct answers are C, D, and E. Change Sets can't be used for affiliated orgs, can't be rolled back, and can't be reused between Production orgs.
upvoted 0 times
...
Dean
7 months ago
I’m a bit confused about the options, but I recall that Change Sets can’t be automated, which seems important to mention.
upvoted 0 times
...
Shala
7 months ago
I practiced a question similar to this, and I think Change Sets can't be reused between Production orgs.
upvoted 0 times
...
Deeann
8 months ago
I'm not entirely sure, but I feel like there was something about Change Sets not being able to be validated before deployment.
upvoted 0 times
...
Paris
8 months ago
I think I remember that Change Sets can't be rolled back, so that might be one of the answers.
upvoted 0 times
...
Kayleigh
8 months ago
Change Set deployment can be a real headache, but I've dealt with it before. I'll go with the options that give the architect the most control and visibility.
upvoted 0 times
...
Julieta
8 months ago
Ugh, Change Sets are the worst. I hate how inflexible they can be. I'll just try to eliminate the options that seem the most problematic.
upvoted 0 times
...
Gaston
8 months ago
Okay, let's see. I know Change Sets have some limitations, so I'll try to identify the key ones that the architect should consider for a safe deployment.
upvoted 0 times
...
Hoa
9 months ago
A, B, and D are definitely not the right answers. Change Sets can be automated, validated, and rolled back.
upvoted 0 times
...
Lenora
9 months ago
Wait, C? I thought they could be used across affiliated orgs!
upvoted 0 times
...
Hector
9 months ago
B is a big issue too. Validation is crucial.
upvoted 0 times
...
Erick
9 months ago
Hmm, this is a tricky one. I'm not sure about the differences between the options, but I know Change Sets can be a bit finicky, so I'll need to think this through carefully.
upvoted 0 times
...
Krystal
10 months ago
I'm pretty confident I can handle this. Change Set deployment is all about managing risk, so I'll focus on the options that address that.
upvoted 0 times
Brinda
4 months ago
E is a good point, reusability can save time.
upvoted 0 times
...
Sharika
4 months ago
C seems relevant, especially for orgs linked to production.
upvoted 0 times
...
Mable
4 months ago
I agree, but B is also important. Validation matters!
upvoted 0 times
...
Ronald
8 months ago
Definitely! And D too, rolling back is crucial.
upvoted 0 times
...
Ronna
9 months ago
I think A is a big one. Automation is key.
upvoted 0 times
...
...

Save Cancel