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

Pegasystems PEGACPSSA23V1 Exam - Topic 3 Question 34 Discussion

Select the three Pega best practices for developing activities. (Choose Three)
A) Keep activities short. Limit your activities to fewer than 15 steps. and C) Limit custom Java steps whenever possible. and E) Limit the use of activities. Use alternative rule types such as data transforms whenever possible.
B) Limit activity calls to at most three to prevent performance problems.
D) Use only activities to support queue processing and interfaces.

Pegasystems PEGACPSSA23V1 Exam - Topic 3 Question 34 Discussion

Actual exam question for Pegasystems's PEGACPSSA23V1 exam
Question #: 34
Topic #: 3
[All PEGACPSSA23V1 Questions]

Select the three Pega best practices for developing activities. (Choose Three)

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

Pega best practices recommend keeping activities short to enhance maintainability and readability. Custom Java steps should be limited to reduce complexity and potential errors. Activities should also be limited in general, with preference given to other rule types that are more declarative and less procedural, like data transforms, to improve application performance and maintainability. Reference: Pega SSA course materials on activity best practices.


by Nakita at Mar 22, 2025, 03:11 PM

Limited Time Offer

25%

Off

Get Premium PEGACPSSA23V1 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Shaun
8 months ago
Yeah, using data transforms instead of activities makes sense!
upvoted 0 times
...
Leigha
8 months ago
Surprised that using activities for everything is still a thing.
upvoted 0 times
...
Dalene
8 months ago
I think limiting activity calls to three is a bit strict.
upvoted 0 times
...
Tegan
9 months ago
Definitely agree on keeping activities short! Less is more.
upvoted 0 times
...
Dusti
9 months ago
Custom Java steps should really be avoided, for sure!
upvoted 0 times
...
Ciara
9 months ago
I think we talked about using alternative rule types like data transforms instead of activities, so maybe that's one of the best practices too.
upvoted 0 times
...
Olive
9 months ago
I feel like limiting custom Java steps is important, but I can't remember if it's a best practice or just something we discussed in class.
upvoted 0 times
...
Junita
10 months ago
I remember something about limiting activity calls to improve performance, but I can't recall the exact number. Was it three or five?
upvoted 0 times
...
Alayna
10 months ago
I think keeping activities short is definitely a best practice, but I'm not sure if it should be fewer than 15 steps or if that's just a guideline.
upvoted 0 times
...
Carey
10 months ago
Alright, let me think this through. Limiting activity steps, calls, and custom code - those make sense to me as best practices. I'll go with those three.
upvoted 0 times
...
Lorriane
10 months ago
I'm feeling pretty confident about this. The key seems to be balancing performance, maintainability, and flexibility when designing Pega activities.
upvoted 0 times
...
Denny
10 months ago
Wait, I'm a bit confused. Should we really be limiting the use of activities altogether? I'm not sure about that one.
upvoted 0 times
...
Kasandra
11 months ago
Okay, I think I've got this. Keeping activities short, limiting activity calls, and minimizing custom Java steps seem like solid best practices to focus on.
upvoted 0 times
...
Hollis
11 months ago
Hmm, this looks like a tricky one. I'll need to carefully review the best practices for Pega activities to make sure I select the right three.
upvoted 0 times
...
Stefany
1 year ago
I also think D is a good practice. Using only activities for queue processing and interfaces can help maintain consistency.
upvoted 0 times
...
Larue
1 year ago
Hmm, let's see. I'll go with A, C, and E. Gotta keep those activities lean and mean, and use alternatives when you can. Oh, and no Java if you can help it - that's just asking for trouble!
upvoted 0 times
Erasmo
1 year ago
User1: Let's stick to those best practices for developing activities.
upvoted 0 times
...
Harrison
1 year ago
User3: Agreed, avoiding custom Java steps is important for performance.
upvoted 0 times
...
Dewitt
1 year ago
User2: Definitely, keeping activities short and using alternatives is key.
upvoted 0 times
...
Merlyn
1 year ago
User1: I think A, C, and E are the way to go.
upvoted 0 times
...
Sharika
1 year ago
Agreed, avoiding Java whenever possible is a good practice. Activities should be kept simple and efficient.
upvoted 0 times
...
Dan
1 year ago
Using alternative rule types like data transforms is a good idea. Activities should be used sparingly.
upvoted 0 times
...
Gracia
1 year ago
Definitely, limiting custom Java steps is important. Stick to activities and data transforms.
upvoted 0 times
...
Galen
1 year ago
Definitely, avoiding custom Java steps is a good idea to prevent issues.
upvoted 0 times
...
Nobuko
1 year ago
I agree, keeping activities short and using data transforms is key.
upvoted 0 times
...
Wendell
1 year ago
I agree, keeping activities short is key. Less than 15 steps is the way to go.
upvoted 0 times
...
...
Nu
1 year ago
That's a tough one, but I'd go with A, C, and E. Wouldn't want to overload the system with too many activities, you know?
upvoted 0 times
...
Kenneth
1 year ago
A, C, and E. Totally agree, activities should be short and sweet. And who needs Java when you've got rule types like data transforms?
upvoted 0 times
...
Edna
1 year ago
I agree with Tom. Keeping activities short, limiting activity calls, and avoiding custom Java steps are important for performance.
upvoted 0 times
...
Tom
1 year ago
I think A, B, and C are the best practices for developing activities.
upvoted 0 times
...
Wava
1 year ago
B, C, and E. Limiting activity calls is crucial to avoid performance issues. Plus, custom Java can be a real performance hog if not used carefully.
upvoted 0 times
...
Valentin
1 year ago
A, C, and E for sure. Keeping activities short and limiting custom Java is just good practice. And using alternatives to activities whenever possible is key for performance.
upvoted 0 times
Belen
1 year ago
Limiting custom Java and using data transforms instead of activities is definitely the way to go. It helps with performance and maintenance in the long run.
upvoted 0 times
...
Nancey
1 year ago
I agree, keeping activities short and avoiding custom Java is important for performance. Data transforms are a great alternative to activities.
upvoted 0 times
...
Talia
1 year ago
A, C, and E are definitely the way to go. Short activities, minimal Java, and using data transforms instead of activities is the way to go.
upvoted 0 times
...
...

Save Cancel