Configure Psc Service Attachment Nat Subnet Firewall

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An enterprise data engineering team is establishing a private, cross-VPC data ingestion pipeline to transfer sensitive analytical workloads into a managed database. To prevent overlapping IP space issues and strictly isolate tenant networks, the architecture requires exposing the database backend to consumer VPCs using a Private Service Connect (PSC) service attachment behind an internal forwarding rule.

Which configuration must you implement in the producer VPC network to enable secure connectivity and permit traffic from the PSC service attachment to the target backend instance?

Establish VPC Network Peering between the producer and consumer VPCs, configure custom route export, and create an ingress firewall rule with target tag 0.0.0.0/0.

Configure the service attachment to use the primary default compute subnetwork, and create an ingress firewall rule allowing traffic originating directly from the consumer VPC's source subnet CIDR block.

Enable Cloud NAT on the producer VPC router, attach an external forwarding rule to the database proxy, and deploy an egress firewall rule on the database subnet.

Provision a dedicated subnetwork with the purpose set to PRIVATE_SERVICE_CONNECT, assign it to the service attachment's NAT subnets, and configure an ingress firewall rule allowing traffic from this NAT subnetwork's CIDR range to the target backend instance.

Professional Cloud Data Engineer

Configure Psc Service Attachment Nat Subnet Firewall

Related questions