GDPR Architecture & System Design 3 — Questions and Answers
Question 1: In a cloud-native architecture, which mechanism BEST supports GDPR data residency requirements when deploying across multiple regions?
- Replicating all data globally for high availability regardless of origin
- Geo-fencing with data sovereignty controls that restrict replication to approved regions (Correct answer)
- Using a CDN to cache all data at edge nodes worldwide
- Storing data in the cheapest available region by default
Correct answer: Geo-fencing with data sovereignty controls that restrict replication to approved regions
Geo-fencing with data sovereignty controls ensures personal data of EU residents remains within approved jurisdictions, supporting GDPR's data transfer restrictions.
Question 2: Which architectural pattern for handling data subject access requests (DSARs) is most scalable for large enterprise systems with dozens of data stores?
- Manual spreadsheet tracking of all data store locations
- A data discovery and metadata catalog integrated with automated DSAR orchestration (Correct answer)
- Requiring each team to respond independently when requests arrive
- Storing all personal data in a single monolithic database for easy retrieval
Correct answer: A data discovery and metadata catalog integrated with automated DSAR orchestration
A metadata catalog combined with automated orchestration enables systematic, auditable, and timely responses to DSARs across many data stores.
Question 3: When designing audit logging for GDPR compliance, which characteristic is MOST important for the logs themselves?
- Logs should be human-readable and stored in plain text files
- Logs must be tamper-evident, access-controlled, and retained for an appropriate period (Correct answer)
- Logs should capture all data in full fidelity including complete PII values
- Logs should be deleted weekly to minimize storage of personal data
Correct answer: Logs must be tamper-evident, access-controlled, and retained for an appropriate period
Audit logs must be tamper-evident to serve as trustworthy accountability records, access-controlled to prevent unauthorized modification, and retained to support breach investigation and regulatory inquiries.
Question 4: A system architect proposes using a blockchain to store personal data to ensure immutability. Why is this problematic under GDPR?
- Blockchain technology is too expensive to operate at scale
- Immutability conflicts with the right to erasure and right to rectification (Correct answer)
- Blockchain networks cannot achieve the throughput needed for GDPR compliance
- Regulators have explicitly banned blockchain use for personal data
Correct answer: Immutability conflicts with the right to erasure and right to rectification
Blockchain's core property of immutability directly conflicts with GDPR Articles 17 and 16, which grant individuals the right to erasure and correction of personal data.
Question 5: Which concept describes the architectural practice of giving each system component only the minimum access to personal data needed to perform its function?
- Defense in depth
- Principle of least privilege (Correct answer)
- Zero trust architecture
- Security through obscurity
Correct answer: Principle of least privilege
The principle of least privilege limits each component's access to only the personal data it genuinely needs, directly supporting GDPR data minimization and integrity requirements.
Question 6: When designing a system that transfers personal data to a third-party analytics provider, which architecture pattern best maintains GDPR compliance?
- Sending raw personal data directly to the analytics provider's API
- Pre-processing data to anonymize or pseudonymize it before transmission (Correct answer)
- Granting the analytics provider direct database access
- Delaying transfers until the provider requests data manually
Correct answer: Pre-processing data to anonymize or pseudonymize it before transmission
Pre-processing to anonymize or pseudonymize reduces the risk to data subjects and may remove the transfer from GDPR scope entirely if true anonymization is achieved.
Question 7: Under GDPR's 'security by design' principle, when should encryption key management be considered in the system design lifecycle?
- After the system is deployed and handling live personal data
- During the initial design phase, before any architecture decisions are finalized (Correct answer)
- Only when a security audit flags it as a risk
- When key management is requested by a data subject
Correct answer: During the initial design phase, before any architecture decisions are finalized
GDPR Article 25 requires data protection by design, meaning encryption and key management strategies must be embedded from the earliest design stages, not retrofitted.
GDPR Architecture & System Design 3
In a cloud-native architecture, which mechanism BEST supports GDPR data residency requirements when deploying across multiple regions?