Cyber Monday 2024! 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]

In a Human Resources application, the Social Security Number (SSN) and date of birth details for employees are confidential, and business requirements state that only the HR Manager can see these details.

What is the best approach to mask the information for other users everywhere in the application?

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:

Dierdre
4 months ago
I'm just hoping I don't have to memorize any Social Security numbers for this exam. That would be the real security risk!
upvoted 0 times
...
Nathalie
4 months ago
I'm going with D. Gotta keep that SSN and birth date on lockdown, yo!
upvoted 0 times
Lajuana
3 months ago
A) Use the PropertyRead access control policy for the SSN and date of birth.
upvoted 0 times
...
Tony
3 months ago
C) Add an Access When rule for access role objects of the HR Manager role.
upvoted 0 times
...
Brandon
3 months ago
D. Gotta keep that SSN and birth date on lockdown, yo!
upvoted 0 times
...
...
Stefan
4 months ago
B looks good to me. Adding the privilege rule for the UI controls seems straightforward and effective.
upvoted 0 times
Yolando
4 months ago
B does seem like the most straightforward option for masking the information.
upvoted 0 times
...
Herman
4 months ago
I agree, adding the privilege rule for the UI controls makes sense.
upvoted 0 times
...
Trina
4 months ago
I think B is the best approach. It's simple and effective.
upvoted 0 times
...
...
Karl
4 months ago
I think option D is the way to go, using Property Encrypt access control policy for extra security.
upvoted 0 times
...
Kanisha
4 months ago
I'm not sure, but I think C might be the right answer. Sounds like it would restrict access to the HR Manager role.
upvoted 0 times
Jarvis
3 months ago
True, but using an Access When rule for the HR Manager role seems like a straightforward solution.
upvoted 0 times
...
Frederica
3 months ago
That's a good point. Property Encrypt could provide an extra layer of security.
upvoted 0 times
...
Ming
4 months ago
But wouldn't using Property Encrypt be more secure for masking the information?
upvoted 0 times
...
Mollie
4 months ago
I think C is the best option too. It restricts access to the HR Manager role.
upvoted 0 times
...
...
Leonida
5 months ago
I think D is the best approach. Encrypting the sensitive data is the most secure way to protect it.
upvoted 0 times
Nobuko
3 months ago
C) Add an Access When rule for access role objects of the HR Manager role.
upvoted 0 times
...
Phyliss
4 months ago
A) Use the PropertyRead access control policy for the SSN and date of birth.
upvoted 0 times
...
Sheridan
4 months ago
D) Use the Property Encrypt access control policy for the SSN and date of birth.
upvoted 0 times
...
...
Devorah
5 months ago
I prefer option C, adding an Access When rule for the HR Manager role.
upvoted 0 times
...
Bea
5 months ago
I agree with Beabye, using PropertyRead access control policy makes sense.
upvoted 0 times
...
Bobbye
5 months ago
I think option A is the best approach.
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