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)

AKeep activities short. Limit your activities to fewer than 15 steps.

BLimit activity calls to at most three to prevent performance problems.

CLimit custom Java steps whenever possible.

DUse only activities to support queue processing and interfaces.

ELimit the use of activities. Use alternative rule types such as data transforms whenever possible.

Show Suggested 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

5 days 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

6 days 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

...

Nu

7 days 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

8 days 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

11 days ago

I agree with Tom. Keeping activities short, limiting activity calls, and avoiding custom Java steps are important for performance.

upvoted 0 times

...

Tom

17 days ago

I think A, B, and C are the best practices for developing activities.

upvoted 0 times

...

Wava

23 days 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

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

...