Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization uses a Shared VPC (prod-shared-vpc) in host project host-vpc-prod, with application workloads deployed in attached service projects app-a-prod and app-b-prod. A separate security project (sec-ops-proj) runs a standalone VPC (sec-vpc).
You must implement private DNS resolution using least-privilege IAM for automation service accounts (tf-app-a, tf-app-b, tf-sec) with these requirements:
appa.internal., appb.internal.) without creating new VPCs or modifying other host project DNS zones.sec-vpc resolve appa.internal. and appb.internal. without VPC Network Peering.Which architecture and IAM configuration should you implement?
app-a-prod and app-b-prod to bind their private zones to prod-shared-vpc, granting tf-app-a and tf-app-b roles/dns.admin on host-vpc-prod. Create Cloud DNS peering zones in sec-ops-proj targeting prod-shared-vpc, granting tf-sec roles/dns.admin on sec-ops-proj and roles/dns.peer on app-a-prod and app-b-prod.This approach attempts to combine cross-project binding and DNS peering, but assigns DNS Administrator (roles/dns.admin) at the host project level to service project automation and assigns DNS Peer (roles/dns.peer) to the consumer service account on the service projects instead of the host project.
host-vpc-prod: Granting roles/dns.admin on host-vpc-prod gives tf-app-a and tf-app-b full administrative control over every managed zone (including public zones and other teams' records) and DNS server policies in the host project.sec-ops-proj creates a DNS peering zone targeting prod-shared-vpc, Cloud DNS checks whether tf-sec holds dns.networks.targetWithPeeringZone (provided by roles/dns.peer) on the project that owns the producer VPC network (host-vpc-prod). Granting roles/dns.peer on app-a-prod and app-b-prod causes peering zone creation to fail with a permission error.roles/dns.admin: Includes permissions to create, update, and delete all public zones, private zones, and policies across the entire target project.dns.networks.bindPrivateDNSZone specifically governs binding a private zone to a VPC network without granting zone modification rights on other zones in that project.Cross-project binding were replaced by zones bound to independent VPCs owned inside app-a-prod and app-b-prod (making them the producer VPC projects for tf-sec), and the security team did not require least-privilege separation between host and service project DNS administration.
app-a-prod and app-b-prod to bind their private zones to prod-shared-vpc, granting their service accounts dns.managedZones.create in their respective service projects and dns.networks.bindPrivateDNSZone on host-vpc-prod. Create Cloud DNS peering zones in sec-ops-proj targeting prod-shared-vpc, granting tf-sec roles/dns.admin on sec-ops-proj and roles/dns.peer on host-vpc-prod.Cloud DNS cross-project binding allows service projects in a Shared VPC to create and own private managed zones within their own project boundaries while binding those zones directly to the Shared VPC network owned by the host project. Cloud DNS peering creates a unidirectional relationship where a DNS consumer network forwards queries for a specific domain suffix to a DNS producer network for resolution according to the producer's name resolution order.
app-a-prod and app-b-prod own and manage appa.internal. and appb.internal. in their respective service projects without creating placeholder VPCs.dns.managedZones.create inside each service project and only dns.networks.bindPrivateDNSZone on host-vpc-prod separates private zone binding from broader DNS Administrator (roles/dns.admin) privileges in the host project, preventing teams from modifying host-level zones or policies.sec-ops-proj targeting prod-shared-vpc enables workloads in sec-vpc to resolve appa.internal. and appb.internal. directly over Cloud DNS control-plane routing without VPC Network Peering.tf-sec roles/dns.admin in sec-ops-proj and roles/dns.peer (dns.networks.targetWithPeeringZone) on host-vpc-prod satisfies peering permissions because prod-shared-vpc—the producer VPC network—resides in the host project.prod-shared-vpc with no extra VPC overhead.prod-shared-vpc immediately resolve cross-project bound zones with no transitive hop limit.sec-vpc resolves the targeted suffixes without exposing other internal routing or subnets.Unlike hosting all zones in the host project or creating placeholder VPCs, combining cross-project binding for Shared VPC service projects with DNS peering for standalone VPCs preserves strict administrative isolation, follows the principle of least privilege, and leverages native Cloud DNS resolution without unnecessary network peering.
appa.internal. and appb.internal. directly in host-vpc-prod authorized for prod-shared-vpc, granting tf-app-a and tf-app-b roles/dns.admin on host-vpc-prod. Connect sec-vpc to prod-shared-vpc using VPC Network Peering and configure Cloud DNS forwarding zones in sec-ops-proj targeting prod-shared-vpc.Centralizing private zones in host-vpc-prod places all DNS zone ownership in the host project, while VPC Network Peering establishes Layer 3 IP connectivity between VPCs and Cloud DNS forwarding zones send queries for specific domain suffixes to target IP addresses (such as on-premises DNS servers).
appa.internal. and appb.internal. in host-vpc-prod and granting roles/dns.admin to tf-app-a and tf-app-b removes service project ownership boundaries and exposes host project DNS resources to modification by application automation.sec-vpc and prod-shared-vpc via VPC Network Peering introduces IP-level routing between the networks, which is explicitly prohibited and does not automatically share private Cloud DNS zones.sec-vpc needed to forward queries to on-premises DNS servers rather than Cloud DNS private zones in prod-shared-vpc—even then, sec-vpc would use a DNS peering zone targeting prod-shared-vpc (which holds the forwarding zone to on-premises), rather than a forwarding zone targeting prod-shared-vpc.
app-a-prod and app-b-prod to host their private zones, and configure Cloud DNS peering zones on prod-shared-vpc and sec-vpc targeting those placeholder VPCs. Grant tf-app-a and tf-app-b roles/dns.admin in their service projects, and grant tf-sec roles/dns.peer on app-a-prod and app-b-prod.Deploying placeholder VPC networks in service projects isolates private DNS zones within standalone VPCs and relies on Cloud DNS peering to forward queries between those placeholder VPCs, the Shared VPC, and external consumer VPCs.
app-a-prod and app-b-prod introduces unnecessary network resources that cross-project binding is explicitly designed to eliminate.prod-shared-vpc to resolve appa.internal. and appb.internal., host project administrators would have to configure and maintain peering zones on prod-shared-vpc targeting every service project's placeholder VPC.tf-sec roles/dns.peer on app-a-prod and app-b-prod only works if sec-vpc directly targets those placeholder VPCs, and even then, it creates fragmented peering meshes and complicates single transitive hop limits if sec-vpc attempts to resolve through prod-shared-vpc.prod-shared-vpc without additional peering zones.The application teams were prohibited from using cross-project binding (for example, if the projects belonged to different Google Cloud organizations where cross-project binding is unsupported) and genuinely operated isolated VPC networks rather than attaching workloads to a Shared VPC.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated