Google Professional Cloud Network Engineer Practice Test 80
Question 790
For an original Google Cloud Professional Cloud Network Engineer educational scenario, consider: An appliance fleet must survive maintenance, but all NCC connectivity depends on one VM's NIC and the team claims that hub objects provide appliance redundancy. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Select mutually supported VPC and hybrid path MTUs and evaluate TCP MSS/PMTUD handling to accommodate each encapsulation layer.
- Check: Inspect appliance instance and NIC, router appliance spoke membership, BGP adjacency, health/failover path and effective routes.
- Change: Design supported NCC router appliance instances with corresponding Cloud Router and attachment requirements, including failover and correct route advertisement.
- Check: Inspect target service, source and destination projects, relevant IAM, perimeter violation audit details and ingress or egress policy evaluation.
- Create a router appliance spoke and assume NCC will automatically configure the VM's BGP daemon and all routes.
Explanation
Correct Answer
B:Router appliances provide a managed integration for self-operated routing functions but do not automatically make the underlying VMs highly available or assign BGP policy. Inspect appliance instance and NIC, router appliance spoke membership, BGP adjacency, health/failover path and effective routes.
C:Router appliances provide a managed integration for self-operated routing functions but do not automatically make the underlying VMs highly available or assign BGP policy. Evidence: Inspect appliance instance and NIC, router appliance spoke membership, BGP adjacency, health/failover path and effective routes.
Incorrect Answers
A:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (VPC MTU and encapsulation overhead planning) rather than the documented NCC router appliance deployment and route handling decision.
D:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (VPC Service Controls ingress/egress boundary) rather than the documented NCC router appliance deployment and route handling decision.
E:For this select two assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it. Router appliances provide a managed integration for self-operated routing functions but do not automatically make the underlying VMs highly available or assign BGP policy.
Question 791
A Google Cloud Professional Network Engineer is reviewing this Google Cloud networking environment scenario: A design connects a VPC through Peering to a second VPC, then attaches the second as NCC spoke expecting the first to inherit all NCC hybrid routes by default. An unsafe shortcut would be: Assume adding any two connectivity edges automatically makes every attached VPC and on-premises subnet fully transitive. What should the cloud network administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Map actual NCC and VPC route propagation and nontransitive boundaries; use supported spokes or Private NAT and appropriate filters to meet required connectivity.
- Attach the service project correctly and assign supported shared-subnet usage roles to deployment identities while maintaining host network administration scope.
- Configure eligible nonoverlapping VPC Network Peering and supported custom route import/export behavior, checking route uniqueness and both network sides.
- Assume adding any two connectivity edges automatically makes every attached VPC and on-premises subnet fully transitive.
Explanation
Correct Answer
A:Map actual NCC and VPC route propagation and nontransitive boundaries; use supported spokes or Private NAT and appropriate filters to meet required connectivity. VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
Incorrect Answers
B:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Shared VPC host and service project attachment) rather than the documented NCC transitivity and overlapping topology pitfalls decision.
C:Configure eligible nonoverlapping VPC Network Peering and supported custom route import/export behavior, checking route uniqueness and both network sides. VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
D:VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path. For this best change assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it.
Question 792
A Google Cloud network infrastructure review finds: A design connects a VPC through Peering to a second VPC, then attaches the second as NCC spoke expecting the first to inherit all NCC hybrid routes by default. The team proposes: Map actual NCC and VPC route propagation and nontransitive boundaries; use supported spokes or Private NAT and appropriate filters to meet required connectivity. Which Google Cloud networking technical principle most strongly supports the proposed response? Select ONE best answer.
- VPN tunnel establishment, redundant tunnel health and routing exchange are distinct observable conditions; any one green status is insufficient for service readiness.
- Hybrid resolution depends on the direction of queries and network reachability to forwarding targets, not solely on matching zone suffixes.
- Cross-Cloud Interconnect transports connectivity between cloud providers but still requires configured routing peers, network security and suitable failure-domain diversity on both ends.
- VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
Explanation
Correct Answer
D:Demonstrable success requires: Authorized network pairs communicate without relying on unsupported transitivity or ambiguous overlapping route advertisements.
Incorrect Answers
A:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Cloud VPN tunnel monitoring and availability) rather than the documented NCC transitivity and overlapping topology pitfalls decision.
B:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Cloud DNS forwarding to on-premises resolvers) rather than the documented NCC transitivity and overlapping topology pitfalls decision.
C:Cross-Cloud Interconnect transports connectivity between cloud providers but still requires configured routing peers, network security and suitable failure-domain diversity on both ends. VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
Question 793
The cloud network operations team has not approved a broad network-wide change. Available evidence indicates: A design connects a VPC through Peering to a second VPC, then attaches the second as NCC spoke expecting the first to inherit all NCC hybrid routes by default. Which evidence best tests the Google Cloud networking diagnosis before approving a disruptive change? Select ONE best answer.
- Inspect Cloud Router peer logs, local/remote ASN, link-local IP, MD5 or BFD settings, received routes and VPC effective next hops.
- Build a prefix-level topology showing spoke types, peer boundaries, route filters, overlapping prefixes and bidirectional packet tests.
- Inspect query source, authoritative or forwarded zones, inbound forwarding policy, outbound targets, network authorization and resolver query logs.
- Inspect circuit status, attachment state, BGP peers, VLAN tags, regional placement, learned routes and single-link failure tests.
Explanation
Correct Answer
B:VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
Incorrect Answers
A:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Cloud Router BGP peering troubleshooting) rather than the documented NCC transitivity and overlapping topology pitfalls decision.
C:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Hybrid Cloud DNS topology planning) rather than the documented NCC transitivity and overlapping topology pitfalls decision.
D:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Dedicated Interconnect VLAN attachment design) rather than the documented NCC transitivity and overlapping topology pitfalls decision.
Question 794
A candidate network change has been piloted and stakeholders require a post-change acceptance check. Original problem: A design connects a VPC through Peering to a second VPC, then attaches the second as NCC spoke expecting the first to inherit all NCC hybrid routes by default. 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.
- Authorized network pairs communicate without relying on unsupported transitivity or ambiguous overlapping route advertisements.
- The deployed hybrid network satisfies its intended documented availability design and survives tested loss of an eligible component.
- Intended workloads communicate privately across supported attachments and fail over without exposing unrelated cloud prefixes.
- The new approved content is served and expected cache entries are refreshed without unnecessarily purging all unrelated assets.
Explanation
Correct Answer
A:VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path. The result must be validated using the documented site, route, application or user context.
Incorrect Answers
B:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Interconnect service availability architecture 99.9 versus 99.99) rather than the documented NCC transitivity and overlapping topology pitfalls decision.
C:Intended workloads communicate privately across supported attachments and fail over without exposing unrelated cloud prefixes. VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
D:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Cloud CDN invalidation and stale content control) rather than the documented NCC transitivity and overlapping topology pitfalls decision.
Question 795
A production Google Cloud networking change review identifies the following problem: A design connects a VPC through Peering to a second VPC, then attaches the second as NCC spoke expecting the first to inherit all NCC hybrid routes by default. Which paired Google Cloud networking action and verification should close the review? Select ONE best answer.
- Change: Apply appropriate preconfigured Google Cloud Armor WAF expressions and tune compatible sensitivity, exclusions or preview before enforcing malicious request classes. Verify: Review attack request samples, matched WAF rule IDs, preview logs, legitimate controls and measured block rates.
- Change: Design supported NCC router appliance instances with corresponding Cloud Router and attachment requirements, including failover and correct route advertisement. Verify: Inspect appliance instance and NIC, router appliance spoke membership, BGP adjacency, health/failover path and effective routes.
- Change: Configure supported Shared VPC GKE host/service attachment and minimum required subnet and service-agent permissions for cluster resources. Verify: Inspect cluster project, host subnet reference, GKE service agent roles, secondary ranges and control-plane or node provisioning errors.
- Change: Map actual NCC and VPC route propagation and nontransitive boundaries; use supported spokes or Private NAT and appropriate filters to meet required connectivity. Verify: Build a prefix-level topology showing spoke types, peer boundaries, route filters, overlapping prefixes and bidirectional packet tests.
Explanation
Correct Answer
D:This pair links the appropriate network response with evidence of the underlying cloud networking issue. Applied case: A design connects a VPC through Peering to a second VPC, then attaches the second as NCC spoke expecting the first to inherit all NCC hybrid routes by default.
Incorrect Answers
A:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Cloud Armor WAF preconfigured expression rule testing) rather than the documented NCC transitivity and overlapping topology pitfalls decision.
B:Change: Design supported NCC router appliance instances with corresponding Cloud Router and attachment requirements, including failover and correct route advertisement. VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
C:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (GKE in Shared VPC service project) rather than the documented NCC transitivity and overlapping topology pitfalls decision.
Question 796
A Google Cloud Professional Network Engineer is reviewing this Google Cloud networking environment scenario: A provider advertises overlapping branch prefixes through multiple NCC hybrid spokes, leaving traffic selecting unexpected routes despite both links showing healthy. An unsafe shortcut would be: Assume adding any two connectivity edges automatically makes every attached VPC and on-premises subnet fully transitive. What should the cloud network administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Configure supported Cloud NAT manual external address selection where stable egress is required and appropriate static/dynamic port allocation for expected client concurrency.
- Assume adding any two connectivity edges automatically makes every attached VPC and on-premises subnet fully transitive.
- Route applicable inspected traffic to a supported internal passthrough load balancer next hop with healthy appliance backends and validated symmetric flow behavior.
- Map actual NCC and VPC route propagation and nontransitive boundaries; use supported spokes or Private NAT and appropriate filters to meet required connectivity.
Explanation
Correct Answer
D:Map actual NCC and VPC route propagation and nontransitive boundaries; use supported spokes or Private NAT and appropriate filters to meet required connectivity. VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
Incorrect Answers
A:Configure supported Cloud NAT manual external address selection where stable egress is required and appropriate static/dynamic port allocation for expected client concurrency. VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
B:VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
C:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Internal load balancer as appliance next hop) rather than the documented NCC transitivity and overlapping topology pitfalls decision.
Question 797
A Google Cloud network infrastructure review finds: A provider advertises overlapping branch prefixes through multiple NCC hybrid spokes, leaving traffic selecting unexpected routes despite both links showing healthy. The team proposes: Map actual NCC and VPC route propagation and nontransitive boundaries; use supported spokes or Private NAT and appropriate filters to meet required connectivity. Which Google Cloud networking technical principle most strongly supports the proposed response? Select ONE best answer.
- A load balancer's health and traffic disposition can differ from VM uptime; Cloud Armor decisions require separate policy-level evidence.
- Router appliances provide a managed integration for self-operated routing functions but do not automatically make the underlying VMs highly available or assign BGP policy.
- VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
- Cloud Router's effective imported routes and VPC best-path mode influence forwarding; advertisements and best-path calculations are not guaranteed to match a naive shortest-AS-path guess.
Explanation
Correct Answer
C:Demonstrable success requires: Authorized network pairs communicate without relying on unsupported transitivity or ambiguous overlapping route advertisements.
Incorrect Answers
A:A load balancer's health and traffic disposition can differ from VM uptime; Cloud Armor decisions require separate policy-level evidence. A provider advertises overlapping branch prefixes through multiple NCC hybrid spokes, leaving traffic selecting unexpected routes despite both links showing healthy.
B:Router appliances provide a managed integration for self-operated routing functions but do not automatically make the underlying VMs highly available or assign BGP policy. VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
D:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Custom learned routes and BGP best path control) rather than the documented NCC transitivity and overlapping topology pitfalls decision.
Question 798
The cloud network operations team has not approved a broad network-wide change. Available evidence indicates: A provider advertises overlapping branch prefixes through multiple NCC hybrid spokes, leaving traffic selecting unexpected routes despite both links showing healthy. Which evidence best tests the Google Cloud networking diagnosis before approving a disruptive change? Select ONE best answer.
- Inspect spoke types, hub topology, route propagation, filters, effective reachability, and intended inspection-path evidence.
- Compare hub topology, spoke group assignments, actual route exchange and effective paths for allowed versus denied destinations.
- Build a prefix-level topology showing spoke types, peer boundaries, route filters, overlapping prefixes and bidirectional packet tests.
- Review provider-side attachment state, BGP sessions, prefix filters, capacity, site diversity and controlled one-link-down traffic tests.
Explanation
Correct Answer
C:VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path. Confirm afterward that: Authorized network pairs communicate without relying on unsupported transitivity or ambiguous overlapping route advertisements.
Incorrect Answers
A:Inspect spoke types, hub topology, route propagation, filters, effective reachability, and intended inspection-path evidence. VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
B:Compare hub topology, spoke group assignments, actual route exchange and effective paths for allowed versus denied destinations. A provider advertises overlapping branch prefixes through multiple NCC hybrid spokes, leaving traffic selecting unexpected routes despite both links showing healthy.
D:Review provider-side attachment state, BGP sessions, prefix filters, capacity, site diversity and controlled one-link-down traffic tests. VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
Question 799
A candidate network change has been piloted and stakeholders require a post-change acceptance check. Original problem: A provider advertises overlapping branch prefixes through multiple NCC hybrid spokes, leaving traffic selecting unexpected routes despite both links showing healthy. 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.
- Private instances retain stable authorized egress and sufficient port capacity under load without public addresses per VM.
- Legacy peers connect with compatible selectors during transition and upgraded paths meet documented recovery expectations.
- Authorized network pairs communicate without relying on unsupported transitivity or ambiguous overlapping route advertisements.
- Public representations cache efficiently while personalized responses cannot be served across user boundaries.
Explanation
Correct Answer
C:VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path. The approved implementation step was: Map actual NCC and VPC route propagation and nontransitive boundaries; use supported spokes or Private NAT and appropriate filters to meet required connectivity.
Incorrect Answers
A:Private instances retain stable authorized egress and sufficient port capacity under load without public addresses per VM. VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
B:Legacy peers connect with compatible selectors during transition and upgraded paths meet documented recovery expectations. A provider advertises overlapping branch prefixes through multiple NCC hybrid spokes, leaving traffic selecting unexpected routes despite both links showing healthy.
D:Public representations cache efficiently while personalized responses cannot be served across user boundaries. VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
Question 800
For an original Google Cloud Professional Cloud Network Engineer educational scenario, consider: A provider advertises overlapping branch prefixes through multiple NCC hybrid spokes, leaving traffic selecting unexpected routes despite both links showing healthy. Select THREE compatible elements: a proper correction, a targeted diagnostic and an acceptance result.
- Result: Authorized network pairs communicate without relying on unsupported transitivity or ambiguous overlapping route advertisements.
- Check: Audit allocated primary, secondary, hybrid, producer and translated CIDRs; test route resolution and NAT mapping from both sides.
- Result: Unhealthy peers are detected within the planned interval and alternative paths receive traffic without flapping healthy links.
- Change: Configure custom Cloud Router advertised routes and suitable route scope with precise prefixes and tested peer reception.
- 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: Build a prefix-level topology showing spoke types, peer boundaries, route filters, overlapping prefixes and bidirectional packet tests.
Explanation
Correct Answer
A:VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path. Required intervention: Map actual NCC and VPC route propagation and nontransitive boundaries; use supported spokes or Private NAT and appropriate filters to meet required connectivity.
E:VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path. Acceptance: Authorized network pairs communicate without relying on unsupported transitivity or ambiguous overlapping route advertisements.
F:VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path. Build a prefix-level topology showing spoke types, peer boundaries, route filters, overlapping prefixes and bidirectional packet tests.
Incorrect Answers
B:Check: Audit allocated primary, secondary, hybrid, producer and translated CIDRs; test route resolution and NAT mapping from both sides. VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
C:Result: Unhealthy peers are detected within the planned interval and alternative paths receive traffic without flapping healthy links. VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.
D:Change: Configure custom Cloud Router advertised routes and suitable route scope with precise prefixes and tested peer reception. VPC Peering, NCC hub topology and BGP route exchange have separate transit and CIDR rules; healthy links do not imply every graph edge is a routing path.