You are allocating an IP range for Private Services Access to enable Cloud SQL private IP in your VPC. Which requirement must the allocated range meet?

Private Services Access (PSA) for Cloud SQL requires a dedicated IP range within your Virtual Private Cloud (VPC) network. This range must be a reserved secondary (alias) IP range in the same consumer VPC where your Cloud SQL instance will reside. This ensures that the private connection between your VPC and Google's services (where Cloud SQL runs) is established correctly and securely. Crucially, this allocated range cannot overlap with any existing subnets in your VPC to prevent IP address conflicts. Public IP ranges are incorrect because PSA is for private connectivity. A different project is incorrect as the connection needs to be within the same VPC. IPv6 global ranges are not used for this specific private service connection.