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 26 Discussion

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

The opportunity Service and opportunity Service Test classes are in package A but are used only in package B. Both second-generation packages have the same namespace. Therefore, they should be moved to package B for better organization and control.

What should the architect recommend for this process?

Show Suggested Answer Hide Answer
Suggested Answer: A, D

by Helaine at Nov 25, 2023, 10:51 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
Bettyann
3 months ago
Just changing the code in package B should be enough, right?
upvoted 0 times
...
Makeda
3 months ago
Option C sounds like the best approach for future-proofing.
upvoted 0 times
...
Heike
3 months ago
Surprised they were in the wrong package to begin with!
upvoted 0 times
...
Cherrie
4 months ago
I disagree, deprecating them first seems unnecessary.
upvoted 0 times
...
Leoma
4 months ago
Moving classes to package B makes sense for organization.
upvoted 0 times
...
Helga
4 months ago
I feel like setting them as deprecated and recreating them with new names could lead to confusion. Is that really necessary?
upvoted 0 times
...
Shawna
4 months ago
This question reminds me of a similar practice we did where we had to refactor classes. I think option C makes sense for version control.
upvoted 0 times
...
Nettie
4 months ago
I’m a bit unsure about the best approach. Should we really deprecate them first, or just move them directly?
upvoted 0 times
...
Art
5 months ago
I remember we discussed the importance of maintaining clean architecture. Moving the classes to package B seems like a good idea for organization.
upvoted 0 times
...
Thurman
5 months ago
I'm not totally sure about this one. There are a few different options, and I'm not 100% confident in my understanding of the implications of each. I think I'll need to review the material again and maybe consult with a colleague before making a decision.
upvoted 0 times
...
Annmarie
5 months ago
I'm leaning towards option C - moving the classes to package B and creating new package versions. That way, we can ensure that the changes are properly versioned and rolled out to all the dependent code.
upvoted 0 times
...
Anastacia
5 months ago
Okay, I've got this. The key here is that the classes in package A are only used in package B, and the two packages have the same namespace. So the best solution is to move the classes to package B and update the references in package B, which is option B.
upvoted 0 times
...
Iraida
5 months ago
Hmm, I'm a bit confused by this question. I'm not sure if I should go with option A and just deprecate the classes in package A, or if I should actually move them to package B. I'll need to think this through carefully.
upvoted 0 times
...
Olive
5 months ago
This seems like a straightforward question about package organization. I think I'll go with option B - moving the classes from package A to package B and updating the code in package B that references them.
upvoted 0 times
...
Karol
5 months ago
I think I've got a strategy here. The key is understanding how the view and table changes interact with the final code block. I'll work through it carefully.
upvoted 0 times
...
Bobbye
5 months ago
Okay, let me walk through this step-by-step. The child accepted 1 bite out of 10 offered, so we need to measure the percentage of bites accepted. I'm pretty confident C, percent of occurrence, is the right answer here.
upvoted 0 times
...
Gracia
5 months ago
Hmm, I'm a bit confused about the specific steps to configure this. I'll need to read through the instructions carefully.
upvoted 0 times
...
Twila
5 months ago
I'm pretty sure we practiced a question similar to this, and it involved creating a profile for updates. That might be option D.
upvoted 0 times
...
Jani
5 months ago
I think I've got it! The output should be "red blue yellow" since the `color` variable is set to those values in the nested loops.
upvoted 0 times
...
Monte
10 months ago
Option B is the way to go, unless of course, you're feeling adventurous and want to try Option D - 'Recreate the classes with new names!' That way, you can really keep your team on their toes. 'Wait, which class are we using again?' Ah, the joys of software development!
upvoted 0 times
...
Carmelina
10 months ago
Option B is the clear winner here. I mean, who wants to deal with deprecated classes and new package versions? That's just asking for trouble. This is a no-brainer.
upvoted 0 times
Lawrence
8 months ago
It's definitely the easiest option to just move the classes and update the code. No need for deprecated classes and new package versions.
upvoted 0 times
...
Asuncion
9 months ago
Yeah, moving the classes from package A to package B and updating the code in package B makes the most sense.
upvoted 0 times
...
Jettie
9 months ago
I agree, option B seems like the most straightforward solution.
upvoted 0 times
...
...
Mariann
10 months ago
Option B is the way to go. It's the most efficient solution that minimizes the impact on the existing codebase. Deprecating and recreating classes seems like a lot of unnecessary work.
upvoted 0 times
Francis
9 months ago
Yeah, it makes sense to minimize the impact on the existing codebase.
upvoted 0 times
...
Daron
9 months ago
I agree, option B seems like the most efficient solution.
upvoted 0 times
...
Yvonne
9 months ago
Yeah, it makes sense to just move the classes and update the code in package B.
upvoted 0 times
...
Lili
10 months ago
I agree, option B seems like the most efficient solution.
upvoted 0 times
...
...
Karrie
10 months ago
I think option C is the best choice. Moving the classes to package B and creating new versions seems like the most efficient solution.
upvoted 0 times
...
Stevie
11 months ago
I agree with Elinore. It will make it easier to control and manage the classes.
upvoted 0 times
...
Kimbery
11 months ago
I'm not a fan of moving classes around just for the sake of organization. Option C seems like overkill, and Option D could cause compatibility issues. I'd go with Option B.
upvoted 0 times
Velda
9 months ago
Let's go with Option B then.
upvoted 0 times
...
Grover
9 months ago
Yeah, changing the code in package B is probably the most straightforward solution.
upvoted 0 times
...
Elsa
9 months ago
Option B seems like the safest choice.
upvoted 0 times
...
Daisy
10 months ago
I agree, moving classes around can be risky.
upvoted 0 times
...
...
Gretchen
11 months ago
Option B seems like the most logical choice. By moving the classes to package B and updating the code in package B, we can maintain the existing functionality without disrupting the system.
upvoted 0 times
...
Elinore
11 months ago
I think we should move the classes to package B for better organization.
upvoted 0 times
...

Save Cancel