Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

CertNexus Exam ITS-110 Topic 1 Question 16 Discussion

Actual exam question for CertNexus's ITS-110 exam
Question #: 16
Topic #: 1
[All ITS-110 Questions]

A cloud developer for an IoT service is storing billing information. Which of the following should be considered a common vulnerability in regard to this data that could be used to compromise privacy?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Isadora
1 months ago
I can't believe they're even considering A as an option. Enabling notifications is a feature, not a vulnerability! The real issue is B - poor data retention policies.
upvoted 0 times
Irving
3 days ago
We need to make sure the data is secured in motion and at rest.
upvoted 0 times
...
Laurena
4 days ago
Yeah, lack of data retention policies is a real problem.
upvoted 0 times
...
Iola
12 days ago
I agree, enabling notifications is not a vulnerability.
upvoted 0 times
...
...
Delbert
2 months ago
Haha, I bet the developers are 'resting' pretty comfortably while the data is 'in motion' all over the place. D is definitely not the right choice here.
upvoted 0 times
Mari
18 days ago
User 3: Securing data in motion and at rest is crucial for protecting billing information.
upvoted 0 times
...
Farrah
19 days ago
User 2: Yeah, that could definitely lead to privacy issues.
upvoted 0 times
...
Paris
25 days ago
User 1: Lack of data retention policies is a big vulnerability.
upvoted 0 times
...
...
Nathan
2 months ago
C sounds like the right answer to me. Authorized access to personal info is a big vulnerability, even if the access is supposed to be legitimate.
upvoted 0 times
Salina
5 days ago
We should always be cautious about who has access to sensitive data.
upvoted 0 times
...
Stephaine
10 days ago
Definitely, even if the access is supposed to be legitimate.
upvoted 0 times
...
Ben
12 days ago
I agree, authorized access to personal info can be a big vulnerability.
upvoted 0 times
...
Graciela
13 days ago
C sounds like the right answer to me.
upvoted 0 times
...
Cristy
23 days ago
We should always be cautious about who has access to sensitive data.
upvoted 0 times
...
Devorah
25 days ago
Even if the access is supposed to be legitimate.
upvoted 0 times
...
Ellsworth
1 months ago
I agree, authorized access to personal info is a big vulnerability.
upvoted 0 times
...
Elise
1 months ago
C sounds like the right answer to me.
upvoted 0 times
...
...
Avery
2 months ago
But what about securing data in motion and at rest? Wouldn't that also be important to protect privacy?
upvoted 0 times
...
Dalene
2 months ago
I agree with Teri. Without proper data retention policies, sensitive billing information could be exposed.
upvoted 0 times
...
Shenika
2 months ago
Option A is a legal requirement, not a vulnerability. I think the correct answer is B - lack of data retention policies. That could lead to sensitive information being kept longer than necessary, increasing the risk of a breach.
upvoted 0 times
Lizbeth
2 months ago
B: Yeah, keeping sensitive information longer than necessary is definitely a risk.
upvoted 0 times
...
France
2 months ago
A: I think the correct answer is B - lack of data retention policies.
upvoted 0 times
...
...
Teri
2 months ago
I think lack of data retention policies could be a vulnerability.
upvoted 0 times
...
Karma
2 months ago
But what about securing data in motion and at rest? Wouldn't that also be important to protect privacy?
upvoted 0 times
...
Willodean
2 months ago
I agree with Elly. Without proper data retention policies, sensitive billing information could be exposed.
upvoted 0 times
...
Elly
3 months ago
I think lack of data retention policies could be a vulnerability.
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