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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

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

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

A team of developers at Universal Containers has developed Apex Triggers and Apex

Classes in a sandbox. The team has also written test classes to unit test these triggers and classes. When executed in the sandbox, all the test methods pass and all the classes meet the minimum code coverage requirement. But when they tried deploying these components to production, a

few of these test methods failed

What should an architect recommend?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Ruth at Sep 18, 2024, 11:24 PM

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
Andra
3 months ago
Just because it works in sandbox doesn't mean it’ll work in prod.
upvoted 0 times
...
Yuki
3 months ago
Definitely agree with option D. Always generate your own data!
upvoted 0 times
...
Skye
3 months ago
Wait, why would you set SeeAllData to True? That seems risky!
upvoted 0 times
...
Floyd
4 months ago
I think using SeeAllData is a bad practice. Better to generate data.
upvoted 0 times
...
Jamal
4 months ago
Sounds like a classic case of missing test data in production.
upvoted 0 times
...
Earleen
4 months ago
I feel like we might need to create test data in production, but that seems risky. I think I lean towards D as well, but I’m not completely confident.
upvoted 0 times
...
Shawna
4 months ago
This situation reminds me of a practice question where we had to ensure test isolation. I think generating data in the test methods is crucial, so D might be right.
upvoted 0 times
...
Stanton
4 months ago
I'm a bit unsure about the implications of SeeAllData. I think setting it to True could lead to issues, but I can't recall the specifics.
upvoted 0 times
...
Eileen
5 months ago
I remember we discussed the importance of not relying on production data for tests. Option D seems like the best practice.
upvoted 0 times
...
Chauncey
5 months ago
I've seen this kind of issue before. The best approach is probably to generate the test data in the test methods themselves, rather than relying on SeeAllData. That way, you can ensure the tests are self-contained and not dependent on the specific data in the production org.
upvoted 0 times
...
Dean
5 months ago
Okay, let's see. It sounds like the team has already done a good job with their unit testing, but there's something about the production environment that's causing issues. I'd recommend looking into the data setup and making sure the test methods are generating the necessary data, rather than relying on SeeAllData.
upvoted 0 times
...
Tegan
5 months ago
I'm a bit confused by this question. If the tests passed in the sandbox, why are they failing in production? I'll need to think carefully about the differences between the two environments and how that might be impacting the test results.
upvoted 0 times
...
Cherelle
5 months ago
Hmm, this is a tricky one. I think the key here is to understand why the test methods are failing in production, even though they passed in the sandbox. Maybe there's some difference in the data or environment that's causing the issue.
upvoted 0 times
...
Carmela
5 months ago
Okay, let me think this through step-by-step. The Level 2 class model is not vendor-specific, so that rules out option B. It's also not the same as the System of Record Fabric, so option A is out. That leaves options C and D, and I think option C about it being an expansion of the Level 1 class model sounds right.
upvoted 0 times
...
Dorothy
1 year ago
I think setting SeeAllData to True and generating data in test methods could also be a good option.
upvoted 0 times
...
Yvette
1 year ago
I agree with Caitlin. It's important to have accurate data in production for testing.
upvoted 0 times
...
Caitlin
1 year ago
I think we should create test data in production before deploying.
upvoted 0 times
...
Keneth
1 year ago
I'm feeling lucky, so I'm gonna go with A. Create the test data in production before deploying the test classes. What could go wrong, right? *laughs nervously*
upvoted 0 times
...
Antonio
1 year ago
Haha, these questions always try to trick you. I'm going with C. Explicitly set SeeAllData to True and generate the data in the test methods. Best of both worlds, right?
upvoted 0 times
Joanne
1 year ago
That's a good point. Maybe creating test data in production before deploying would be a safer option.
upvoted 0 times
...
Chara
1 year ago
But wouldn't setting SeeAllData to True affect other test classes as well?
upvoted 0 times
...
Huey
1 year ago
Yeah, that sounds like a good approach. It ensures the test methods have access to production data.
upvoted 0 times
...
Chanel
1 year ago
I think C is the way to go. Set SeeAllData to True and generate data in the test methods.
upvoted 0 times
...
...
Annmarie
1 year ago
Hmm, I think B is the way to go. If you set SeeAllData to True, you can use the real data in production, right? That's gotta be easier than generating a whole bunch of test data.
upvoted 0 times
...
Cristal
1 year ago
Oh man, I totally had this one! The correct answer is D. Using SeeAllData in production is a big no-no, it can lead to some serious issues. Better to generate data in the test methods, that's the way to go.
upvoted 0 times
Lyla
1 year ago
Generating data in the test methods is definitely the safer option.
upvoted 0 times
...
Trevor
1 year ago
I agree, using SeeAllData in production is risky.
upvoted 0 times
...
...

Save Cancel