Google Professional Cloud Network Engineer Practice Test 39
Question 380
For an original Google Cloud Professional Cloud Network Engineer educational scenario, consider: A newly configured NCC route filter drops one valid branch prefix because its CIDR rule is too narrow, although tunnel health is normal. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Configure NCC supported IP/CIDR range filters and route controls to publish only intended prefixes, then validate source and destination route tables.
- Check: Compare announced routes, filter conditions, import/export status, effective spoke route tables and permit/deny reachability tests.
- Use allow-all route filters for every spoke because BGP encryption supposedly prevents cross-tenant routing leaks.
- Check: Review policy route priority, match criteria, target source or destination, next-hop availability, and representative permitted and non-permitted flows.
- Change: Choose VPC Network Peering for supported nontransitive VPC connectivity, or PSC/service-centric access or NCC for the required connectivity model.
Explanation
Correct Answer
A:NCC connectivity control depends on route acceptance and propagation scope; healthy tunnels cannot compensate for incorrect range filters. Evidence: Compare announced routes, filter conditions, import/export status, effective spoke route tables and permit/deny reachability tests.
B:NCC connectivity control depends on route acceptance and propagation scope; healthy tunnels cannot compensate for incorrect range filters. Required intervention: Configure NCC supported IP/CIDR range filters and route controls to publish only intended prefixes, then validate source and destination route tables.
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 connectivity control depends on route acceptance and propagation scope; healthy tunnels cannot compensate for incorrect range filters.
D:Check: Review policy route priority, match criteria, target source or destination, next-hop availability, and representative permitted and non-permitted flows. NCC connectivity control depends on route acceptance and propagation scope; healthy tunnels cannot compensate for incorrect range filters.
E:Change: Choose VPC Network Peering for supported nontransitive VPC connectivity, or PSC/service-centric access or NCC for the required connectivity model. NCC connectivity control depends on route acceptance and propagation scope; healthy tunnels cannot compensate for incorrect range filters.
Question 381
A Google Cloud Professional Network Engineer is reviewing this Google Cloud networking environment scenario: Two correctly attached NCC spokes remain disconnected for a required prefix, but engineers only check that the hub object exists and never review route exchange. An unsafe shortcut would be: Recreate all NCC resources whenever a spoke route disappears, ignoring the effective route advertisement and filter evidence. What should the cloud network administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Diagnose NCC spoke health, eligibility, connectivity and route propagation using hub metrics, logs and scoped Connectivity Tests before correction.
- Use supported Packet Mirroring to a controlled collector for necessary packet-level evidence, alongside VPC Flow Logs and firewall logs for broader metadata.
- Configure supported Shared VPC GKE host/service attachment and minimum required subnet and service-agent permissions for cluster resources.
- Recreate all NCC resources whenever a spoke route disappears, ignoring the effective route advertisement and filter evidence.
Explanation
Correct Answer
A:Diagnose NCC spoke health, eligibility, connectivity and route propagation using hub metrics, logs and scoped Connectivity Tests before correction. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
Incorrect Answers
B:Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
C:Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path. Diagnose NCC spoke health, eligibility, connectivity and route propagation using hub metrics, logs and scoped Connectivity Tests before correction.
D:Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application 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 382
A Google Cloud network infrastructure review finds: Two correctly attached NCC spokes remain disconnected for a required prefix, but engineers only check that the hub object exists and never review route exchange. The team proposes: Diagnose NCC spoke health, eligibility, connectivity and route propagation using hub metrics, logs and scoped Connectivity Tests before correction. Which Google Cloud networking technical principle most strongly supports the proposed response? Select ONE best answer.
- Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
- Hybrid access products have different physical/partner dependencies, performance envelopes and encryption behavior; the correct architecture depends on workload constraints.
- Pod CIDR growth and cluster DNS are distinct GKE networking functions; correct secondary allocation and DNS topology must be validated separately.
- NCC spoke types represent distinct attached resource models, and their propagation and service semantics differ; labels alone do not change a resource's type.
Explanation
Correct Answer
A:Demonstrable success requires: A clearly identified misconfiguration is corrected and approved paths work without rebuilding healthy hub components.
Incorrect Answers
B:Hybrid access products have different physical/partner dependencies, performance envelopes and encryption behavior; the correct architecture depends on workload constraints. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
C:Pod CIDR growth and cluster DNS are distinct GKE networking functions; correct secondary allocation and DNS topology must be validated separately. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
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 operational troubleshooting decision.
Question 383
The cloud network operations team has not approved a broad network-wide change. Available evidence indicates: Two correctly attached NCC spokes remain disconnected for a required prefix, but engineers only check that the hub object exists and never review route exchange. Which evidence best tests the Google Cloud networking diagnosis before approving a disruptive change? Select ONE best answer.
- Correlate spoke attachment status, route exchange, filters, tunnel or VLAN state and failed packet analysis.
- Inspect cluster dataplane mode, namespace selectors, Pod labels, policy resources and allowed/denied Pod connection tests.
- Inspect cluster project, host subnet reference, GKE service agent roles, secondary ranges and control-plane or node provisioning errors.
- Compare required security capabilities, selected NGFW tier, enabled policy services, support or enrollment and attack simulation logs.
Explanation
Correct Answer
A:Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
Incorrect Answers
B:Inspect cluster dataplane mode, namespace selectors, Pod labels, policy resources and allowed/denied Pod connection tests. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
C:Inspect cluster project, host subnet reference, GKE service agent roles, secondary ranges and control-plane or node provisioning errors. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
D:Compare required security capabilities, selected NGFW tier, enabled policy services, support or enrollment and attack simulation logs. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
Question 384
A candidate network change has been piloted and stakeholders require a post-change acceptance check. Original problem: Two correctly attached NCC spokes remain disconnected for a required prefix, but engineers only check that the hub object exists and never review route exchange. 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.
- Root cause is isolated to the correct layer and approved applications recover without resetting healthy unrelated components.
- A clearly identified misconfiguration is corrected and approved paths work without rebuilding healthy hub components.
- Allowed prefixes propagate to intended spokes while restricted and accidental prefixes are not redistributed.
- BGP peers establish correctly and exchange intended routes without duplicated endpoint identifiers or credential mismatches.
Explanation
Correct Answer
B:Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path. The result must be validated using the documented site, route, application or user context.
Incorrect Answers
A:Root cause is isolated to the correct layer and approved applications recover without resetting healthy unrelated components. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
C:Allowed prefixes propagate to intended spokes while restricted and accidental prefixes are not redistributed. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
D:BGP peers establish correctly and exchange intended routes without duplicated endpoint identifiers or credential mismatches. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
Question 385
A production Google Cloud networking change review identifies the following problem: Two correctly attached NCC spokes remain disconnected for a required prefix, but engineers only check that the hub object exists and never review route exchange. Which paired Google Cloud networking action and verification should close the review? Select ONE best answer.
- Change: Use Network Intelligence Center Performance Dashboard scopes and time windows to correlate latency and packet-loss measurements with affected paths. Verify: Compare relevant path geography, scoped metrics, incident timestamps and application or load-balancer telemetry.
- Change: Configure NCC supported IP/CIDR range filters and route controls to publish only intended prefixes, then validate source and destination route tables. Verify: Compare announced routes, filter conditions, import/export status, effective spoke route tables and permit/deny reachability tests.
- Change: Diagnose NCC spoke health, eligibility, connectivity and route propagation using hub metrics, logs and scoped Connectivity Tests before correction. Verify: Correlate spoke attachment status, route exchange, filters, tunnel or VLAN state and failed packet analysis.
- Change: Assess supported Classic VPN routing and selector modes and migrate to a suitable HA VPN design when features, support and availability require it. Verify: Inspect gateway version, policy selectors, peer capabilities, static or dynamic routes, target availability needs and migration test plan.
Explanation
Correct Answer
C:This pair links the appropriate network response with evidence of the underlying cloud networking issue. Applied case: Two correctly attached NCC spokes remain disconnected for a required prefix, but engineers only check that the hub object exists and never review route exchange.
Incorrect Answers
A:Change: Use Network Intelligence Center Performance Dashboard scopes and time windows to correlate latency and packet-loss measurements with affected paths. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
B:Change: Configure NCC supported IP/CIDR range filters and route controls to publish only intended prefixes, then validate source and destination route tables. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
D:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Classic VPN legacy migration assessment) rather than the documented NCC operational troubleshooting decision.
Question 386
A Google Cloud Professional Network Engineer is reviewing this Google Cloud networking environment scenario: A previously healthy hybrid spoke stops forwarding after a policy change and operators delete the entire hub before checking connection and route events. An unsafe shortcut would be: Recreate all NCC resources whenever a spoke route disappears, ignoring the effective route advertisement and filter evidence. What should the cloud network administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Recreate all NCC resources whenever a spoke route disappears, ignoring the effective route advertisement and filter evidence.
- Enable supported GKE dataplane and deploy intentional Kubernetes NetworkPolicy controls with positive and denied inter-Pod flow tests.
- Diagnose NCC spoke health, eligibility, connectivity and route propagation using hub metrics, logs and scoped Connectivity Tests before correction.
- Select mutually supported VPC and hybrid path MTUs and evaluate TCP MSS/PMTUD handling to accommodate each encapsulation layer.
Explanation
Correct Answer
C:Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
Incorrect Answers
A:Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path. Use this instead: Diagnose NCC spoke health, eligibility, connectivity and route propagation using hub metrics, logs and scoped Connectivity Tests before correction.
B:Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
D:Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path. Discriminating evidence: Correlate spoke attachment status, route exchange, filters, tunnel or VLAN state and failed packet analysis.
Question 387
A Google Cloud network infrastructure review finds: A previously healthy hybrid spoke stops forwarding after a policy change and operators delete the entire hub before checking connection and route events. The team proposes: Diagnose NCC spoke health, eligibility, connectivity and route propagation using hub metrics, logs and scoped Connectivity Tests before correction. Which Google Cloud networking technical principle most strongly supports the proposed response? Select ONE best answer.
- DNS routing policies steer answers according to supported policy and resolver inputs; cached DNS answers and health checks can affect effective failover.
- Routing tags and IAM secure tags are not interchangeable, and forwarding follows VPC route applicability and precedence rather than route names.
- Cloud NAT provides source translation while Secure Web Proxy supplies eligible policy-controlled web egress; their functions are complementary rather than interchangeable.
- Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
Explanation
Correct Answer
D:Demonstrable success requires: A clearly identified misconfiguration is corrected and approved paths work without rebuilding healthy hub components. This principle explains the proposed network response, which is: Diagnose NCC spoke health, eligibility, connectivity and route propagation using hub metrics, logs and scoped Connectivity Tests before correction.
Incorrect Answers
A:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Cloud DNS geographic and failover policies) rather than the documented NCC operational troubleshooting decision.
B:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Route tags, route priority and selector behavior) rather than the documented NCC operational troubleshooting decision.
C:Cloud NAT provides source translation while Secure Web Proxy supplies eligible policy-controlled web egress; their functions are complementary rather than interchangeable. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
Question 388
The cloud network operations team has not approved a broad network-wide change. Available evidence indicates: A previously healthy hybrid spoke stops forwarding after a policy change and operators delete the entire hub before checking connection and route events. Which evidence best tests the Google Cloud networking diagnosis before approving a disruptive change? Select ONE best answer.
- Inspect supported route-to-ILB configuration, forwarding rule, backend health, ingress/egress NICs and forward and return flow captures during failover.
- Correlate spoke attachment status, route exchange, filters, tunnel or VLAN state and failed packet analysis.
- Inspect current Pod and Service CIDR utilization, new range assignments, node pools, cluster DNS configuration and query logs from failing Pods.
- Compare request key, rate metrics, user populations, rule order, preview decisions and controlled burst traffic.
Explanation
Correct Answer
B:Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path. Confirm afterward that: A clearly identified misconfiguration is corrected and approved paths work without rebuilding healthy hub components.
Incorrect Answers
A:Inspect supported route-to-ILB configuration, forwarding rule, backend health, ingress/egress NICs and forward and return flow captures during failover. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
C:Inspect current Pod and Service CIDR utilization, new range assignments, node pools, cluster DNS configuration and query logs from failing Pods. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
D:Compare request key, rate metrics, user populations, rule order, preview decisions and controlled burst traffic. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
Question 389
A candidate network change has been piloted and stakeholders require a post-change acceptance check. Original problem: A previously healthy hybrid spoke stops forwarding after a policy change and operators delete the entire hub before checking connection and route events. 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.
- A clearly identified misconfiguration is corrected and approved paths work without rebuilding healthy hub components.
- Only approved consumer networks resolve current central private records without duplicating or publicly exposing zones.
- Only intended traffic traverses the healthy appliance tier in both directions with no unintended bypass.
- Required traffic matches the intended governing rule while protected workloads remain denied to unauthorized networks.
Explanation
Correct Answer
A:Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
Incorrect Answers
B:Only approved consumer networks resolve current central private records without duplicating or publicly exposing zones. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
C:Only intended traffic traverses the healthy appliance tier in both directions with no unintended bypass. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
D:Required traffic matches the intended governing rule while protected workloads remain denied to unauthorized networks. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
Question 390
For an original Google Cloud Professional Cloud Network Engineer educational scenario, consider: A previously healthy hybrid spoke stops forwarding after a policy change and operators delete the entire hub before checking connection and route events. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Inspect source behavior, bot score or classification where available, threat indicators, rule logs and partner allow tests.
- Check: Correlate spoke attachment status, route exchange, filters, tunnel or VLAN state and failed packet analysis.
- Change: Diagnose NCC spoke health, eligibility, connectivity and route propagation using hub metrics, logs and scoped Connectivity Tests before correction.
- Recreate all NCC resources whenever a spoke route disappears, ignoring the effective route advertisement and filter evidence.
- Change: Select mutually supported VPC and hybrid path MTUs and evaluate TCP MSS/PMTUD handling to accommodate each encapsulation layer.
Explanation
Correct Answer
B:Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path. Acceptance: A clearly identified misconfiguration is corrected and approved paths work without rebuilding healthy hub components.
C:Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path. Evidence: Correlate spoke attachment status, route exchange, filters, tunnel or VLAN state and failed packet analysis.
Incorrect Answers
A:Check: Inspect source behavior, bot score or classification where available, threat indicators, rule logs and partner allow tests. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
D:For this select two assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.
E:Change: Select mutually supported VPC and hybrid path MTUs and evaluate TCP MSS/PMTUD handling to accommodate each encapsulation layer. Hub and spoke resource existence is not evidence of a valid propagated next hop or an allowed application path.