As a managed-service producer exposing a private API via Private Service Connect, which components must you provide in your producer project to let consumers connect to your backends?

To expose a private API via Private Service Connect as a producer, you must create a regional service attachment. This service attachment acts as the interface for consumers to connect to your service. The backends providing the service must be reachable through either Network Endpoint Groups (NEGs) or load balancer backends (e.g., an internal HTTP(S) load balancer). This setup allows Private Service Connect to direct traffic from consumers to your service instances securely within your VPC. A public HTTP(S) load balancer with a global external IP is incorrect because Private Service Connect is for private, not public, access. VPC Network Peering to every consumer project is incorrect as Private Service Connect eliminates the need for direct peering with each consumer. Enabling Private Google Access on consumer projects is irrelevant for a producer's setup and is a consumer-side configuration for accessing Google APIs privately.