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 2 Question 68 Discussion

Universal Containers (UC) has a large user base (>300 users) and was originally implemented eight years ago by a Salesforce Systems Integration Partner. Since then, UC has made a number of changes to their Visual force pages and Apex classes in response to customer requirements, made by a variety of Vendors and internal teams. Which three issues would a new Technical Architect expect to see when evaluating the code in the Salesforce org? Choose 3 answers
A) Multiple triggers on the same object, making it hard to understand the order of operations. and D) Duplicated logic across Visual force pages and Apex classes performing similar tasks. and E) Custom built JSON and String manipulation Classes that are no longer required.
B) Multiple unit test failures would be encountered.
C) Broken functionality due to Salesforce upgrades.

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

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

Universal Containers (UC) has a large user base (>300 users) and was originally implemented eight years ago by a Salesforce Systems Integration Partner. Since then, UC has made a number of changes to their Visual force pages and Apex classes in response to customer requirements, made by a variety of Vendors and internal teams. Which three issues would a new Technical Architect expect to see when evaluating the code in the Salesforce org? Choose 3 answers

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

by Emelda at Nov 24, 2025, 11:08 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
Lucy
2 months ago
Custom JSON classes might be outdated. Cleanup needed!
upvoted 0 times
...
Ceola
2 months ago
Broken functionality from upgrades is likely too.
upvoted 0 times
...
Annabelle
2 months ago
I’d also expect unit test failures. Too many changes over time.
upvoted 0 times
...
Leatha
2 months ago
Definitely! It complicates the order of operations.
upvoted 0 times
...
Ona
3 months ago
I think multiple triggers on the same object is a big issue.
upvoted 0 times
...
Malika
3 months ago
E) Custom JSON classes? Why are they still around?
upvoted 0 times
...
Bea
3 months ago
C) Surprised to see broken functionality from upgrades, but it makes sense.
upvoted 0 times
...
Glendora
4 months ago
B) Unit test failures? That’s a nightmare waiting to happen.
upvoted 0 times
...
Truman
4 months ago
Totally agree, D) Duplicated logic is a big red flag too.
upvoted 0 times
...
Suzi
4 months ago
A) Multiple triggers on the same object is a classic issue.
upvoted 0 times
...
Lindsey
4 months ago
Haha, I bet they've got some real "gems" in that Salesforce org. D, A, and C for the win!
upvoted 0 times
...
Cyndy
4 months ago
D, C, and A for sure. Sounds like a classic case of technical debt. Yikes!
upvoted 0 times
...
Isidra
4 months ago
I think multiple unit test failures could be common in a legacy system like this, but I’m not completely confident about that one.
upvoted 0 times
...
Lonny
5 months ago
I feel like duplicated logic across Visualforce pages and Apex classes is something we’ve seen before in case studies. It just makes the codebase messy.
upvoted 0 times
...
Miss
5 months ago
I’m not entirely sure, but I think broken functionality due to Salesforce upgrades could be a problem too. We saw that in a practice scenario, right?
upvoted 0 times
...
Maricela
5 months ago
I remember we discussed how multiple triggers can really complicate things, especially with order of execution. That seems like a likely issue here.
upvoted 0 times
...
Blair
5 months ago
Ah, I've seen this kind of thing before. Duplicated logic and custom JSON/String classes are definitely red flags. I'll make sure to highlight those as potential issues the new Architect should look out for.
upvoted 0 times
...
Phillip
5 months ago
Okay, let's see. Multiple triggers, unit test failures, and broken functionality from upgrades - those all sound like common problems in a mature Salesforce org. I'll make sure to hit those key points in my answer.
upvoted 0 times
...
Oren
5 months ago
Definitely D, B, and C. Lack of code reuse and testing, plus Salesforce changes, can really mess things up.
upvoted 0 times
...
Clemencia
6 months ago
I'd say D, C, and A are the most likely issues. Spaghetti code is a common problem in legacy Salesforce orgs.
upvoted 0 times
...
Alida
6 months ago
Duplicated logic is a concern. It wastes resources.
upvoted 0 times
...
Jose
6 months ago
I'm going with D, A, and E. Bet they've got some crazy custom classes that no one understands anymore.
upvoted 0 times
...
Vashti
6 months ago
Hmm, I'm a bit unsure about this one. There are a lot of potential issues to consider, and I'm not sure which ones are the most likely. I'll need to think it through carefully.
upvoted 0 times
...
Elbert
7 months ago
This question seems pretty straightforward. I'd focus on identifying common issues with legacy Salesforce orgs, like duplicated logic and outdated custom code.
upvoted 0 times
Melodie
1 month ago
And broken functionality after upgrades is a big red flag too.
upvoted 0 times
...
Magda
1 month ago
Yes! That can really complicate things.
upvoted 0 times
...
Shayne
2 months ago
Don't forget about multiple triggers on the same object.
upvoted 0 times
...
Ayesha
2 months ago
Totally agree, it's a common issue.
upvoted 0 times
...
Ariel
6 months ago
Legacy code often has duplicated logic.
upvoted 0 times
...
...

Save Cancel