Google Professional Cloud Network Engineer Practice Test 90
Question 890
For an original Google Cloud Professional Cloud Network Engineer educational scenario, consider: A private connection drops after reassigning a VLAN attachment, but engineers change VPC firewall rules without verifying tag pairing and Cloud Router adjacency. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Correlate attachment status, circuit utilization/errors, provider handoff, VLAN or pairing key and Cloud Router peer events.
- Change: Run scoped Network Intelligence Center Connectivity Tests and interpret simulated route and firewall paths with live endpoint testing where necessary.
- Delete all firewall rules when a physical Interconnect port loses signal because that is supposedly an ingress policy issue.
- Change: Compare physical or partner link state, attachment provisioning, VLAN tag and Cloud Router BGP state before changing higher-layer policy.
- Check: Compare announced routes, filter conditions, import/export status, effective spoke route tables and permit/deny reachability tests.
Explanation
Correct Answer
A:Interconnect problems may occur at port, provider, VLAN and BGP layers; the presence of a resource ID is not proof of a working data plane. Required intervention: Compare physical or partner link state, attachment provisioning, VLAN tag and Cloud Router BGP state before changing higher-layer policy.
D:Interconnect problems may occur at port, provider, VLAN and BGP layers; the presence of a resource ID is not proof of a working data plane. Evidence: Correlate attachment status, circuit utilization/errors, provider handoff, VLAN or pairing key and Cloud Router peer events.
Incorrect Answers
B:Change: Run scoped Network Intelligence Center Connectivity Tests and interpret simulated route and firewall paths with live endpoint testing where necessary. Interconnect problems may occur at port, provider, VLAN and BGP layers; the presence of a resource ID is not proof of a working data plane.
C:For this select two assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it. Interconnect problems may occur at port, provider, VLAN and BGP layers; the presence of a resource ID is not proof of a working data plane.
E:Check: Compare announced routes, filter conditions, import/export status, effective spoke route tables and permit/deny reachability tests. Interconnect problems may occur at port, provider, VLAN and BGP layers; the presence of a resource ID is not proof of a working data plane.
Question 891
A Google Cloud Professional Network Engineer is reviewing this Google Cloud networking environment scenario: An on-premises BGP peer is stuck in Active after a router swap because its neighbor ASN is incorrect, but Cloud VPN tunnel health is still green. An unsafe shortcut would be: Assume Established BGP means every possible remote prefix is automatically reachable and firewall-permitted. What should the cloud network administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Assume Established BGP means every possible remote prefix is automatically reachable and firewall-permitted.
- Configure supported NCC Private NAT and PSC route or service propagation behavior appropriate to the attached topology and CIDR ownership.
- Select supported Partner Interconnect layer 2 or layer 3 provider responsibilities and configure attachment activation and Cloud Router behavior accordingly.
- Diagnose Cloud Router BGP session parameters, neighbor reachability, advertised and learned prefixes, route preferences and VPC dynamic routing mode.
Explanation
Correct Answer
D:Diagnose Cloud Router BGP session parameters, neighbor reachability, advertised and learned prefixes, route preferences and VPC dynamic routing mode. BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
Incorrect Answers
A:BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately. 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 supported NCC Private NAT and PSC route or service propagation behavior appropriate to the attached topology and CIDR ownership. BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
C:Select supported Partner Interconnect layer 2 or layer 3 provider responsibilities and configure attachment activation and Cloud Router behavior accordingly. BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
Question 892
A Google Cloud network infrastructure review finds: An on-premises BGP peer is stuck in Active after a router swap because its neighbor ASN is incorrect, but Cloud VPN tunnel health is still green. The team proposes: Diagnose Cloud Router BGP session parameters, neighbor reachability, advertised and learned prefixes, route preferences and VPC dynamic routing mode. Which Google Cloud networking technical principle most strongly supports the proposed response? Select ONE best answer.
- 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.
- BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
- Layer 7 proxy load balancing and Layer 4 passthrough load balancing expose different frontend address, protocol, globality and HTTP routing behavior.
- NCC Private NAT addresses eligible overlapping-network connectivity while PSC propagation exposes supported services; neither automatically creates broad peer-to-peer reachability.
Explanation
Correct Answer
B:Relevant validation before approval: Inspect Cloud Router peer logs, local/remote ASN, link-local IP, MD5 or BFD settings, received routes and VPC effective next hops.
Incorrect Answers
A:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (NCC transitivity and overlapping topology pitfalls) rather than the documented Cloud Router BGP peering troubleshooting decision.
C: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 Router BGP peering troubleshooting decision.
D:NCC Private NAT addresses eligible overlapping-network connectivity while PSC propagation exposes supported services; neither automatically creates broad peer-to-peer reachability. BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
Question 893
The cloud network operations team has not approved a broad network-wide change. Available evidence indicates: An on-premises BGP peer is stuck in Active after a router swap because its neighbor ASN is incorrect, but Cloud VPN tunnel health is still green. Which evidence best tests the Google Cloud networking diagnosis before approving a disruptive change? Select ONE best answer.
- Examine drain timeouts, backend health, active connections, weighted routing or URL map revisions and client error rates during a staging cutover.
- Inspect Cloud Router peer logs, local/remote ASN, link-local IP, MD5 or BFD settings, received routes and VPC effective next hops.
- Compare subnet Flow Logs settings, firewall rule logging, source/destination tuples, action/bytes and application request timing.
- Inspect supported route-to-ILB configuration, forwarding rule, backend health, ingress/egress NICs and forward and return flow captures during failover.
Explanation
Correct Answer
B:BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
Incorrect Answers
A:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Application Load Balancer connection draining and redirects) rather than the documented Cloud Router BGP peering troubleshooting decision.
C:Compare subnet Flow Logs settings, firewall rule logging, source/destination tuples, action/bytes and application request timing. BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
D: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 Cloud Router BGP peering troubleshooting decision.
Question 894
A candidate network change has been piloted and stakeholders require a post-change acceptance check. Original problem: An on-premises BGP peer is stuck in Active after a router swap because its neighbor ASN is incorrect, but Cloud VPN tunnel health is still green. 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.
- Internal callers reach private endpoints while external callers resolve only sanctioned public endpoints.
- BGP and route selection operate as intended for authorized prefixes and no unrelated route policy is broadened.
- Approved rules remain effective while unused or problematic configuration is remediated with an auditable baseline.
- Intended workloads reach only authorized private services without requiring an unapproved public address or unrelated transit route.
Explanation
Correct Answer
B:BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately. The result must be validated using the documented site, route, application or user context.
Incorrect Answers
A:Internal callers reach private endpoints while external callers resolve only sanctioned public endpoints. BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
C:Approved rules remain effective while unused or problematic configuration is remediated with an auditable baseline. BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
D:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Managed service private connectivity selection) rather than the documented Cloud Router BGP peering troubleshooting decision.
Question 895
A production Google Cloud networking change review identifies the following problem: An on-premises BGP peer is stuck in Active after a router swap because its neighbor ASN is incorrect, but Cloud VPN tunnel health is still green. Which paired Google Cloud networking action and verification should close the review? Select ONE best answer.
- Change: Diagnose Cloud Router BGP session parameters, neighbor reachability, advertised and learned prefixes, route preferences and VPC dynamic routing mode. Verify: Inspect Cloud Router peer logs, local/remote ASN, link-local IP, MD5 or BFD settings, received routes and VPC effective next hops.
- Change: Set regional or global dynamic routing mode consistent with required subnet reachability and verify cross-region dynamic route preference and failover. Verify: Inspect VPC routing mode, region-specific dynamic tables, BGP advertisements, path priorities and packet routes during a regional link outage.
- Change: Monitor load-balancer request/latency/backend health and Cloud Armor matched-rule metrics and logs to separate application, origin and security causes. Verify: Correlate URL map/backend service, 5xx source, health-check status, Armor policy/rule IDs and representative request timestamps.
- Change: Review Cloud NAT allocation, port-utilization metrics and translation/error logs, then adjust supported address or port capacity for actual demand. Verify: Compare NAT gateway metrics, allocated versus needed ports, error logs, instance activity, source endpoints and test connection rates.
Explanation
Correct Answer
A:This pair links the appropriate network response with evidence of the underlying cloud networking issue. Applied case: An on-premises BGP peer is stuck in Active after a router swap because its neighbor ASN is incorrect, but Cloud VPN tunnel health is still green.
Incorrect Answers
B:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Regional versus global dynamic routing behavior) rather than the documented Cloud Router BGP peering troubleshooting decision.
C:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Load balancer backend and Cloud Armor monitoring) rather than the documented Cloud Router BGP peering troubleshooting decision.
D:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Cloud NAT logs and capacity monitoring) rather than the documented Cloud Router BGP peering troubleshooting decision.
Question 896
A Google Cloud Professional Network Engineer is reviewing this Google Cloud networking environment scenario: A session is Established yet the VPC cannot reach a new remote prefix because export policy and route selection were not checked. An unsafe shortcut would be: Assume Established BGP means every possible remote prefix is automatically reachable and firewall-permitted. What should the cloud network administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Extend eligible GKE Pod address capacity with additional supported secondary ranges and troubleshoot DNS through the configured cluster DNS service and optional caching.
- Design supported dual-stack subnet or endpoint addressing and appropriate IPv6 or PUPI treatment with matching routes, DNS and policy.
- Assume Established BGP means every possible remote prefix is automatically reachable and firewall-permitted.
- Diagnose Cloud Router BGP session parameters, neighbor reachability, advertised and learned prefixes, route preferences and VPC dynamic routing mode.
Explanation
Correct Answer
D:Diagnose Cloud Router BGP session parameters, neighbor reachability, advertised and learned prefixes, route preferences and VPC dynamic routing mode. BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
Incorrect Answers
A:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (GKE additional Pod ranges and DNS integration) rather than the documented Cloud Router BGP peering troubleshooting decision.
B:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Dual-stack IPv6 and PUPI address planning) rather than the documented Cloud Router BGP peering troubleshooting decision.
C:BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
Question 897
A Google Cloud network infrastructure review finds: A session is Established yet the VPC cannot reach a new remote prefix because export policy and route selection were not checked. The team proposes: Diagnose Cloud Router BGP session parameters, neighbor reachability, advertised and learned prefixes, route preferences and VPC dynamic routing mode. Which Google Cloud networking technical principle most strongly supports the proposed response? Select ONE best answer.
- BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
- Cloud Router advertisements determine what remote routers learn; having a VPC resource does not guarantee its prefix is included in every peer's outgoing BGP policy.
- Flow logs aggregate or sample flow characteristics, while Packet Mirroring supplies eligible packet copies and requires explicit source, filters and collector safeguards.
- Authoritative Cloud DNS visibility depends on zone type and public delegation or private VPC authorization; record creation alone does not preserve service reachability.
Explanation
Correct Answer
A:Relevant validation before approval: Inspect Cloud Router peer logs, local/remote ASN, link-local IP, MD5 or BFD settings, received routes and VPC effective next hops.
Incorrect Answers
B:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Custom advertised routes for on-premises connectivity) rather than the documented Cloud Router BGP peering troubleshooting decision.
C:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Packet Mirroring versus logs for packet-level diagnosis) rather than the documented Cloud Router BGP peering troubleshooting decision.
D:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Cloud DNS authoritative public and private zone management) rather than the documented Cloud Router BGP peering troubleshooting decision.
Question 898
The cloud network operations team has not approved a broad network-wide change. Available evidence indicates: A session is Established yet the VPC cannot reach a new remote prefix because export policy and route selection were not checked. Which evidence best tests the Google Cloud networking diagnosis before approving a disruptive change? Select ONE best answer.
- Specify source, destination, port and protocol; inspect traces, next hops, firewall policy and independent real traffic test.
- Examine topology resource scope, traffic metrics, direction and timestamps, then verify the selected path with routes or Connectivity Tests.
- Trace NIC attachments, route and policy-based next hops, ILB backend health, session state and bidirectional packet captures during failure.
- Inspect Cloud Router peer logs, local/remote ASN, link-local IP, MD5 or BFD settings, received routes and VPC effective next hops.
Explanation
Correct Answer
D:BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately. This check evaluates the actual network transport, access or management-lifecycle issue before a risky network-wide change.
Incorrect Answers
A:Specify source, destination, port and protocol; inspect traces, next hops, firewall policy and independent real traffic test. A session is Established yet the VPC cannot reach a new remote prefix because export policy and route selection were not checked.
B:Examine topology resource scope, traffic metrics, direction and timestamps, then verify the selected path with routes or Connectivity Tests. BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
C:Trace NIC attachments, route and policy-based next hops, ILB backend health, session state and bidirectional packet captures during failure. A session is Established yet the VPC cannot reach a new remote prefix because export policy and route selection were not checked.
Question 899
A candidate network change has been piloted and stakeholders require a post-change acceptance check. Original problem: A session is Established yet the VPC cannot reach a new remote prefix because export policy and route selection were not checked. 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.
- Production requests use the intended supported ingress footprint with measured acceptable latency and an understood tier cost.
- BGP and route selection operate as intended for authorized prefixes and no unrelated route policy is broadened.
- The team locates and fixes the true route or policy issue with auditable network evidence and no broad allow-all rule.
- Operators isolate the relevant changed network path and corroborate it with measurable forwarding evidence.
Explanation
Correct Answer
B:BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately. The approved implementation step was: Diagnose Cloud Router BGP session parameters, neighbor reachability, advertised and learned prefixes, route preferences and VPC dynamic routing mode.
Incorrect Answers
A:Production requests use the intended supported ingress footprint with measured acceptable latency and an understood tier cost. A session is Established yet the VPC cannot reach a new remote prefix because export policy and route selection were not checked.
C:The team locates and fixes the true route or policy issue with auditable network evidence and no broad allow-all rule. BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
D:Operators isolate the relevant changed network path and corroborate it with measurable forwarding evidence. BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
Question 900
For an original Google Cloud Professional Cloud Network Engineer educational scenario, consider: A session is Established yet the VPC cannot reach a new remote prefix because export policy and route selection were not checked. Select THREE compatible elements: a proper correction, a targeted diagnostic and an acceptance result.
- Check: Inspect internet NEG endpoints, backend service, origin host header, TLS trust, CDN status and a representative cache-hit versus origin-fetch test.
- Change: Define supported tag or service-account-based firewall targeting with the appropriate policy type and verify workload identity and tag bindings.
- Change: Diagnose Cloud Router BGP session parameters, neighbor reachability, advertised and learned prefixes, route preferences and VPC dynamic routing mode.
- Result: BGP and route selection operate as intended for authorized prefixes and no unrelated route policy is broadened.
- Check: Inspect Cloud Router peer logs, local/remote ASN, link-local IP, MD5 or BFD settings, received routes and VPC effective next hops.
- Result: Loss of redundancy is detected before an outage and failover restores approved prefixes within documented objectives.
Explanation
Correct Answer
C:BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately. Evidence: Inspect Cloud Router peer logs, local/remote ASN, link-local IP, MD5 or BFD settings, received routes and VPC effective next hops.
D:BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately. Required intervention: Diagnose Cloud Router BGP session parameters, neighbor reachability, advertised and learned prefixes, route preferences and VPC dynamic routing mode.
E:BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately. Inspect Cloud Router peer logs, local/remote ASN, link-local IP, MD5 or BFD settings, received routes and VPC effective next hops.
Incorrect Answers
A:Check: Inspect internet NEG endpoints, backend service, origin host header, TLS trust, CDN status and a representative cache-hit versus origin-fetch test. BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.
B:Change: Define supported tag or service-account-based firewall targeting with the appropriate policy type and verify workload identity and tag bindings. A session is Established yet the VPC cannot reach a new remote prefix because export policy and route selection were not checked.
F:Result: Loss of redundancy is detected before an outage and failover restores approved prefixes within documented objectives. BGP can be down with an up IPsec path or up without an intended prefix; peer status and effective route acceptance must be checked separately.