Pegasystems PEGACPLSA88V1 Exam - Topic 8 Question 17 Discussion

Actual exam question for Pegasystems's PEGACPLSA88V1 exam

Question #: 17
Topic #: 8

MyCo.com has instances of SCM-F5, SmartDispute, and CPM-F5 in their Production Environment distributed across multiple Pega instances. A new business requirement states that users working in any one application cart create a case in any other application.

What is your recommendation to implement the new business requirement?

ASynchronize case creation with RFST services.

BLeverage database replication to communicate case creation.

CImplement Federated Case Management.

DImplement a parent case across multiple products.

Show Suggested Answer

Suggested Answer: A

Using the PropertyRead access control policy for the SSN and date of birth ensures that only users with the appropriate access (e.g., HR Manager) can view these details. This approach masks the information for other users.

Reference:

Pega best practices for data security and access control recommend using PropertyRead policies to restrict access to sensitive information.

Therefore, the correct answer is:

A . Use the PropertyRead access control policy for the SSN and date of birth.

by Clarence at Jul 16, 2024, 02:38 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Amber

3 months ago

B seems too complicated for this requirement.

upvoted 0 times

...

Tyisha

3 months ago

Wait, can they really create cases across different apps like that?

upvoted 0 times

...

Noe

3 months ago

A sounds like a solid plan, but what about performance?

upvoted 0 times

...

Tony

4 months ago

Not sure about that, D could work too.

upvoted 0 times

...

Shizue

4 months ago

I think option C is the best choice for this.

upvoted 0 times

...

Glory

4 months ago

Implementing a parent case across multiple products seems like a valid option, but I’m not confident it would meet the requirement effectively.

upvoted 0 times

...

Judy

4 months ago

Database replication sounds familiar, but I feel like it might complicate things more than necessary for this requirement.

upvoted 0 times

...

Arlen

4 months ago

I think synchronizing case creation with RFST services might be the right approach, but I need to double-check the specifics.

upvoted 0 times

...

Nakita

5 months ago

I remember we discussed Federated Case Management in class, but I'm not entirely sure how it applies here.

upvoted 0 times

...

Queen

5 months ago

I'm leaning towards the parent case approach. That seems like it would provide the most flexibility and integration between the different applications.

upvoted 0 times

...

Jerry

5 months ago

Synchronizing case creation with RFST services could be a good option, but I'm not sure how that would work across multiple Pega instances. I'll have to explore that further.

upvoted 0 times

...

Gracia

5 months ago

Okay, I think I've got a handle on this. Implementing Federated Case Management seems like the most straightforward way to meet the new requirement.

upvoted 0 times

...

Isabella

5 months ago

Hmm, I'm a bit unsure about this one. I'll need to review the Pega documentation on case management and integration to see what the best solution might be.

upvoted 0 times

...

Elizabeth

5 months ago

This looks like a tricky one. I'll need to carefully consider the different options and think through the pros and cons of each approach.

upvoted 0 times

...

Yesenia

5 months ago

I'm a bit unsure about this one. The two life cycles don't seem to line up perfectly, so I'll need to think it through step-by-step to make sure I get the right answer.

upvoted 0 times

...

Luis

5 months ago

I remember discussing the benefits of using DataWorks in class. It seemed like the most efficient way to manage such a large project.

upvoted 0 times

...

Johnson

10 months ago

Federated Case Management is the way to go. It's like a superhero team-up, but for your business applications. Who doesn't love a good crossover event?

upvoted 0 times

Casie

9 months ago

C) Implement Federated Case Management.

upvoted 0 times

...

Jennie

9 months ago

B) Leverage database replication to communicate case creation.

upvoted 0 times

...

Daren

9 months ago

A) Synchronize case creation with RFST services.

upvoted 0 times

...

Charlene

10 months ago

RFST services? Sounds like a delicious breakfast cereal. I'll take two bowls, please! Oh, wait, we're talking about a Pega certification exam. My bad.

upvoted 0 times

...

Paris

10 months ago

Implementing a parent case across multiple products? That's like trying to herd cats, if you ask me. Federated Case Management is definitely the most elegant solution here.

upvoted 0 times

Oliva

9 months ago

Maybe, but Federated Case Management seems more robust.

upvoted 0 times

...

Tabetha

9 months ago

But wouldn't synchronizing case creation with RFST services be simpler?

upvoted 0 times

...

Dean

9 months ago

I agree, it would make things a lot smoother.

upvoted 0 times

...

Fausto

10 months ago

Federated Case Management sounds like the way to go.

upvoted 0 times

...

Carole

10 months ago

I'm not sure about the database replication approach. That could get messy and lead to potential data inconsistencies. I'd rather go with the RFST services or Federated Case Management options.

upvoted 0 times

Jaleesa

10 months ago

I think implementing Federated Case Management would be the best option for this scenario.

upvoted 0 times

...

Ashlyn

10 months ago

I agree, database replication could cause more problems than it solves.

upvoted 0 times

...

Margarett

10 months ago

I'm not sure about Federated Case Management. Maybe we should consider implementing a parent case across multiple products instead.

upvoted 0 times

...

Isaac

11 months ago

Federated Case Management seems like the way to go here. It allows seamless integration between the different applications and can handle the case creation requirements across the applications.

upvoted 0 times