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 2 Question 15 Discussion

Actual exam question for Pegasystems's PEGACPLSA88V1 exam
Question #: 15
Topic #: 2
[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:

Leota
5 months ago
Wait, we're supposed to be protecting confidential data, not playing hide-and-seek with it. Encrypt that stuff, I say!
upvoted 0 times
...
Shaniqua
5 months ago
I think the Access When rule is the best option here. It's more flexible than just hiding the fields, and you can still give the HR Manager access when they need it.
upvoted 0 times
Nickolas
3 months ago
But with PropertyRead, you can easily manage access to the SSN and date of birth without complicating things.
upvoted 0 times
...
Michel
3 months ago
I think Property Encrypt would be more secure, though. It adds an extra layer of protection to the data.
upvoted 0 times
...
Shawna
3 months ago
I agree, using an Access When rule allows for more control over who can see the information.
upvoted 0 times
...
Loreen
3 months ago
C) Add an Access When rule for access role objects of the HR Manager role.
upvoted 0 times
...
Bev
4 months ago
B) Add the privilege rule for the UI controls that display the SSN and date of birth.
upvoted 0 times
...
Keneth
4 months ago
A) Use the PropertyRead access control policy for the SSN and date of birth.
upvoted 0 times
...
...
Willard
5 months ago
I prefer option D because encrypting the data adds an extra layer of security.
upvoted 0 times
...
Daryl
5 months ago
I'm not sure, I think option C could also work if we limit access based on roles.
upvoted 0 times
...
Geraldo
5 months ago
Hmm, I don't know. Isn't there a way to just, I don't know, magic it away or something? Like, make it disappear with a wave of the wand?
upvoted 0 times
Merissa
4 months ago
B) Add the privilege rule for the UI controls that display the SSN and date of birth.
upvoted 0 times
...
Lynelle
5 months ago
A) Use the PropertyRead access control policy for the SSN and date of birth.
upvoted 0 times
...
...
Mollie
5 months ago
I'm not so sure about that. Encrypting the data could make it harder to work with, and the PropertyRead policy might be a simpler solution.
upvoted 0 times
...
Nana
6 months ago
I agree with Vanda, option A seems like the most secure way to protect sensitive information.
upvoted 0 times
...
Lazaro
6 months ago
Option D is definitely the way to go. Encrypting the data is the most secure way to protect confidential information like SSN and date of birth.
upvoted 0 times
Dorethea
5 months ago
I agree, using Property Encrypt access control policy for the SSN and date of birth is the best approach to ensure only the HR Manager can see the details.
upvoted 0 times
...
Isadora
5 months ago
Option D is definitely the way to go. Encrypting the data is the most secure way to protect confidential information like SSN and date of birth.
upvoted 0 times
...
...
Vanda
6 months ago
I think option A is the best approach because it restricts access to the actual data.
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