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 Exam PEGACPSSA23V1 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:

Submit Cancel
Stefany
2 months 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
2 months 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
Gracia
Definitely, limiting custom Java steps is important. Stick to activities and data transforms.
upvoted 0 times
...
Galen
18 days ago
Definitely, avoiding custom Java steps is a good idea to prevent issues.
upvoted 0 times
...
Nobuko
19 days ago
I agree, keeping activities short and using data transforms is key.
upvoted 0 times
...
Wendell
1 months ago
I agree, keeping activities short is key. Less than 15 steps is the way to go.
upvoted 0 times
...
...
Nu
2 months 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
2 months 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
2 months ago
I agree with Tom. Keeping activities short, limiting activity calls, and avoiding custom Java steps are important for performance.
upvoted 0 times
...
Tom
2 months ago
I think A, B, and C are the best practices for developing activities.
upvoted 0 times
...
Wava
2 months 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
2 months 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 months 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 months 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 months 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