The purpose of this procedure is to ensure that all traffic originating from your own GCP VPC, going out to your JFrog JPD (residing in the same region) will be routed automatically via the Private Service Connect, rather than via public Internet. Traffic going out to other JFrog domains, such as remote JPDs located in other regions, or to other JFrog services such as releases.jfrog.io, will continue to be routed via public Internet.
Note
Once you set up an GCP Private Service Connect via MyJFrog, JFrog automatically creates an additional domain name that reaches your instance, in the format acme.pe.jfrog.io. This domain will be used by your Private Service Connect setup. For example, if your standard public JFrog domain is myservername.jfrog.io, then the additional domain will be myservername.pe.jfrog.io.
How you choose to set up your DNS in GCP depends on your organization's architecture. Follow the Google Cloud documentation for instructions on creating a record that points to your Private Service Connect endpoint IP address.