A public health agency in New Zealand is building a centralized patient registry on Google Cloud. To satisfy strict national health data sovereignty rules and data governance mandates, the organization has three mandatory security requirements:
1. All storage and compute resources holding patient records must be geographically restricted to the australia-southeast1 region.
2. Google Cloud support personnel must obtain explicit customer approval before accessing system logs or underlying infrastructure during troubleshooting.
3. The design must mitigate data exfiltration risks by preventing authorized internal users from transferring patient datasets to external, non-approved Cloud Storage buckets outside the environment boundary.
Which combination of Google Cloud architectural controls meets all three regulatory compliance requirements?
- Configure an Organization Policy enforcing the gcp.resourceLocations constraint restricted to australia-southeast1, enable Access Approval at the project hierarchy level, and establish a VPC Service Controls perimeter around the storage and analytical workloads.Answer
- BAssign primitive Owner IAM roles restricted exclusively to local system administrators, enable Access Approval for vendor support, and mandate Customer-Supplied Encryption Keys (CSEK) stored on-premises to enforce regional boundaries.
- CEnforce an Organization Policy for gcp.resourceLocations, mandate Customer-Supplied Encryption Keys (CSEK) managed in local hardware security modules to restrict data access, and implement standard IAM roles to prevent unauthorized bucket copies.
- DEnable Access Approval for support tickets, create custom IAM roles restricting user access, and rely on IAM storage permissions to block data transfers to external Google Cloud projects.