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 PEGACPLSA88V1 Topic 8 Question 17 Discussion

Actual exam question for Pegasystems's PEGACPLSA88V1 exam
Question #: 17
Topic #: 8
[All PEGACPLSA88V1 Questions]

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?

Show Suggested Answer Hide 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.


Contribute your Thoughts:

Johnson
3 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
2 months ago
C) Implement Federated Case Management.
upvoted 0 times
...
Jennie
2 months ago
B) Leverage database replication to communicate case creation.
upvoted 0 times
...
Daren
2 months ago
A) Synchronize case creation with RFST services.
upvoted 0 times
...
...
Charlene
3 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
3 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
2 months ago
Maybe, but Federated Case Management seems more robust.
upvoted 0 times
...
Tabetha
2 months ago
But wouldn't synchronizing case creation with RFST services be simpler?
upvoted 0 times
...
Dean
2 months ago
I agree, it would make things a lot smoother.
upvoted 0 times
...
Fausto
3 months ago
Federated Case Management sounds like the way to go.
upvoted 0 times
...
...
Carole
3 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
3 months ago
I think implementing Federated Case Management would be the best option for this scenario.
upvoted 0 times
...
Ashlyn
3 months ago
I agree, database replication could cause more problems than it solves.
upvoted 0 times
...
...
Margarett
3 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
3 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
Jennifer
2 months ago
D) Implement a parent case across multiple products.
upvoted 0 times
...
Ngoc
2 months ago
C) Implement Federated Case Management.
upvoted 0 times
...
Gilma
2 months ago
B) Leverage database replication to communicate case creation.
upvoted 0 times
...
Raina
2 months ago
A) Synchronize case creation with RFST services.
upvoted 0 times
...
...
Mari
3 months ago
I agree with Inocencia. It seems like the most efficient way to meet the new business requirement.
upvoted 0 times
...
Inocencia
4 months ago
I think we should implement Federated Case Management.
upvoted 0 times
...

Save Cancel