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

Exin Exam PDPF Topic 5 Question 70 Discussion

Actual exam question for Exin's PDPF exam
Question #: 70
Topic #: 5
[All PDPF Questions]

One of the seven principles of data protection by design is Functionality - Positive-Sum, not Zero-Sum. What is the essence of this principle?

Show Suggested Answer Hide Answer
Suggested Answer: D

Applied security standards must assure the confidentiality, integrity and availability of personal data throughout their lifecycle. Incorrect. This is an aspect of End-to-End Security - Lifecycle Protection, one of the other six basic principles.

If different types of legitimate objectives are contradictory, the privacy objectives must be given priority over other security objectives. Incorrect. Data protection by design rejects the idea that privacy competes with other interests, design objectives, and technical capabilities.

When embedding privacy into a given technology, process, or system, it should be done in such a way that full functionality is not impaired. Correct. This is the essence. (Literature: A, Chapter 8; GDPR Article 25)

Wherever possible, detailed privacy impact and risk assessments should be carried out and published, clearly documenting the privacy risks. Incorrect. This is an aspect of Privacy Embedded into Design, one of the other six basic principles.


Contribute your Thoughts:

Raina
2 months ago
Option D is the way to go. No one wants a privacy-focused system that's a pain to use. Gotta strike that balance, you know?
upvoted 0 times
Quentin
12 days ago
Absolutely, we want systems that are user-friendly and secure at the same time.
upvoted 0 times
...
Lennie
14 days ago
It can be tricky, but it's crucial to make sure privacy measures don't hinder the usability of a system.
upvoted 0 times
...
Kristel
21 days ago
I agree, it's all about finding that balance between functionality and privacy.
upvoted 0 times
...
Melissia
1 months ago
Option D is definitely important. We need systems that work well while also protecting our privacy.
upvoted 0 times
...
...
Flo
2 months ago
Haha, sounds like a classic case of data privacy vs. usability. Can't we just have a 'privacy' button that does it all?
upvoted 0 times
...
Rosendo
2 months ago
I agree with Loreen, this principle is about ensuring privacy is integrated in a way that doesn't compromise the overall functionality.
upvoted 0 times
Wilda
29 days ago
C) Wherever possible, detailed privacy impact and risk assessments should be carried out and published, clearly documenting the privacy risks.
upvoted 0 times
...
Gerri
1 months ago
B) Applied security standards must assure the confidentiality, integrity and availability of personal data throughout their lifecycle.
upvoted 0 times
...
Adelina
1 months ago
A) If different types of legitimate objectives are contradictory, the privacy objectives must be given priority over other security objectives.
upvoted 0 times
...
...
Quentin
2 months ago
I believe option D is the correct answer. We need to embed privacy into technology without impairing functionality.
upvoted 0 times
...
Orville
2 months ago
I agree with Lilli. It's important to prioritize privacy objectives over other security objectives.
upvoted 0 times
...
Lilli
2 months ago
I think the essence of this principle is to ensure that privacy is not compromised for the sake of functionality.
upvoted 0 times
...
Loreen
3 months ago
Option D is clearly the correct answer here. Functionality should not be sacrificed for privacy, we need a balanced approach.
upvoted 0 times
Tawny
2 months ago
Yes, it's important to ensure that privacy measures do not hinder the full functionality of a system.
upvoted 0 times
...
Tawny
3 months ago
I agree, sacrificing functionality for privacy is not ideal.
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