Google Professional Cloud Network Engineer Practice Test 61
Question 600
For an original Google Cloud Professional Cloud Network Engineer educational scenario, consider: Two independently governed VPCs must resolve private names without copying all records into each project, but DNS peering is not designed and duplicate zones drift. Select THREE compatible elements: a proper correction, a targeted diagnostic and an acceptance result.
- Check: Review zone type, NS delegation, complete record inventory, TTLs, authorized networks and both public and private DNS queries.
- Result: New traffic reaches the ready service while in-flight compatible sessions complete or recover according to documented expectations.
- Change: Configure supported cross-project private-zone binding or Cloud DNS peering according to zone ownership and approved consumer networks.
- Check: Inspect zone ownership, bound networks, peering zone targets, IAM for binding and queries originating in each VPC.
- Change: Select the appropriate supported internal or external regional/global Application or Network Load Balancer, mapping the protocol and control-plane requirements.
- Result: Only approved consumer networks resolve current central private records without duplicating or publicly exposing zones.
Explanation
Correct Answer
C:Cross-project zone binding and DNS peering provide different mechanisms for authorized private name visibility; VPC route peering alone does not always exchange private DNS zones. Acceptance: Only approved consumer networks resolve current central private records without duplicating or publicly exposing zones.
D:Cross-project zone binding and DNS peering provide different mechanisms for authorized private name visibility; VPC route peering alone does not always exchange private DNS zones. Required intervention: Configure supported cross-project private-zone binding or Cloud DNS peering according to zone ownership and approved consumer networks.
F:Cross-project zone binding and DNS peering provide different mechanisms for authorized private name visibility; VPC route peering alone does not always exchange private DNS zones. Evidence: Inspect zone ownership, bound networks, peering zone targets, IAM for binding and queries originating in each VPC.
Incorrect Answers
A:Check: Review zone type, NS delegation, complete record inventory, TTLs, authorized networks and both public and private DNS queries. Cross-project zone binding and DNS peering provide different mechanisms for authorized private name visibility; VPC route peering alone does not always exchange private DNS zones.
B:Result: New traffic reaches the ready service while in-flight compatible sessions complete or recover according to documented expectations. Cross-project zone binding and DNS peering provide different mechanisms for authorized private name visibility; VPC route peering alone does not always exchange private DNS zones.
E:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Global versus regional and proxy versus passthrough load balancing) rather than the documented Cloud DNS cross-project binding and peering decision.
Question 601
A Google Cloud Professional Network Engineer is reviewing this Google Cloud networking environment scenario: A Kubernetes Ingress receives a new load-balancer address, but its published app DNS still points to the prior deployment after manual records are forgotten. An unsafe shortcut would be: Let every cluster service account overwrite all organizational DNS zones because DNS changes are easy to reverse. What should the cloud network administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Let every cluster service account overwrite all organizational DNS zones because DNS changes are easy to reverse.
- Configure eligible Cross-Cloud Interconnect connectivity and VLAN attachments with both clouds' route, security and redundancy requirements explicitly integrated.
- Configure a supported external-dns controller with appropriate Cloud DNS zone ownership and limited permissions for the intended GKE services.
- Review Firewall Insights rule use and shadowing together with Network Analyzer configuration warnings, then validate changes using safe targeted tests.
Explanation
Correct Answer
C:Configure a supported external-dns controller with appropriate Cloud DNS zone ownership and limited permissions for the intended GKE services. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
Incorrect Answers
A:External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure. For this best change assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it.
B:Configure eligible Cross-Cloud Interconnect connectivity and VLAN attachments with both clouds' route, security and redundancy requirements explicitly integrated. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
D:Review Firewall Insights rule use and shadowing together with Network Analyzer configuration warnings, then validate changes using safe targeted tests. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
Question 602
A Google Cloud network infrastructure review finds: A Kubernetes Ingress receives a new load-balancer address, but its published app DNS still points to the prior deployment after manual records are forgotten. The team proposes: Configure a supported external-dns controller with appropriate Cloud DNS zone ownership and limited permissions for the intended GKE services. Which Google Cloud networking technical principle most strongly supports the proposed response? Select ONE best answer.
- External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
- Stateful appliances inspect traffic on paths they actually traverse; an ILB next-hop route and symmetric return path must both be designed explicitly.
- Network tags, resource-manager secure tags and service-account selectors have different scopes and compatibility; matching text labels do not grant identical targeting.
- Internet NEGs provide supported external origin connectivity; CDN eligibility, origin hostname and certificate behavior must match the actual backend path.
Explanation
Correct Answer
A:Relevant validation before approval: Review controller sources, domain or zone filters, TXT ownership, service frontend changes, API permissions and authoritative DNS readback.
Incorrect Answers
B:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Network virtual appliance multi-NIC and ILB routing) rather than the documented GKE external-dns operator and DNS automation decision.
C:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Network tags, secure tags and service-account firewall targets) rather than the documented GKE external-dns operator and DNS automation decision.
D:Internet NEGs provide supported external origin connectivity; CDN eligibility, origin hostname and certificate behavior must match the actual backend path. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
Question 603
The cloud network operations team has not approved a broad network-wide change. Available evidence indicates: A Kubernetes Ingress receives a new load-balancer address, but its published app DNS still points to the prior deployment after manual records are forgotten. Which evidence best tests the Google Cloud networking diagnosis before approving a disruptive change? Select ONE best answer.
- Examine topology resource scope, traffic metrics, direction and timestamps, then verify the selected path with routes or Connectivity Tests.
- Inspect spoke types, hub topology, route propagation, filters, effective reachability, and intended inspection-path evidence.
- Review controller sources, domain or zone filters, TXT ownership, service frontend changes, API permissions and authoritative DNS readback.
- Check origin type, load-balancer backend CDN flag, response cache headers, cache key, hit ratio and personalized-content negative tests.
Explanation
Correct Answer
C:Confirm afterward that: Approved GKE service records update after deployment while unrelated public and private zones remain unchanged.
Incorrect Answers
A:Examine topology resource scope, traffic metrics, direction and timestamps, then verify the selected path with routes or Connectivity Tests. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
B:Inspect spoke types, hub topology, route propagation, filters, effective reachability, and intended inspection-path evidence. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
D:Check origin type, load-balancer backend CDN flag, response cache headers, cache key, hit ratio and personalized-content negative tests. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
Question 604
A candidate network change has been piloted and stakeholders require a post-change acceptance check. Original problem: A Kubernetes Ingress receives a new load-balancer address, but its published app DNS still points to the prior deployment after manual records are forgotten. The accountable service owner requires evidence that outcomes are met without disrupting planned work. Which acceptance result demonstrates that the network response meets the intended outcome? Select ONE best answer.
- Public representations cache efficiently while personalized responses cannot be served across user boundaries.
- Large and small payloads complete reliably without disabling encryption or relying on fragmentation assumptions.
- Loss of redundancy is detected before an outage and failover restores approved prefixes within documented objectives.
- Approved GKE service records update after deployment while unrelated public and private zones remain unchanged.
Explanation
Correct Answer
D:External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
Incorrect Answers
A:Public representations cache efficiently while personalized responses cannot be served across user boundaries. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
B:Large and small payloads complete reliably without disabling encryption or relying on fragmentation assumptions. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
C:Loss of redundancy is detected before an outage and failover restores approved prefixes within documented objectives. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
Question 605
A production Google Cloud networking change review identifies the following problem: A Kubernetes Ingress receives a new load-balancer address, but its published app DNS still points to the prior deployment after manual records are forgotten. Which paired Google Cloud networking action and verification should close the review? Select ONE best answer.
- Change: Configure a supported external-dns controller with appropriate Cloud DNS zone ownership and limited permissions for the intended GKE services. Verify: Review controller sources, domain or zone filters, TXT ownership, service frontend changes, API permissions and authoritative DNS readback.
- Change: Configure supported cross-project private-zone binding or Cloud DNS peering according to zone ownership and approved consumer networks. Verify: Inspect zone ownership, bound networks, peering zone targets, IAM for binding and queries originating in each VPC.
- Change: Create or maintain a supported VPC-native GKE cluster with assigned primary and secondary subnet ranges sized for nodes, Pods and Services. Verify: Review cluster networking mode, subnet secondary assignments, max Pods per node, allocated ranges and scheduling/address failure events.
- Change: Analyze hierarchical firewall policies and VPC rules in documented evaluation order, then create the least-privilege policy at the governing scope. Verify: Inspect effective policy hierarchy, rule priority and action, source/service account or tags, and a scoped Connectivity Test.
Explanation
Correct Answer
A:This pair links the appropriate network response with evidence of the underlying cloud networking issue. Applied case: A Kubernetes Ingress receives a new load-balancer address, but its published app DNS still points to the prior deployment after manual records are forgotten.
Incorrect Answers
B:Change: Configure supported cross-project private-zone binding or Cloud DNS peering according to zone ownership and approved consumer networks. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
C:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (GKE VPC-native alias IP implementation) rather than the documented GKE external-dns operator and DNS automation decision.
D:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Hierarchical firewall policy precedence across organization) rather than the documented GKE external-dns operator and DNS automation decision.
Question 606
A Google Cloud Professional Network Engineer is reviewing this Google Cloud networking environment scenario: A cluster automation account is granted editor permissions to all DNS zones instead of only the approved managed zone for its namespace workloads. An unsafe shortcut would be: Let every cluster service account overwrite all organizational DNS zones because DNS changes are easy to reverse. What should the cloud network administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Configure a supported external-dns controller with appropriate Cloud DNS zone ownership and limited permissions for the intended GKE services.
- Let every cluster service account overwrite all organizational DNS zones because DNS changes are easy to reverse.
- Use Network Intelligence Center Performance Dashboard scopes and time windows to correlate latency and packet-loss measurements with affected paths.
- Identify the supported NCC VPC, hybrid and producer spoke roles and attach the correct eligible resources to the hub with designed route exchange.
Explanation
Correct Answer
A:Configure a supported external-dns controller with appropriate Cloud DNS zone ownership and limited permissions for the intended GKE services. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
Incorrect Answers
B:External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
C:Use Network Intelligence Center Performance Dashboard scopes and time windows to correlate latency and packet-loss measurements with affected paths. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
D:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (NCC VPC/hybrid/producer spoke selection) rather than the documented GKE external-dns operator and DNS automation decision.
Question 607
A Google Cloud network infrastructure review finds: A cluster automation account is granted editor permissions to all DNS zones instead of only the approved managed zone for its namespace workloads. The team proposes: Configure a supported external-dns controller with appropriate Cloud DNS zone ownership and limited permissions for the intended GKE services. Which Google Cloud networking technical principle most strongly supports the proposed response? Select ONE best answer.
- External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
- GKE controllers reconcile Kubernetes routing resources into Google Cloud load balancing, and controller/class and service endpoint compatibility control deployment.
- VPC Network Peering does not automatically provide transitive routing, and service-level PSC access avoids extending an entire routing domain for one producer.
- BGP control-plane establishment requires consistent neighbor identity and IP reachability; IPsec health alone does not prove route exchange.
Explanation
Correct Answer
A:Relevant validation before approval: Review controller sources, domain or zone filters, TXT ownership, service frontend changes, API permissions and authoritative DNS readback.
Incorrect Answers
B:GKE controllers reconcile Kubernetes routing resources into Google Cloud load balancing, and controller/class and service endpoint compatibility control deployment. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
C:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (VPC Network Peering constraints and alternatives) rather than the documented GKE external-dns operator and DNS automation decision.
D:BGP control-plane establishment requires consistent neighbor identity and IP reachability; IPsec health alone does not prove route exchange. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
Question 608
The cloud network operations team has not approved a broad network-wide change. Available evidence indicates: A cluster automation account is granted editor permissions to all DNS zones instead of only the approved managed zone for its namespace workloads. Which evidence best tests the Google Cloud networking diagnosis before approving a disruptive change? Select ONE best answer.
- Compare VPC mode, region, subnet CIDRs, private pool reservations, effective firewall evaluation and a controlled approved VM-to-service path.
- Inspect URL map route and weights, matching host/path, backend distribution, request headers and mirrored traffic safety.
- Inspect forward and return paths, effective policy routes, appliance NICs, load-balancer health and a forced appliance-failure trial.
- Review controller sources, domain or zone filters, TXT ownership, service frontend changes, API permissions and authoritative DNS readback.
Explanation
Correct Answer
D:Confirm afterward that: Approved GKE service records update after deployment while unrelated public and private zones remain unchanged.
Incorrect Answers
A:Compare VPC mode, region, subnet CIDRs, private pool reservations, effective firewall evaluation and a controlled approved VM-to-service path. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
B:Inspect URL map route and weights, matching host/path, backend distribution, request headers and mirrored traffic safety. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
C:Inspect forward and return paths, effective policy routes, appliance NICs, load-balancer health and a forced appliance-failure trial. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
Question 609
A candidate network change has been piloted and stakeholders require a post-change acceptance check. Original problem: A cluster automation account is granted editor permissions to all DNS zones instead of only the approved managed zone for its namespace workloads. The accountable service owner requires evidence that outcomes are met without disrupting planned work. Which acceptance result demonstrates that the network response meets the intended outcome? Select ONE best answer.
- Operators isolate the relevant changed network path and corroborate it with measurable forwarding evidence.
- Approved cross-boundary API calls succeed where explicitly allowed while unapproved data movement remains denied and logged.
- Production clients reach the correct backend and measured canary traffic follows approved proportions without unintended request disclosure.
- Approved GKE service records update after deployment while unrelated public and private zones remain unchanged.
Explanation
Correct Answer
D:External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure. The result must be validated using the documented site, route, application or user context.
Incorrect Answers
A:Operators isolate the relevant changed network path and corroborate it with measurable forwarding evidence. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
B:Approved cross-boundary API calls succeed where explicitly allowed while unapproved data movement remains denied and logged. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
C:Production clients reach the correct backend and measured canary traffic follows approved proportions without unintended request disclosure. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
Question 610
For an original Google Cloud Professional Cloud Network Engineer educational scenario, consider: A cluster automation account is granted editor permissions to all DNS zones instead of only the approved managed zone for its namespace workloads. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Configure a supported external-dns controller with appropriate Cloud DNS zone ownership and limited permissions for the intended GKE services.
- Change: Map actual NCC and VPC route propagation and nontransitive boundaries; use supported spokes or Private NAT and appropriate filters to meet required connectivity.
- Check: Review controller sources, domain or zone filters, TXT ownership, service frontend changes, API permissions and authoritative DNS readback.
- Check: Compare origin response, cache headers, edge response age, host/path invalidation scope and a subsequent request from representative regions.
- Let every cluster service account overwrite all organizational DNS zones because DNS changes are easy to reverse.
Explanation
Correct Answer
A:Evidence: Review controller sources, domain or zone filters, TXT ownership, service frontend changes, API permissions and authoritative DNS readback.
C:Acceptance: Approved GKE service records update after deployment while unrelated public and private zones remain unchanged.
Incorrect Answers
B:Change: Map actual NCC and VPC route propagation and nontransitive boundaries; use supported spokes or Private NAT and appropriate filters to meet required connectivity. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
D:Check: Compare origin response, cache headers, edge response age, host/path invalidation scope and a subsequent request from representative regions. External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure.
E:External DNS controllers reconcile eligible Kubernetes resources to authorized DNS record sets, and incorrect zone filters or broad IAM create drift or exposure. Use this instead: Configure a supported external-dns controller with appropriate Cloud DNS zone ownership and limited permissions for the intended GKE services.