Cloud Digital Leader Fundamental Cloud Concepts Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Organization policies with location restrictions

  Why this is correct

  Organization policies with location restrictions specifically enforce data residency by using constraints such as `gcp.resource-locations` to limit where cloud resources can be created. These policies are applied hierarchically at the organization, folder, or project level, and any resource creation request that specifies a region outside the allowed list is denied. This is a preventive control that stops non-compliant infrastructure from being provisioned in the first place, making it the correct mechanism for the company's data location requirements.

• ✗

  Cloud Audit Logs

  Why it's wrong here

  Cloud Audit Logs provide a record of administrative and data-access activities, capturing details like who performed an action, when, and from where, but they are purely detective rather than preventive. They can help you review whether data has been accessed or where resources were created after the fact, yet they have no ability to restrict or block resource creation in non-approved regions. Therefore, audit logs are useful for compliance verification but cannot enforce geographic data residency, so they are incorrect for this scenario.

• ✗

  Cloud KMS

  Why it's wrong here

  Cloud KMS is responsible for creating, rotating, and managing encryption keys that protect data at rest, but key management is unrelated to the physical location where data is stored. You can encrypt data using CMEK and still store it in any region, as keys and data are independent entities. Since KMS does not filter or constrain resource deployment locations, it cannot enforce a data residency policy, making it an incorrect answer.

• ✗

  VPC Service Controls

  Why it's wrong here

  VPC Service Controls uses service perimeters to restrict data movement based on identity and context, which helps prevent exfiltration, but it does not dictate where resources are physically deployed. Resources inside a perimeter can be distributed across multiple regions, and the service does not evaluate geographic location when allowing access. While it is a strong security control for addressing data breach risk, it does not meet the requirement to restrict data processing to specific geographic regions like the EU, so it is wrong.

Go deeper

Related to this question