Google Professional Cloud Network Engineer Practice Test 78
Question 770
For an original Google Cloud Professional Cloud Network Engineer educational scenario, consider: A new Interconnect VLAN attachment is brought online but excluded from the planned spoke group and route filters, causing only one region to see remote site prefixes. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Configure supported Shared VPC GKE host/service attachment and minimum required subnet and service-agent permissions for cluster resources.
- Check: Compare provider handoff model, attachment pairing key and operational status, VLAN configuration, Cloud Router sessions and actual imported prefixes.
- Check: Inspect spoke resource references, hub attachment state, BGP reachability, propagated CIDRs and cross-spoke Connectivity Tests.
- Change: Attach supported HA VPN tunnels or Interconnect VLAN resources as NCC hybrid spokes and verify route exchange and segmentation.
- Assume every Cloud VPN tunnel automatically appears as a fully connected NCC hybrid spoke whenever a hub is created.
Explanation
Correct Answer
C:NCC hybrid spokes connect eligible VPN or VLAN transports to hub routing relationships; tunnel existence alone does not create NCC membership. Required intervention: Attach supported HA VPN tunnels or Interconnect VLAN resources as NCC hybrid spokes and verify route exchange and segmentation.
D:NCC hybrid spokes connect eligible VPN or VLAN transports to hub routing relationships; tunnel existence alone does not create NCC membership. Evidence: Inspect spoke resource references, hub attachment state, BGP reachability, propagated CIDRs and cross-spoke Connectivity Tests.
Incorrect Answers
A:Change: Configure supported Shared VPC GKE host/service attachment and minimum required subnet and service-agent permissions for cluster resources. NCC hybrid spokes connect eligible VPN or VLAN transports to hub routing relationships; tunnel existence alone does not create NCC membership.
B:Compare provider handoff model, attachment pairing key and operational status, VLAN configuration, Cloud Router sessions and actual imported prefixes. This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Partner Interconnect layer 2 versus layer 3 operational scope) rather than the documented NCC hybrid spokes on Cloud VPN and VLAN decision. The relevant Google Cloud networking principle under the April 2026 guide is: NCC hybrid spokes connect eligible VPN or VLAN transports to hub routing relationships; tunnel existence alone does not create NCC membership. The relevant action is: Attach supported HA VPN tunnels or Interconnect VLAN resources as NCC hybrid spokes and verify route exchange and segmentation. Discriminating evidence: Inspect spoke resource references, hub attachment state, BGP reachability, propagated CIDRs and cross-spoke Connectivity Tests.
E:For this select two assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it. NCC hybrid spokes connect eligible VPN or VLAN transports to hub routing relationships; tunnel existence alone does not create NCC membership.
Question 771
A Google Cloud Professional Network Engineer is reviewing this Google Cloud networking environment scenario: Two offices each connect with separate Interconnect attachments but cannot reach one another because the hub's site-to-site data transfer behavior was not configured as supported. An unsafe shortcut would be: Treat every NCC hub as a universal internet-scale router that exchanges all customer prefixes automatically. What should the cloud network administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Configure eligible Cross-Cloud Interconnect connectivity and VLAN attachments with both clouds' route, security and redundancy requirements explicitly integrated.
- Configure supported NCC site-to-site data transfer with deliberate eligible hybrid spokes and route/prefix propagation limits.
- Treat every NCC hub as a universal internet-scale router that exchanges all customer prefixes automatically.
- 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
B:Configure supported NCC site-to-site data transfer with deliberate eligible hybrid spokes and route/prefix propagation limits. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
Incorrect Answers
A:NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default. Configure supported NCC site-to-site data transfer with deliberate eligible hybrid spokes and route/prefix propagation limits.
C:NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default. For this best change assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it.
D:NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
Question 772
A Google Cloud network infrastructure review finds: Two offices each connect with separate Interconnect attachments but cannot reach one another because the hub's site-to-site data transfer behavior was not configured as supported. The team proposes: Configure supported NCC site-to-site data transfer with deliberate eligible hybrid spokes and route/prefix propagation limits. Which Google Cloud networking technical principle most strongly supports the proposed response? Select ONE best answer.
- Bot and threat-intelligence signals provide risk evidence but not a universal binary label for all clients; policy priority and business exceptions still matter.
- A supported internal load-balancer next hop enables health-aware appliance placement but does not create firewalls, repair return paths or guarantee stateful session survival.
- Partner Interconnect responsibilities differ by provider layer and interconnection model; customer BGP and route advertisement cannot be inferred solely from the attachment order.
- NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
Explanation
Correct Answer
D:Demonstrable success requires: Allowed sites exchange only approved prefixes with bidirectional reachability and no unintended third-party transit. This principle explains the proposed network response, which is: Configure supported NCC site-to-site data transfer with deliberate eligible hybrid spokes and route/prefix propagation limits.
Incorrect Answers
A:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Cloud Armor bot management and threat intelligence) rather than the documented NCC site-to-site data transfer and transit decision.
B: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 site-to-site data transfer and transit decision.
C:Partner Interconnect responsibilities differ by provider layer and interconnection model; customer BGP and route advertisement cannot be inferred solely from the attachment order. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
Question 773
The cloud network operations team has not approved a broad network-wide change. Available evidence indicates: Two offices each connect with separate Interconnect attachments but cannot reach one another because the hub's site-to-site data transfer behavior was not configured as supported. Which evidence best tests the Google Cloud networking diagnosis before approving a disruptive change? Select ONE best answer.
- Review backend service mode, affinity settings, capacity limits, health changes and observed client-to-backend distribution during load.
- Review Cloud Router BGP diagnostics, peer ASN and interface addresses, MD5 authentication where supported, session state and advertised prefixes.
- Compare site-to-site setting, hybrid spoke attachment, both peer route tables, route filters and a permit/deny packet test.
- Capture link/tunnel health, BGP advertisements, effective routes, firewall admission and end-to-end app flows before and after fault injection.
Explanation
Correct Answer
C:NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
Incorrect Answers
A:Review backend service mode, affinity settings, capacity limits, health changes and observed client-to-backend distribution during load. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
B:Review Cloud Router BGP diagnostics, peer ASN and interface addresses, MD5 authentication where supported, session state and advertised prefixes. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
D:Capture link/tunnel health, BGP advertisements, effective routes, firewall admission and end-to-end app flows before and after fault injection. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
Question 774
A candidate network change has been piloted and stakeholders require a post-change acceptance check. Original problem: Two offices each connect with separate Interconnect attachments but cannot reach one another because the hub's site-to-site data transfer behavior was not configured as supported. 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.
- Approved destinations are learned remotely while unrelated or protected subnets are not advertised.
- Allowed sites exchange only approved prefixes with bidirectional reachability and no unintended third-party transit.
- Approved remote-origin content is served through the designed Google Cloud frontend and caches safely without backend address confusion.
- Intended eligible regional or cross-region clients reach healthy backends without broadening access unnecessarily.
Explanation
Correct Answer
B:NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default. The approved implementation step was: Configure supported NCC site-to-site data transfer with deliberate eligible hybrid spokes and route/prefix propagation limits.
Incorrect Answers
A:Approved destinations are learned remotely while unrelated or protected subnets are not advertised. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
C:Approved remote-origin content is served through the designed Google Cloud frontend and caches safely without backend address confusion. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
D:Intended eligible regional or cross-region clients reach healthy backends without broadening access unnecessarily. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
Question 775
A production Google Cloud networking change review identifies the following problem: Two offices each connect with separate Interconnect attachments but cannot reach one another because the hub's site-to-site data transfer behavior was not configured as supported. Which paired Google Cloud networking action and verification should close the review? Select ONE best answer.
- Change: Configure supported DNS peering or cross-project binding and inbound/outbound forwarding with explicit zone visibility and bidirectional resolver paths. Verify: Inspect private-zone authorizations, DNS server policies, forwarding targets, return paths and query logs in each source VPC or premises.
- 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.
- Change: Configure supported NCC site-to-site data transfer with deliberate eligible hybrid spokes and route/prefix propagation limits. Verify: Compare site-to-site setting, hybrid spoke attachment, both peer route tables, route filters and a permit/deny packet test.
- Change: Configure supported Cloud Router BGP peer ASN, compatible link-local session addresses and authentication settings with the remote router. Verify: Review Cloud Router BGP diagnostics, peer ASN and interface addresses, MD5 authentication where supported, session state and advertised prefixes.
Explanation
Correct Answer
C:This pair links the appropriate network response with evidence of the underlying cloud networking issue. Applied case: Two offices each connect with separate Interconnect attachments but cannot reach one another because the hub's site-to-site data transfer behavior was not configured as supported.
Incorrect Answers
A:Change: Configure supported DNS peering or cross-project binding and inbound/outbound forwarding with explicit zone visibility and bidirectional resolver paths. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
B:Change: Correlate the full hybrid transport, BGP and VPC forwarding path and stage failure tests with explicit route preference and recovery criteria. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
D:Change: Configure supported Cloud Router BGP peer ASN, compatible link-local session addresses and authentication settings with the remote router.
Question 776
A Google Cloud Professional Network Engineer is reviewing this Google Cloud networking environment scenario: A corporate site is connected to an NCC hub and security believes it can transparently transit between all unrelated partner networks by default. An unsafe shortcut would be: Treat every NCC hub as a universal internet-scale router that exchanges all customer prefixes automatically. What should the cloud network administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Configure supported NCC site-to-site data transfer with deliberate eligible hybrid spokes and route/prefix propagation limits.
- Configure and log eligible ingress or egress VPC firewall rules with precise action, priority, protocol, target and source/destination selectors.
- Treat every NCC hub as a universal internet-scale router that exchanges all customer prefixes automatically.
- 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 supported NCC site-to-site data transfer with deliberate eligible hybrid spokes and route/prefix propagation limits. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
Incorrect Answers
B:Configure and log eligible ingress or egress VPC firewall rules with precise action, priority, protocol, target and source/destination selectors. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
C:NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default. Use this instead: Configure supported NCC site-to-site data transfer with deliberate eligible hybrid spokes and route/prefix propagation limits.
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 NCC site-to-site data transfer and transit decision.
Question 777
A Google Cloud network infrastructure review finds: A corporate site is connected to an NCC hub and security believes it can transparently transit between all unrelated partner networks by default. The team proposes: Configure supported NCC site-to-site data transfer with deliberate eligible hybrid spokes and route/prefix propagation limits. Which Google Cloud networking technical principle most strongly supports the proposed response? Select ONE best answer.
- Google Cloud VPC networks are global constructs while subnets and many forwarding resources are regional; resource location remains operationally significant.
- NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
- Layer-7 inspection requires eligible tier, security profiles, endpoints and effective policy binding; basic allow/deny firewalls inspect different properties.
- NCC hybrid spokes connect eligible VPN or VLAN transports to hub routing relationships; tunnel existence alone does not create NCC membership.
Explanation
Correct Answer
B:Demonstrable success requires: Allowed sites exchange only approved prefixes with bidirectional reachability and no unintended third-party transit.
Incorrect Answers
A:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Global VPC versus regional resource locality) rather than the documented NCC site-to-site data transfer and transit decision.
C:Layer-7 inspection requires eligible tier, security profiles, endpoints and effective policy binding; basic allow/deny firewalls inspect different properties. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
D:NCC hybrid spokes connect eligible VPN or VLAN transports to hub routing relationships; tunnel existence alone does not create NCC membership. This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (NCC hybrid spokes on Cloud VPN and VLAN) rather than the documented NCC site-to-site data transfer and transit decision. The relevant Google Cloud networking principle under the April 2026 guide is: NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default. The relevant action is: Configure supported NCC site-to-site data transfer with deliberate eligible hybrid spokes and route/prefix propagation limits. Discriminating evidence: Compare site-to-site setting, hybrid spoke attachment, both peer route tables, route filters and a permit/deny packet test.
Question 778
The cloud network operations team has not approved a broad network-wide change. Available evidence indicates: A corporate site is connected to an NCC hub and security believes it can transparently transit between all unrelated partner networks by default. Which evidence best tests the Google Cloud networking diagnosis before approving a disruptive change? Select ONE best answer.
- Check client proxy settings or routing, web proxy policy match, certificate behavior, blocked and allowed destinations and request audit logs.
- Inspect registrar DS, published DNSKEY, RRSIG validity, authoritative answers and recursive validation tests.
- Inspect cluster project, host subnet reference, GKE service agent roles, secondary ranges and control-plane or node provisioning errors.
- Compare site-to-site setting, hybrid spoke attachment, both peer route tables, route filters and a permit/deny packet test.
Explanation
Correct Answer
D:NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
Incorrect Answers
A:Check client proxy settings or routing, web proxy policy match, certificate behavior, blocked and allowed destinations and request audit logs. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
B:Inspect registrar DS, published DNSKEY, RRSIG validity, authoritative answers and recursive validation tests. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
C:Inspect cluster project, host subnet reference, GKE service agent roles, secondary ranges and control-plane or node provisioning errors. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
Question 779
A candidate network change has been piloted and stakeholders require a post-change acceptance check. Original problem: A corporate site is connected to an NCC hub and security believes it can transparently transit between all unrelated partner networks 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.
- Approved learned destinations use the intended supported next hop and backup routes converge without route oscillation or leakage.
- Allowed sites exchange only approved prefixes with bidirectional reachability and no unintended third-party transit.
- Production requests use the intended supported ingress footprint with measured acceptable latency and an understood tier cost.
- Healthy instances are admitted to serving and unhealthy ones are excluded without exposing broad unsolicited access.
Explanation
Correct Answer
B:NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default. The result must be validated using the documented site, route, application or user context.
Incorrect Answers
A:Approved learned destinations use the intended supported next hop and backup routes converge without route oscillation or leakage. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
C:Production requests use the intended supported ingress footprint with measured acceptable latency and an understood tier cost. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
D:Healthy instances are admitted to serving and unhealthy ones are excluded without exposing broad unsolicited access. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
Question 780
For an original Google Cloud Professional Cloud Network Engineer educational scenario, consider: A corporate site is connected to an NCC hub and security believes it can transparently transit between all unrelated partner networks by default. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Compare site-to-site setting, hybrid spoke attachment, both peer route tables, route filters and a permit/deny packet test.
- Change: Configure supported NCC site-to-site data transfer with deliberate eligible hybrid spokes and route/prefix propagation limits.
- Treat every NCC hub as a universal internet-scale router that exchanges all customer prefixes automatically.
- Check: Compare provider handoff model, attachment pairing key and operational status, VLAN configuration, Cloud Router sessions and actual imported prefixes.
- Change: Select Dedicated Interconnect, Partner Interconnect or HA VPN based on bandwidth, carrier access, encryption, lead time and resilience.
Explanation
Correct Answer
A:NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default. Required intervention: Configure supported NCC site-to-site data transfer with deliberate eligible hybrid spokes and route/prefix propagation limits.
B:NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default. Acceptance: Allowed sites exchange only approved prefixes with bidirectional reachability and no unintended third-party transit.
Incorrect Answers
C:For this select two assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
D:Check: Compare provider handoff model, attachment pairing key and operational status, VLAN configuration, Cloud Router sessions and actual imported prefixes. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.
E:Change: Select Dedicated Interconnect, Partner Interconnect or HA VPN based on bandwidth, carrier access, encryption, lead time and resilience. NCC can connect supported hybrid sites through explicitly configured hub behavior, but it does not authorize or create unbounded on-premises transitivity by default.