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

CompTIA Exam DS0-001 Topic 2 Question 33 Discussion

Actual exam question for CompTIA's DS0-001 exam
Question #: 33
Topic #: 2
[All DS0-001 Questions]

A group of developers needs access to a database in a development environment, but the database contains sensitive dat

a. Which of the following should the database administrator do before giving the developers access to the environment?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Broderick
1 months ago
If you ask me, the best way to handle sensitive data is to just print it all out and bury it in the backyard. That's what I'd do!
upvoted 0 times
Hailey
6 days ago
A: Audit access to tables with sensitive data.
upvoted 0 times
...
Hyman
17 days ago
C: Encrypt connections to the development environment.
upvoted 0 times
...
Clarence
22 days ago
B: Mask the sensitive data.
upvoted 0 times
...
Laura
1 months ago
A: Audit access to tables with sensitive data.
upvoted 0 times
...
...
Selma
2 months ago
I heard a rumor that one developer tried to encrypt the entire database. Turns out they just made a really big paperweight.
upvoted 0 times
Jess
6 days ago
D: Encrypting connections to the development environment is another important step to take.
upvoted 0 times
...
Sena
11 days ago
C: Removing sensitive data from tables could also be a good precaution.
upvoted 0 times
...
Amber
29 days ago
B: They should also consider masking the sensitive data before giving access to developers.
upvoted 0 times
...
Deandrea
1 months ago
A: The database administrator should audit access to tables with sensitive data.
upvoted 0 times
...
...
Sylvia
2 months ago
Auditing access is a good idea, but it doesn't actually protect the data. Gotta go with option C and mask that sensitive stuff.
upvoted 0 times
...
Asha
2 months ago
I once tried to remove all the sensitive data from a database. Ended up with an empty database and very confused developers. Option C is the way to go.
upvoted 0 times
Agustin
24 days ago
A) Audit access to tables with sensitive data.
upvoted 0 times
...
Alica
25 days ago
C) Mask the sensitive data.
upvoted 0 times
...
...
Alfred
2 months ago
Encryption is important, but it doesn't address the underlying issue of sensitive data exposure. Option C is the way to go.
upvoted 0 times
...
Micheline
2 months ago
Option C seems to be the best choice. Masking the sensitive data is a good way to protect it while still allowing the developers access.
upvoted 0 times
Sherita
17 days ago
D: Yes, that would be a good additional step to ensure security.
upvoted 0 times
...
Verona
29 days ago
C: Should we also audit access to the tables with sensitive data?
upvoted 0 times
...
Felton
1 months ago
B: That's a good idea. It will protect the data while still allowing them to work.
upvoted 0 times
...
Devorah
1 months ago
A: I think we should mask the sensitive data before giving access to the developers.
upvoted 0 times
...
...
Louvenia
2 months ago
I think masking the sensitive data could also be a good option to protect it from unauthorized access.
upvoted 0 times
...
Dominga
2 months ago
I agree with Eleni. It's important to monitor who has access to the sensitive data.
upvoted 0 times
...
Eleni
2 months ago
I think the database administrator should audit access to tables with sensitive 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