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

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

Erasmo

3 days ago

User1: Let's stick to those best practices for developing activities.

upvoted 0 times

...

Harrison

4 days ago

User3: Agreed, avoiding custom Java steps is important for performance.

upvoted 0 times

...

Dewitt

5 days ago

User2: Definitely, keeping activities short and using alternatives is key.

upvoted 0 times

...

Merlyn

6 days ago

User1: I think A, C, and E are the way to go.

upvoted 0 times

...

Sharika

7 days ago

Agreed, avoiding Java whenever possible is a good practice. Activities should be kept simple and efficient.

upvoted 0 times

...

Dan

8 days ago

Using alternative rule types like data transforms is a good idea. Activities should be used sparingly.

upvoted 0 times

...

Gracia

9 days ago

Definitely, limiting custom Java steps is important. Stick to activities and data transforms.

upvoted 0 times

...

Galen

27 days ago

Definitely, avoiding custom Java steps is a good idea to prevent issues.

upvoted 0 times

...

Nobuko

28 days ago

I agree, keeping activities short and using data transforms is key.

upvoted 0 times

...

Wendell

2 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

3 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

3 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

2 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

2 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

...