Your organization wants to be compliant with the General Data Protection Regulation (GDPR) on Google Cloud. You must implement data residency and operational sovereignty in the EU. What should you…

Question

Options

• ALimit the physical location of a new resource with the Organization Policy Service "resource
• BUse Cloud IDS to get east-west and north-south traffic visibility in the EU to monitor intra-VPC
• CLimit Google personnel access based on predefined attributes such as their citizenship or
• DUse identity federation to limit access to Google Cloud resources from non-EU entities.
• EUse VPC Flow Logs to monitor intra-VPC and inter-VPC traffic in the EU.

• A
  79% (22)
• B
  7% (2)
• D
  4% (1)
• E
  11% (3)

Explanation

GDPR compliance on Google Cloud requires both data residency (keeping data physically within the EU) and operational sovereignty (controlling who - including Google employees - can access it). Option A addresses data residency by using the Organization Policy Service constraint 'gcp.resourceLocations' to enforce that new resources can only be created in EU regions/multi-regions. Option C addresses operational sovereignty by restricting Google support personnel access using attributes like citizenship or location via Access Approvals combined with Assured Workloads, which allows EU-based organizations to require that only EU-based Google staff can access their environment. Cloud IDS (B) and VPC Flow Logs (E) provide network visibility but do not enforce residency or sovereignty. Identity federation (D) controls external entity access but does not directly enforce GDPR data residency or limit Google personnel access.

No community discussion yet for this question.