Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
A financial enterprise operating in the European Union must comply with strict regional data sovereignty and localization mandates. The organization has activated data residency for Security Command Center (SCC) Enterprise tier across its organization hierarchy. The security compliance team mandates the following operational requirements:
Which configuration approach should the security engineering team implement to satisfy these data residency requirements?
constraints/gcp.resourceLocations organization policy constraint specifying in:eu-locations and route all API calls through the default securitycenter.googleapis.com endpoint.The constraints/gcp.resourceLocations constraint is an organization policy that defines the set of geographic locations where new supported Google Cloud resources (such as Compute Engine VMs, Cloud Storage buckets, or BigQuery datasets) can be provisioned.
securitycenter.googleapis.com).console.eu.cloud.google.com), leaving web traffic on the global console infrastructure.*.rep.googleapis.com) endpoints.The goal was solely to prevent developers from provisioning underlying infrastructure resources (like VMs and storage buckets) outside of EU regions across the resource hierarchy.
securitycenter.googleapis.com.VPC Service Controls (VPC-SC) creates secure network perimeters around Google-managed resources to mitigate data exfiltration risks, while Cloud NAT provides managed outbound internet access for instances without external IP addresses.
securitycenter.googleapis.com still hits the global API frontend rather than the dedicated regional data residency endpoint (securitycenter.LOCATION.rep.googleapis.com).console.eu.cloud.google.com) for security analysts.The requirement was to prevent exfiltration of data from internal VPC networks to unauthorized multi-tenant storage buckets or unauthorized Google Cloud projects.
securitycenter.LOCATION.rep.googleapis.com and instruct analysts to access the jurisdictional Google Cloud console at console.eu.cloud.google.com.Google Cloud provides regional service endpoints and jurisdictional web consoles for services like Security Command Center (SCC) to enforce strict data residency controls. When data residency is enabled, specific resource types (including findings, continuous export configurations, BigQuery export configurations, and mute rules) are pinned to a designated geographic boundary. Interacting with these resources requires using dedicated regional API endpoints (such as securitycenter.LOCATION.rep.googleapis.com) and jurisdictional console URLs (such as console.eu.cloud.google.com or console.eu.cloud.google for workforce identity federation).
securitycenter.LOCATION.rep.googleapis.com ensures that requests route directly to the specified EU location, maintaining data residency for resources while in transit and in use.console.eu.cloud.google.com guarantees that web UI sessions, queries, and displayed findings remain confined within the European Union jurisdiction.Using regional endpoints and the jurisdictional console is the required, native mechanism in Google Cloud for managing data residency-enabled Security Command Center resources. Global default endpoints and the standard console do not route to residency-isolated resources.
constraints/compute.setNewProjectDefaultToZonalDNSOnly constraint across all projects.Config Connector is an add-on that allows managing Google Cloud resources via Kubernetes Resource Model (KRM) manifests, and constraints/compute.setNewProjectDefaultToZonalDNSOnly is an organization policy constraint that forces internal Compute Engine DNS names to use zonal naming structures instead of global DNS.
compute.setNewProjectDefaultToZonalDNSOnly improves Compute Engine internal DNS reliability by avoiding cross-zone registration dependencies.The requirement was to enhance internal Compute Engine DNS fault isolation during zonal outages and manage cloud infrastructure via declarative Kubernetes custom resources.
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