- A
Privacy by design means the platform must refuse to collect any personal data from customers.
Why wrong: Privacy by design doesn't prohibit data collection — it requires that privacy considerations shape how data is collected, stored, and processed. Data minimization (collect only what's needed) is one principle.
- B
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 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.
- C
Privacy by design is a legal requirement that mandates using only on-premises systems for customer data.
Why wrong: Privacy by design is an architectural principle (codified in GDPR Article 25), not a deployment location requirement. Cloud systems can and do implement privacy by design.
- D
Privacy by design means storing all data in an encrypted format and using a VPN for all access.
Why wrong: Encryption and VPN are security controls — one element of privacy protection. Privacy by design is broader: it encompasses data minimization, purpose limitation, transparency, and the full lifecycle of personal data.
Quick Answer
The answer is that privacy by design means embedding privacy protections—such as encryption, data minimization, access controls, and retention policies—directly into the system’s architecture from the start, rather than adding them after deployment. This is correct because the principle shifts privacy from a reactive checklist to a proactive, foundational requirement, ensuring that every layer of the Google Cloud platform, from Cloud KMS for encryption to IAM for granular access and lifecycle policies for data retention, inherently respects user privacy. On the Google Cloud Digital Leader exam, this concept tests your understanding of how to operationalize privacy as a design constraint, not a patch; a common trap is choosing an answer that describes adding privacy controls later or treating them as separate compliance steps. To remember this, think of the mnemonic “Build In, Don’t Bolt On”—privacy must be architected into the foundation, not retrofitted as an afterthought.
Cloud Digital Leader Trust and security with Google Cloud Practice Question
This GCDL practice question tests your understanding of trust and security with google cloud. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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?
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.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 doesn't prohibit data collection — it requires that privacy considerations shape how data is collected, stored, and processed. Data minimization (collect only what's needed) is one principle.
- ✓
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.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Privacy by design is a legal requirement that mandates using only on-premises systems for customer data.
Why it's wrong here
Privacy by design is an architectural principle (codified in GDPR Article 25), not a deployment location requirement. Cloud systems can and do implement privacy by design.
- ✗
Privacy by design means storing all data in an encrypted format and using a VPN for all access.
Why it's wrong here
Encryption and VPN are security controls — one element of privacy protection. Privacy by design is broader: it encompasses data minimization, purpose limitation, transparency, and the full lifecycle of personal data.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often 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.
Detailed technical explanation
How to think about this question
Under the hood, privacy by design on Google Cloud involves using services such as Cloud Data Loss Prevention (DLP) to automatically classify and redact sensitive data, Cloud Audit Logs for monitoring access, and Object Lifecycle Management to enforce retention and deletion policies. For example, a real-world scenario might use BigQuery with column-level security and dynamic data masking to ensure that only authorized analysts see personally identifiable information (PII), while the underlying storage uses CMEK (Customer-Managed Encryption Keys) for encryption at rest. This approach aligns with the seven foundational principles of privacy by design, including proactive not reactive, privacy as the default, and end-to-end security.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Trust and security with Google Cloud — study guide chapter
Learn the concepts, then practise the questions
- →
Trust and security with Google Cloud practice questions
Targeted practice on this topic area only
- →
All GCDL questions
507 questions across all exam domains
- →
Google Cloud Digital Leader study guide
Full concept coverage aligned to exam objectives
- →
GCDL practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related GCDL practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Why cloud technology is transforming business practice questions
Practise GCDL questions linked to Why cloud technology is transforming business.
Fundamental cloud concepts practice questions
Practise GCDL questions linked to Fundamental cloud concepts.
Google Cloud products, services, and solutions practice questions
Practise GCDL questions linked to Google Cloud products, services, and solutions.
Scaling with Google Cloud operations practice questions
Practise GCDL questions linked to Scaling with Google Cloud operations.
Trust and security with Google Cloud practice questions
Practise GCDL questions linked to Trust and security with Google Cloud.
GCDL fundamentals practice questions
Practise GCDL questions linked to GCDL fundamentals.
GCDL scenario practice questions
Practise GCDL questions linked to GCDL scenario.
GCDL troubleshooting practice questions
Practise GCDL questions linked to GCDL troubleshooting.
Practice this exam
Start a free GCDL practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this GCDL question test?
Trust and security with Google Cloud — This question tests Trust and security with Google Cloud — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: 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.
What should I do if I get this GCDL question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.