Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
A healthcare provider is designing an analytics data pipeline on Google Cloud to process electronic health records containing Protected Health Information (PHI) and Personally Identifiable Information (PII). The platform must comply with HIPAA and GDPR requirements.
The compliance architecture must satisfy the following criteria:
Which combination of Google Cloud controls should the organization implement?
This architecture combines Sensitive Data Protection (formerly Cloud DLP), Resource Location Organization Policies, and VPC Service Controls to establish a defense-in-depth security and compliance baseline for sensitive workloads governed by HIPAA and GDPR.
constraints/gcp.resourceLocations) define explicit geographic constraints at the organization, folder, or project level, preventing users from creating cloud resources and storing data outside compliant regions.This solution leverages native, enterprise-grade Google Cloud governance and security mechanisms designed specifically to address data privacy, residency, and exfiltration prevention systematically across all layers of the cloud environment.
This option suggests using Secret Manager for data de-identification, BigQuery authorized views for multi-region access, and Uniform Bucket-Level Access for storage security.
The primary goal was managing application API credentials centrally and consolidating storage access controls under unified IAM policies.
To protect against exfiltration, IAM access must be complemented by network perimeter controls such as VPC Service Controls.
This option attempts to use Google Cloud Armor for payload inspection at Layer 7, IAM Conditions for access management, and Firewall Rules Logging for exfiltration defense.
The requirement were focused solely on protecting public web endpoints from Layer 7 injection attacks and auditing VPC network connections.
Managed services communicate across Google's private API plane, which bypasses standard VPC firewall rules entirely.
This option proposes using Binary Authorization to inspect data, Cloud NAT to restrict outbound egress, and Cloud KMS with default Google-managed keys.
The objective was securing the software supply chain by enforcing container signature validation before deploying microservices.
De-identifying sensitive data before storage requires content-aware data processing pipelines, not container deployment gates.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated