Each dev team has its own project and all teams are located in the United States. You must prevent resource creation outside US locations. What should you do?

The correct approach is to place dev projects in a common folder and apply an organization policy constraining resource locations to US regions. Organization policies, specifically the "Resource Location Restriction" constraint, are designed to enforce geographical restrictions across projects, folders, or the entire organization. Applying it at the folder level ensures all projects within that folder inherit the restriction, preventing resource creation outside US locations. Creating a separate organization is unnecessary and adds management overhead. IAM policies control who can do what, not where resources can be created; they cannot enforce geographical location constraints. Binding IAM policies to roles across projects also does not address the requirement of restricting resource locations.