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 PEGAPCSSA87V1 Exam - Topic 6 Question 39 Discussion

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

Pegasystems PEGAPCSSA87V1 Exam - 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

by William at Aug 03, 2024, 10:53 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
My
7 months ago
Using data transforms instead of activities is a game changer!
upvoted 0 times
...
Gregoria
8 months ago
Wait, are we really supposed to limit activities that much? Seems odd.
upvoted 0 times
...
Elly
8 months ago
Custom Java steps should really be avoided, they complicate things.
upvoted 0 times
...
Hildegarde
8 months ago
I think limiting activity calls to three is a bit strict.
upvoted 0 times
...
Trina
8 months ago
Definitely agree on keeping activities short! Less is more.
upvoted 0 times
...
Deonna
9 months ago
I’m a bit confused about using activities for queue processing. I thought we could use other rule types too, but maybe I’m mixing it up.
upvoted 0 times
...
Jerry
9 months ago
I feel like there was a question similar to this on our practice exam, and I think limiting activity calls was one of the answers.
upvoted 0 times
...
Tiera
9 months ago
I think limiting custom Java steps is definitely a best practice. We discussed that in class to avoid complications.
upvoted 0 times
...
Veronika
9 months ago
I remember something about keeping activities short, but I'm not sure if it's fewer than 15 steps or something else.
upvoted 0 times
...
Brandee
9 months ago
I'm a bit confused on the best practice around activity calls. I'll need to double-check that one before answering.
upvoted 0 times
...
Rodolfo
9 months ago
Okay, let's see. I know we want to keep activities short and limit custom Java steps, so I'll definitely select those options.
upvoted 0 times
...
Ashlyn
9 months ago
Hmm, I'm a bit unsure about the right answer here. I'll need to think through the Pega best practices carefully.
upvoted 0 times
...
Eleonora
9 months ago
This looks like a pretty straightforward Pega best practices question. I'm confident I can handle this one.
upvoted 0 times
...
Luz
9 months ago
The key here is to balance performance and maintainability. I'll select the options that focus on those priorities.
upvoted 0 times
...
Kenneth
9 months ago
I'm a bit confused by the wording of the question. Does "directly belong to" mean the product is only assigned to the immediate parent category, or can it be in multiple categories? That could affect which option is best.
upvoted 0 times
...
Christiane
9 months ago
I think a SIP alias would be in a format similar to an email address, so I'm leaning towards option C with John.doe@cisco.com.
upvoted 0 times
...
Ashanti
9 months ago
I'm feeling pretty confident about this one. The customer should consider the control balance during the Discovery and Strategy stage, before they start implementing the SIAM model.
upvoted 0 times
...
Dorothy
1 year 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
1 year ago
E) Limit the use of activities. Use alternative rule types such as data transforms whenever possible.
upvoted 0 times
...
Ezekiel
1 year ago
B) Limit activity calls to at most three to prevent performance problems.
upvoted 0 times
...
Giuseppe
1 year ago
A) Keep activities short. Limit your activities to fewer than 15 steps.
upvoted 0 times
...
...
Shanda
1 year 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 year ago
I think limiting custom Java steps is important too. It can make things more complicated.
upvoted 0 times
...
Lettie
1 year ago
I agree, keeping activities short and using data transforms when possible is key.
upvoted 0 times
...
Cassandra
1 year ago
A, C, and E are definitely the way to go. Who has time for long activities anyway?
upvoted 0 times
...
...
Argelia
1 year 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
1 year ago
I think B is also important to consider to prevent performance issues.
upvoted 0 times
...
Shawnna
1 year ago
I agree with you, A, C, and E are solid choices for best practices.
upvoted 0 times
...
...
Tamera
1 year 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
1 year 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 year 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
1 year ago
I think limiting activity calls to three makes sense to prevent performance issues.
upvoted 0 times
...
Kandis
1 year ago
I agree, keeping activities short and using alternative rule types can improve performance.
upvoted 0 times
...
Stephaine
1 year 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
1 year 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
1 year ago
I agree with Edison. Keeping activities short, limiting activity calls, and avoiding custom Java steps are important for performance.
upvoted 0 times
...
Edison
1 year ago
I think A, B, and C are the best practices for developing activities.
upvoted 0 times
...

Save Cancel