Cloud Digital Leader Trust and security with Google Cloud Practice Question
A company's security architect wants to implement 'privacy by design' principles when building a new customer data platform on Google Cloud. What does privacy by design mean in this context?
⚠ Common exam trap
A common mix-up: candidates confuse privacy by design with a single technical control (like encryption or VPNs) or assume it prohibits data collection entirely, when in fact it is a holistic architectural approach that integrates multiple privacy controls from the outset.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Privacy by design means privacy protections (encryption, data minimization, access controls, retention policies) are architected into the system from the start, not added after deployment.
Privacy by design is a foundational principle that requires embedding privacy controls—such as encryption, data minimization, access controls, and retention policies—into the architecture of a system from the initial design phase, rather than retrofitting them after deployment. In the context of Google Cloud, this means using services like Cloud KMS for encryption, IAM for fine-grained access control, and data lifecycle policies to minimize data collection and enforce retention limits from the start. Option B correctly captures this proactive, integrated approach.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Privacy by design means the platform must refuse to collect any personal data from customers.
Why it's wrong here
Privacy by design never requires refusing to collect personal data; that would contradict the legitimate business purposes for which data is needed. Instead, it operationalizes principles like data minimization (collect only what is necessary) and purpose limitation (use data only for the declared reason). A system can collect personal data as long as the collection is lawful, transparent, and protected throughout its lifecycle. Refusing all personal data is an overcorrected misreading that would make most customer-facing cloud services impossible to deliver.
- ✓
Privacy by design means privacy protections (encryption, data minimization, access controls, retention policies) are architected into the system from the start, not added after deployment.
Why this is correct
Privacy by design makes privacy a foundational design principle: choosing which data to collect, how to protect it, who can access it, and when to delete it are designed before the first line of code — not discovered at audit time.
- ✗
Privacy by design is a legal requirement that mandates using only on-premises systems for customer data.
Why it's wrong here
GDPR Article 25 does mandate data protection by design, but it does not prescribe on-premises infrastructure. The principle requires implementing technical and organizational measures such as pseudonymization, encryption, and access control, which cloud providers can fully support. On-premises deployments are not automatically more privacy-compliant; they can suffer from poor access governance, unencrypted storage, or weak patching. Thus, equating privacy by design with a ban on cloud data residency conflates architectural principles with deployment topology.
- ✗
Privacy by design means storing all data in an encrypted format and using a VPN for all access.
Why it's wrong here
Encryption at rest and VPNs in transit are important security controls, but they represent only one layer of privacy protection. Privacy by design encompasses broader lifecycle principles, including data minimization (avoiding unnecessary collection), purpose limitation (restricting use to the stated intent), and retention policies (scheduled deletion). Encrypting everything does not address whether data was collected lawfully, whether access is limited to authorized personnel, or whether it is kept beyond its useful life. This option mistakes a subset of confidentiality safeguards for the full privacy-by-design framework.
Go deeper
Related to this question
Learn chapter
Cloud Digital Transformation
Key term
Least privilege
Least privilege is a security principle that means giving users, systems, or programs only the minimum permissions they need to do their job and nothing more.
Key term
KMS
KMS (Key Management Service) is a Microsoft technology that automates volume licensing activation for Windows and Office products within an organization's network.
About these practice questions
Courseiva writes every GCDL question from scratch — 829 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.