Google Professional Cloud Network Engineer Practice Test 3
Question 20
For an original Google Cloud Professional Cloud Network Engineer educational scenario, consider: A recovery team replicates application state across two regions but leaves all DNS and load-balancer health routing fixed to the failed primary region. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Declare an application multi-region resilient merely because two projects exist, without testing backend and traffic failover.
- Change: Configure supported route tags and route priority explicitly and verify destination specificity, eligible next-hop and instance applicability.
- Change: Design regional or multiregional backends, health-based traffic direction, state recovery and tested failure behavior appropriate to the required recovery objectives.
- Check: Exercise region and backend failures and inspect load-balancer backend health, recovery data state, traffic direction and observed recovery times.
- Check: Examine drain timeouts, backend health, active connections, weighted routing or URL map revisions and client error rates during a staging cutover.
Explanation
Correct Answer
C:Application availability needs healthy independent compute and data paths plus workable traffic failover; multiple regions on a slide do not provide a functioning recovery route. Evidence: Exercise region and backend failures and inspect load-balancer backend health, recovery data state, traffic direction and observed recovery times.
D:Application availability needs healthy independent compute and data paths plus workable traffic failover; multiple regions on a slide do not provide a functioning recovery route. Required intervention: Design regional or multiregional backends, health-based traffic direction, state recovery and tested failure behavior appropriate to the required recovery objectives.
Incorrect Answers
A:For this select two assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it. Application availability needs healthy independent compute and data paths plus workable traffic failover; multiple regions on a slide do not provide a functioning recovery route.
B:Change: Configure supported route tags and route priority explicitly and verify destination specificity, eligible next-hop and instance applicability. Application availability needs healthy independent compute and data paths plus workable traffic failover; multiple regions on a slide do not provide a functioning recovery route.
E:Check: Examine drain timeouts, backend health, active connections, weighted routing or URL map revisions and client error rates during a staging cutover. Application availability needs healthy independent compute and data paths plus workable traffic failover; multiple regions on a slide do not provide a functioning recovery route.
Question 21
A Google Cloud Professional Network Engineer is reviewing this Google Cloud networking environment scenario: Private on-premises resolvers cannot resolve private GCE service names, although VMs resolve them inside the VPC where the private zone is authorized. An unsafe shortcut would be: Publish sensitive internal host records into an internet public DNS zone solely to avoid configuring hybrid resolution. What should the cloud network administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Plan inbound and outbound DNS server policies, forwarding destinations, and authorized private-zone visibility for the on-premises/cloud hybrid resolution path.
- Publish sensitive internal host records into an internet public DNS zone solely to avoid configuring hybrid resolution.
- Configure supported DNS peering or cross-project binding and inbound/outbound forwarding with explicit zone visibility and bidirectional resolver paths.
- Review effective static, subnet and dynamic routes and choose supported next hops and route priorities, independently validating firewall admission.
Explanation
Correct Answer
A:Plan inbound and outbound DNS server policies, forwarding destinations, and authorized private-zone visibility for the on-premises/cloud hybrid resolution path. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
Incorrect Answers
B:Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone. For this best change assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it.
C:Configure supported DNS peering or cross-project binding and inbound/outbound forwarding with explicit zone visibility and bidirectional resolver paths. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
D:Review effective static, subnet and dynamic routes and choose supported next hops and route priorities, independently validating firewall admission. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
Question 22
A Google Cloud network infrastructure review finds: Private on-premises resolvers cannot resolve private GCE service names, although VMs resolve them inside the VPC where the private zone is authorized. The team proposes: Plan inbound and outbound DNS server policies, forwarding destinations, and authorized private-zone visibility for the on-premises/cloud hybrid resolution path. Which Google Cloud networking technical principle most strongly supports the proposed response? Select ONE best answer.
- Shared VPC allows service-project workloads to use designated host-project subnetworks when authorized; service project ownership alone is not host subnet access.
- Google Cloud VPC networks are global constructs while subnets and many forwarding resources are regional; resource location remains operationally significant.
- GKE control-plane reachability is governed by endpoint type, network path and authorization; merely configuring an allowed CIDR does not substitute for identity.
- Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
Explanation
Correct Answer
D:Demonstrable success requires: Both on-premises and cloud clients resolve approved internal names consistently without exposing private records on the public internet.
Incorrect Answers
A:Shared VPC allows service-project workloads to use designated host-project subnetworks when authorized; service project ownership alone is not host subnet access. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
B:Google Cloud VPC networks are global constructs while subnets and many forwarding resources are regional; resource location remains operationally significant. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
C:GKE control-plane reachability is governed by endpoint type, network path and authorization; merely configuring an allowed CIDR does not substitute for identity. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
Question 23
The cloud network operations team has not approved a broad network-wide change. Available evidence indicates: Private on-premises resolvers cannot resolve private GCE service names, although VMs resolve them inside the VPC where the private zone is authorized. Which evidence best tests the Google Cloud networking diagnosis before approving a disruptive change? Select ONE best answer.
- Inspect query source, authoritative or forwarded zones, inbound forwarding policy, outbound targets, network authorization and resolver query logs.
- Compare origin response, cache headers, edge response age, host/path invalidation scope and a subsequent request from representative regions.
- Trace VPC peer relationships, expected route visibility, overlapping CIDRs, producer endpoint scope and necessary service-level access.
- Audit allocated primary, secondary, hybrid, producer and translated CIDRs; test route resolution and NAT mapping from both sides.
Explanation
Correct Answer
A:Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
Incorrect Answers
B:Compare origin response, cache headers, edge response age, host/path invalidation scope and a subsequent request from representative regions. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
C:Trace VPC peer relationships, expected route visibility, overlapping CIDRs, producer endpoint scope and necessary service-level access. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
D:Audit allocated primary, secondary, hybrid, producer and translated CIDRs; test route resolution and NAT mapping from both sides. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
Question 24
A candidate network change has been piloted and stakeholders require a post-change acceptance check. Original problem: Private on-premises resolvers cannot resolve private GCE service names, although VMs resolve them inside the VPC where the private zone is authorized. 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.
- Only intended traffic traverses the healthy appliance tier in both directions with no unintended bypass.
- Large and small payloads complete reliably without disabling encryption or relying on fragmentation assumptions.
- New Pods obtain unique reachable alias IPs and cluster growth follows the planned address budget.
- Both on-premises and cloud clients resolve approved internal names consistently without exposing private records on the public internet.
Explanation
Correct Answer
D:Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone. The result must be validated using the documented site, route, application or user context.
Incorrect Answers
A:Only intended traffic traverses the healthy appliance tier in both directions with no unintended bypass. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
B:Large and small payloads complete reliably without disabling encryption or relying on fragmentation assumptions. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
C:New Pods obtain unique reachable alias IPs and cluster growth follows the planned address budget. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
Question 25
A production Google Cloud networking change review identifies the following problem: Private on-premises resolvers cannot resolve private GCE service names, although VMs resolve them inside the VPC where the private zone is authorized. Which paired Google Cloud networking action and verification should close the review? Select ONE best answer.
- Change: Plan supported policy-based or custom routing to a highly available appliance tier, using internal passthrough load balancer next hops where eligible. Verify: Inspect forward and return paths, effective policy routes, appliance NICs, load-balancer health and a forced appliance-failure trial.
- Change: Plan inbound and outbound DNS server policies, forwarding destinations, and authorized private-zone visibility for the on-premises/cloud hybrid resolution path. Verify: Inspect query source, authoritative or forwarded zones, inbound forwarding policy, outbound targets, network authorization and resolver query logs.
- Change: Use the supported GKE Gateway or Ingress controller and appropriate Service and NEG annotations or policies to expose healthy Pod backends. Verify: Inspect GatewayClass/IngressClass, listener and route status, Service endpoints, NEG health, firewall and external request results.
- Change: Correlate the full hybrid transport, BGP and VPC forwarding path and stage failure tests with explicit route preference and recovery criteria. Verify: Capture link/tunnel health, BGP advertisements, effective routes, firewall admission and end-to-end app flows before and after fault injection.
Explanation
Correct Answer
B:This pair links the appropriate network response with evidence of the underlying cloud networking issue. Applied case: Private on-premises resolvers cannot resolve private GCE service names, although VMs resolve them inside the VPC where the private zone is authorized.
Incorrect Answers
A:Change: Plan supported policy-based or custom routing to a highly available appliance tier, using internal passthrough load balancer next hops where eligible.
C:Change: Use the supported GKE Gateway or Ingress controller and appropriate Service and NEG annotations or policies to expose healthy Pod backends.
D:Change: Correlate the full hybrid transport, BGP and VPC forwarding path and stage failure tests with explicit route preference and recovery criteria.
Question 26
A Google Cloud Professional Network Engineer is reviewing this Google Cloud networking environment scenario: A company forwards every internal DNS suffix to public recursive resolvers and expects nonpublic Cloud DNS records to be returned externally. An unsafe shortcut would be: Publish sensitive internal host records into an internet public DNS zone solely to avoid configuring hybrid resolution. What should the cloud network administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Diagnose Cloud Router BGP session parameters, neighbor reachability, advertised and learned prefixes, route preferences and VPC dynamic routing mode.
- Publish sensitive internal host records into an internet public DNS zone solely to avoid configuring hybrid resolution.
- Plan inbound and outbound DNS server policies, forwarding destinations, and authorized private-zone visibility for the on-premises/cloud hybrid resolution path.
- Enable Private Google Access on the appropriate subnet and configure eligible Google API DNS and routes, choosing restricted or private VIP behavior as needed.
Explanation
Correct Answer
C:Plan inbound and outbound DNS server policies, forwarding destinations, and authorized private-zone visibility for the on-premises/cloud hybrid resolution path. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
Incorrect Answers
A:Diagnose Cloud Router BGP session parameters, neighbor reachability, advertised and learned prefixes, route preferences and VPC dynamic routing mode. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
B:Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
D:Enable Private Google Access on the appropriate subnet and configure eligible Google API DNS and routes, choosing restricted or private VIP behavior as needed. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
Question 27
A Google Cloud network infrastructure review finds: A company forwards every internal DNS suffix to public recursive resolvers and expects nonpublic Cloud DNS records to be returned externally. The team proposes: Plan inbound and outbound DNS server policies, forwarding destinations, and authorized private-zone visibility for the on-premises/cloud hybrid resolution path. Which Google Cloud networking technical principle most strongly supports the proposed response? Select ONE best answer.
- Partner Interconnect responsibilities differ by provider layer and interconnection model; customer BGP and route advertisement cannot be inferred solely from the attachment order.
- End-to-end usable packet size is limited by the smallest effective path MTU; local jumbo support does not eliminate overlay overhead.
- Premium and Standard Network Service Tiers differ in external traffic paths and eligible global networking capabilities; choosing a tier is not the same as sizing compute.
- Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
Explanation
Correct Answer
D:Demonstrable success requires: Both on-premises and cloud clients resolve approved internal names consistently without exposing private records on the public internet.
Incorrect Answers
A:Partner Interconnect responsibilities differ by provider layer and interconnection model; customer BGP and route advertisement cannot be inferred solely from the attachment order. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
B:End-to-end usable packet size is limited by the smallest effective path MTU; local jumbo support does not eliminate overlay overhead. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
C:Premium and Standard Network Service Tiers differ in external traffic paths and eligible global networking capabilities; choosing a tier is not the same as sizing compute. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
Question 28
The cloud network operations team has not approved a broad network-wide change. Available evidence indicates: A company forwards every internal DNS suffix to public recursive resolvers and expects nonpublic Cloud DNS records to be returned externally. Which evidence best tests the Google Cloud networking diagnosis before approving a disruptive change? Select ONE best answer.
- Identify producer service eligibility, consumer VPC, internal endpoint or allocated peering range, route and DNS needs, and serverless egress settings.
- Inspect query source, authoritative or forwarded zones, inbound forwarding policy, outbound targets, network authorization and resolver query logs.
- Inspect appliance instance and NIC, router appliance spoke membership, BGP adjacency, health/failover path and effective routes.
- Review on-prem DNS resolution, routed VIP or PSC endpoint, Cloud Router advertisements, firewall reachability and observed egress path.
Explanation
Correct Answer
B:Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone. Confirm afterward that: Both on-premises and cloud clients resolve approved internal names consistently without exposing private records on the public internet.
Incorrect Answers
A:Identify producer service eligibility, consumer VPC, internal endpoint or allocated peering range, route and DNS needs, and serverless egress settings. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
C:Inspect appliance instance and NIC, router appliance spoke membership, BGP adjacency, health/failover path and effective routes. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
D:Review on-prem DNS resolution, routed VIP or PSC endpoint, Cloud Router advertisements, firewall reachability and observed egress path. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
Question 29
A candidate network change has been piloted and stakeholders require a post-change acceptance check. Original problem: A company forwards every internal DNS suffix to public recursive resolvers and expects nonpublic Cloud DNS records to be returned externally. 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.
- Legitimate clients receive responses while selected attacks are denied at the required service layer with observable policy decisions.
- Harmful automated traffic is constrained without indiscriminately denying verified business integrations and accessibility tools.
- Application teams deploy to allowed subnets while network ownership and unrelated project resources remain protected.
- Both on-premises and cloud clients resolve approved internal names consistently without exposing private records on the public internet.
Explanation
Correct Answer
D:Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone. The approved implementation step was: Plan inbound and outbound DNS server policies, forwarding destinations, and authorized private-zone visibility for the on-premises/cloud hybrid resolution path.
Incorrect Answers
A:Legitimate clients receive responses while selected attacks are denied at the required service layer with observable policy decisions. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
B:Harmful automated traffic is constrained without indiscriminately denying verified business integrations and accessibility tools. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
C:Application teams deploy to allowed subnets while network ownership and unrelated project resources remain protected. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
Question 30
For an original Google Cloud Professional Cloud Network Engineer educational scenario, consider: A company forwards every internal DNS suffix to public recursive resolvers and expects nonpublic Cloud DNS records to be returned externally. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Create or maintain a supported VPC-native GKE cluster with assigned primary and secondary subnet ranges sized for nodes, Pods and Services.
- Change: Plan inbound and outbound DNS server policies, forwarding destinations, and authorized private-zone visibility for the on-premises/cloud hybrid resolution path.
- Check: Inspect hub/spoke resource type, attached VPC or tunnel/attachment, producer eligibility, effective routes and a controlled connectivity test.
- Publish sensitive internal host records into an internet public DNS zone solely to avoid configuring hybrid resolution.
- Check: Inspect query source, authoritative or forwarded zones, inbound forwarding policy, outbound targets, network authorization and resolver query logs.
Explanation
Correct Answer
B:Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone. Acceptance: Both on-premises and cloud clients resolve approved internal names consistently without exposing private records on the public internet.
E:Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone. Required intervention: Plan inbound and outbound DNS server policies, forwarding destinations, and authorized private-zone visibility for the on-premises/cloud hybrid resolution path.
Incorrect Answers
A:Change: Create or maintain a supported VPC-native GKE cluster with assigned primary and secondary subnet ranges sized for nodes, Pods and Services. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
C:Check: Inspect hub/spoke resource type, attached VPC or tunnel/attachment, producer eligibility, effective routes and a controlled connectivity test. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.
D:For this select two assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it. Cloud DNS private-zone authorization and DNS forwarding direction determine which resolver can see internal records; public lookup alone cannot expose a private zone.