Your company is active in the European Economic Area (EEA), and will adopt Google Cloud...

The correct answer is A because the policy must apply across projects that are already spread across different folders. Setting the resource location constraint at the organization level gives consistent inheritance across the whole resource hierarchy instead of requiring repeated folder-level configuration. Since the business requirement is to permit only EEA locations, an allow-list model is safer than a deny-list model. A deny list can miss future or unexpected locations, while allowed values define the permitted geographic boundary. Google Cloud’s resource locations constraint supports allowed_values and denied_values, and Google recommends using allowed values or value groups to define the geographic boundary for resources.