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

Pegasystems Exam PEGAPCSSA87V1 Topic 6 Question 39 Discussion

Actual exam question for Pegasystems's PEGAPCSSA87V1 exam
Question #: 39
Topic #: 6
[All PEGAPCSSA87V1 Questions]

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

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Dorothy
2 months ago
Hold up, are we talking about Pega activities or doing laundry? Cause keeping it short and sweet is always a good idea, no matter what you're doing. But 15 steps, that's rookie numbers! Let's aim for 5 or less, folks.
upvoted 0 times
Rebecka
26 days ago
E) Limit the use of activities. Use alternative rule types such as data transforms whenever possible.
upvoted 0 times
...
Ezekiel
1 months ago
B) Limit activity calls to at most three to prevent performance problems.
upvoted 0 times
...
Giuseppe
1 months ago
A) Keep activities short. Limit your activities to fewer than 15 steps.
upvoted 0 times
...
...
Shanda
2 months ago
A, C, and E are the obvious choices here. Who wants to write a million steps in one activity anyway? As for the activity call limit, that's just a recipe for a headache if you ask me.
upvoted 0 times
Helaine
1 months ago
I think limiting custom Java steps is important too. It can make things more complicated.
upvoted 0 times
...
Lettie
1 months ago
I agree, keeping activities short and using data transforms when possible is key.
upvoted 0 times
...
Cassandra
2 months ago
A, C, and E are definitely the way to go. Who has time for long activities anyway?
upvoted 0 times
...
...
Argelia
3 months ago
I'm going with A, C, and E. Keeping activities short and using alternative rule types are definitely best practices. As for the activity call limit, I'm not convinced that's necessary in all cases.
upvoted 0 times
Chi
2 months ago
I think B is also important to consider to prevent performance issues.
upvoted 0 times
...
Shawnna
2 months ago
I agree with you, A, C, and E are solid choices for best practices.
upvoted 0 times
...
...
Tamera
3 months ago
I personally prefer D and E. Using activities for queue processing and interfaces, and limiting their use overall, seems more efficient to me.
upvoted 0 times
...
Ezekiel
3 months ago
A, C, and E for sure. Limiting custom Java is always a good idea, and using alternatives to activities can help with performance. Not sure about the activity call limit though, that seems a bit arbitrary.
upvoted 0 times
Heike
1 months ago
True, but it's important to also consider the specific requirements of the project when deciding on the best practices to follow.
upvoted 0 times
...
Ryan
2 months ago
I think limiting activity calls to three makes sense to prevent performance issues.
upvoted 0 times
...
Kandis
2 months ago
I agree, keeping activities short and using alternative rule types can improve performance.
upvoted 0 times
...
Stephaine
2 months ago
A, C, and E are definitely important. Custom Java should be limited, and using data transforms instead of activities can be helpful.
upvoted 0 times
...
...
Gladys
3 months ago
Hmm, this is a tricky one. I think A, C, and E are the best practices, but I'm not sure about the limit on activity calls. Guess I'll have to review my Pega best practices guide again.
upvoted 0 times
...
Reyes
3 months ago
I agree with Edison. Keeping activities short, limiting activity calls, and avoiding custom Java steps are important for performance.
upvoted 0 times
...
Edison
3 months ago
I think A, B, and C are the best practices for developing activities.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77