Google Professional Cloud Network Engineer Practice Test 28 - Prepaway
Practice Exams:

Pass Google Professional Cloud Network Engineer Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium Bundle
$29.98
$79.99 $109.97

Professional Cloud Network Engineer Premium Bundle


  • Premium File 316 Questions & Answers. Last update: Nov 13, 2026
  • Training Course 57 Lectures
  • Study Guide 500 Pages

Google Professional Cloud Network Engineer Practice Test 28

Question 270

At fictional Redwood Analytics, the infrastructure provisioning team automates service-project and network connectivity controls. A Google Cloud network issue is reported: A policy route sends service traffic toward an internal passthrough load balancer that has no healthy firewall appliance backends. The decisive observation is: Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation. Which scoped engineering response is most appropriate?

  1. For fictional Redwood Analytics, infrastructure provisioning team: Restore a supported health check and backend forwarding configuration for the inspected appliance next-hop service.
  2. For fictional Redwood Analytics, infrastructure provisioning team: Narrow the policy-based routing criteria and validate the documented route selection behavior for affected workload classes.
  3. For fictional Redwood Analytics, infrastructure provisioning team: Configure supported reciprocal custom-route exchange settings and verify advertised prefixes and firewalls for the required peering path.
  4. For fictional Redwood Analytics, infrastructure provisioning team: Set a reviewed dynamic routing mode and appropriate Cloud Router advertisement and priority design for approved multi-region connectivity.

Explanation

Correct Answer

A:

A policy route sends service traffic toward an internal passthrough load balancer that has no healthy firewall appliance backends. The clue Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation supports the bounded action: Restore a supported health check and backend forwarding configuration for the inspected appliance next-hop service. Confirm that a permitted test flow traverses a healthy firewall and fails over correctly when one backend is withdrawn.

Incorrect Answers

B:

Narrow the policy-based routing criteria and validate the documented route selection behavior for affected workload classes. It could be useful for another problem, but it does not change Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation. The response needs to restore a supported health check and backend forwarding configuration for the inspected appliance next-hop service.

C:

An alternative action is configure supported reciprocal custom-route exchange settings and verify advertised prefixes and firewalls for the required peering path. This incident instead involves Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation. Confirm the scoped change through a permitted test flow traverses a healthy firewall and fails over correctly when one backend is withdrawn.

D:

Set a reviewed dynamic routing mode and appropriate Cloud Router advertisement and priority design for approved multi-region connectivity. That would not correct the reported Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation. The supported response is to restore a supported health check and backend forwarding configuration for the inspected appliance next-hop service.

Question 271

The infrastructure provisioning team at fictional Redwood Analytics investigates: A policy route sends service traffic toward an internal passthrough load balancer that has no healthy firewall appliance backends. Which particular observation would most directly distinguish the network cause before changing production resources?

  1. For fictional Redwood Analytics, infrastructure provisioning team: Forwarding diagnostics show traffic matching a broad policy-based route ahead of the expected subnet destination path.
  2. For fictional Redwood Analytics, infrastructure provisioning team: Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation.
  3. For fictional Redwood Analytics, infrastructure provisioning team: Peering configuration shows custom-route export enabled on one side while the receiver does not import those routes.
  4. For fictional Redwood Analytics, infrastructure provisioning team: Effective route views reveal the current dynamic routing mode and selected BGP priorities differ from the expected global recovery plan.

Explanation

Correct Answer

B:

Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation. A route to an internal load balancer is useful only when backend health and packet forwarding are correctly configured. This finding supports the targeted response: Restore a supported health check and backend forwarding configuration for the inspected appliance next-hop service.

Incorrect Answers

A:

Forwarding diagnostics show traffic matching a broad policy-based route ahead of the expected subnet destination path. That finding does not isolate the reported issue: a policy route sends service traffic toward an internal passthrough load balancer that has no healthy firewall appliance backends. The determining evidence is Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation.

C:

That alternative instead describes peering configuration shows custom-route export enabled on one side while the receiver does not import those routes. The actual diagnostic record shows Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation instead. The difference matters because a route to an internal load balancer is useful only when backend health and packet forwarding are correctly configured.

D:

Even if effective route views reveal the current dynamic routing mode and selected BGP priorities differ from the expected global recovery plan, it would not establish the cause here. Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation. The case-specific correction is to restore a supported health check and backend forwarding configuration for the inspected appliance next-hop service.

Question 272

In fictional Redwood Analytics, operators encountered: A policy route sends service traffic toward an internal passthrough load balancer that has no healthy firewall appliance backends. Evidence: Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation. They propose: Restore a supported health check and backend forwarding configuration for the inspected appliance next-hop service. Which independent result best confirms the change works?

  1. For fictional Redwood Analytics, infrastructure provisioning team: Targeted traffic traverses the inspection hop while excluded service destinations continue through their approved direct routes.
  2. For fictional Redwood Analytics, infrastructure provisioning team: A controlled regional link interruption triggers the expected reachable alternate route for the application workload.
  3. For fictional Redwood Analytics, infrastructure provisioning team: A permitted test flow traverses a healthy firewall and fails over correctly when one backend is withdrawn.
  4. For fictional Redwood Analytics, infrastructure provisioning team: The authorized peer reaches the intended hybrid prefix while unrelated private networks remain excluded.

Explanation

Correct Answer

C:

A permitted test flow traverses a healthy firewall and fails over correctly when one backend is withdrawn. This measures whether the response corrected Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation rather than merely completing a configuration step.

Incorrect Answers

A:

A test that targeted traffic traverses the inspection hop while excluded service destinations continue through their approved direct routes would not demonstrate closure of this condition. The needed proof is a permitted test flow traverses a healthy firewall and fails over correctly when one backend is withdrawn.

B:

A controlled regional link interruption triggers the expected reachable alternate route for the application workload. That does not demonstrate the case-specific success condition: a permitted test flow traverses a healthy firewall and fails over correctly when one backend is withdrawn. A route to an internal load balancer is useful only when backend health and packet forwarding are correctly configured.

D:

The authorized peer reaches the intended hybrid prefix while unrelated private networks remain excluded. That result does not test the original problem, identified by Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation. Recovery must show that a permitted test flow traverses a healthy firewall and fails over correctly when one backend is withdrawn.

Question 273

At fictional Redwood Analytics, the infrastructure provisioning team reviews: A policy route sends service traffic toward an internal passthrough load balancer that has no healthy firewall appliance backends. Evidence: Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation. Which Google Cloud networking design principle best explains the required correction?

  1. For fictional Redwood Analytics, infrastructure provisioning team: A route to an internal load balancer is useful only when backend health and packet forwarding are correctly configured.
  2. For fictional Redwood Analytics, infrastructure provisioning team: Policy-based routing decisions can intentionally override or alter normal destination-based forwarding.
  3. For fictional Redwood Analytics, infrastructure provisioning team: VPC Network Peering route visibility depends on explicit import and export policy, not solely successful peering attachment.
  4. For fictional Redwood Analytics, infrastructure provisioning team: Cloud Router and VPC route selection must be modeled together when dynamic prefixes cross regional boundaries.

Explanation

Correct Answer

A:

A route to an internal load balancer is useful only when backend health and packet forwarding are correctly configured. The reported symptom arises where Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation. Address it through restore a supported health check and backend forwarding configuration for the inspected appliance next-hop service.

Incorrect Answers

B:

A proposed explanation is Policy-based routing decisions can intentionally override or alter normal destination-based forwarding. The present evidence is Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation, which instead follows from a route to an internal load balancer is useful only when backend health and packet forwarding are correctly configured.

C:

VPC Network Peering route visibility depends on explicit import and export policy, not solely successful peering attachment. This describes another relationship, not the cause of a policy route sends service traffic toward an internal passthrough load balancer that has no healthy firewall appliance backends. A route to an internal load balancer is useful only when backend health and packet forwarding are correctly configured.

D:

The rule cloud Router and VPC route selection must be modeled together when dynamic prefixes cross regional boundaries does not account for Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation. This case is governed by a route to an internal load balancer is useful only when backend health and packet forwarding are correctly configured.

Question 274

At fictional Redwood Analytics, the observed incident is: A policy route sends service traffic toward an internal passthrough load balancer that has no healthy firewall appliance backends. The diagnostic finding is: Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation. Which action AND separate measurable verification best address this case?

  1. For fictional Redwood Analytics, infrastructure provisioning team: Action: Configure supported reciprocal custom-route exchange settings and verify advertised prefixes and firewalls for the required peering path. Independent proof: The authorized peer reaches the intended hybrid prefix while unrelated private networks remain excluded.
  2. For fictional Redwood Analytics, infrastructure provisioning team: Action: Narrow the policy-based routing criteria and validate the documented route selection behavior for affected workload classes. Independent proof: Targeted traffic traverses the inspection hop while excluded service destinations continue through their approved direct routes.
  3. For fictional Redwood Analytics, infrastructure provisioning team: Action: Set a reviewed dynamic routing mode and appropriate Cloud Router advertisement and priority design for approved multi-region connectivity. Independent proof: A controlled regional link interruption triggers the expected reachable alternate route for the application workload.
  4. For fictional Redwood Analytics, infrastructure provisioning team: Action: Restore a supported health check and backend forwarding configuration for the inspected appliance next-hop service. Independent proof: A permitted test flow traverses a healthy firewall and fails over correctly when one backend is withdrawn.

Explanation

Correct Answer

D:

Restore a supported health check and backend forwarding configuration for the inspected appliance next-hop service. Validation requires a permitted test flow traverses a healthy firewall and fails over correctly when one backend is withdrawn rather than relying on a successful configuration save. A route to an internal load balancer is useful only when backend health and packet forwarding are correctly configured.

Incorrect Answers

A:

Action: Configure supported reciprocal custom-route exchange settings and verify advertised prefixes and firewalls for the required peering path. Independent proof: The authorized peer reaches the intended hybrid prefix while unrelated private networks remain excluded. It misses the relevant dependency because a route to an internal load balancer is useful only when backend health and packet forwarding are correctly configured. Instead verify that a permitted test flow traverses a healthy firewall and fails over correctly when one backend is withdrawn.

B:

The proposed pair addresses Action: Narrow the policy-based routing criteria and validate the documented route selection behavior for affected workload classes. Independent proof: Targeted traffic traverses the inspection hop while excluded service destinations continue through their approved direct routes. Here Health-check diagnostics show both network virtual appliance instances are marked unhealthy despite successful route creation. The bounded response is restore a supported health check and backend forwarding configuration for the inspected appliance next-hop service with proof that a permitted test flow traverses a healthy firewall and fails over correctly when one backend is withdrawn.

C:

The alternative action and test—Action: Set a reviewed dynamic routing mode and appropriate Cloud Router advertisement and priority design for approved multi-region connectivity. Independent proof: A controlled regional link interruption triggers the expected reachable alternate route for the application workload—would measure a different issue. This case requires restore a supported health check and backend forwarding configuration for the inspected appliance next-hop service and confirmation that a permitted test flow traverses a healthy firewall and fails over correctly when one backend is withdrawn.

Question 275

At fictional Cobalt Client Solutions, the VPC implementation engineers operate shared networking, policy routing and Kubernetes clusters. A Google Cloud network issue is reported: A VPC spoke is attached to an NCC hub but one spoke cannot learn remote hybrid prefixes required for a permitted service. The decisive observation is: NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. Which scoped engineering response is most appropriate?

  1. For fictional Cobalt Client Solutions, VPC implementation engineers: Review the supported NCC hub topology and spoke route advertisement and filter rules for the needed authorized prefixes.
  2. For fictional Cobalt Client Solutions, VPC implementation engineers: Select a supported star topology and appropriate route policies with firewall enforcement for central-only access.
  3. For fictional Cobalt Client Solutions, VPC implementation engineers: Evaluate supported Private NAT and NCC deployment semantics to translate the authorized traffic while preserving controlled routes.
  4. For fictional Cobalt Client Solutions, VPC implementation engineers: Configure supported multi-Pod CIDR allocation or the appropriate cluster scale-up procedure for the intended cluster mode.

Explanation

Correct Answer

A:

The case reveals NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. That matters because NCC interconnects network spokes using documented route exchange, but attachment alone does not guarantee every route propagates. The corrective step is to review the supported NCC hub topology and spoke route advertisement and filter rules for the needed authorized prefixes.

Incorrect Answers

B:

Another possible response is to select a supported star topology and appropriate route policies with firewall enforcement for central-only access. The case evidence instead shows that NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. NCC interconnects network spokes using documented route exchange, but attachment alone does not guarantee every route propagates.

C:

Evaluate supported Private NAT and NCC deployment semantics to translate the authorized traffic while preserving controlled routes. This does not address the reported incident: a VPC spoke is attached to an NCC hub but one spoke cannot learn remote hybrid prefixes required for a permitted service. NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. The case-specific correction is to review the supported NCC hub topology and spoke route advertisement and filter rules for the needed authorized prefixes.

D:

One alternative would be to configure supported multi-Pod CIDR allocation or the appropriate cluster scale-up procedure for the intended cluster mode. The observed evidence instead shows that NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. The more relevant correction is to review the supported NCC hub topology and spoke route advertisement and filter rules for the needed authorized prefixes.

Question 276

The VPC implementation engineers at fictional Cobalt Client Solutions investigates: A VPC spoke is attached to an NCC hub but one spoke cannot learn remote hybrid prefixes required for a permitted service. Which particular observation would most directly distinguish the network cause before changing production resources?

  1. For fictional Cobalt Client Solutions, VPC implementation engineers: NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings.
  2. For fictional Cobalt Client Solutions, VPC implementation engineers: NCC route views show direct spoke-to-spoke learning that contradicts the approved hub-only application traffic model.
  3. For fictional Cobalt Client Solutions, VPC implementation engineers: Peering and hybrid forwarding tests fail because the same destination range is locally assigned on both sides of the interconnection.
  4. For fictional Cobalt Client Solutions, VPC implementation engineers: Cluster control-plane access configuration includes address blocks outside the documented authorized management perimeter.

Explanation

Correct Answer

A:

NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. It identifies the problem behind a VPC spoke is attached to an NCC hub but one spoke cannot learn remote hybrid prefixes required for a permitted service. NCC interconnects network spokes using documented route exchange, but attachment alone does not guarantee every route propagates.

Incorrect Answers

B:

NCC route views show direct spoke-to-spoke learning that contradicts the approved hub-only application traffic model. It does not account for the observation NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings in the reported situation.

C:

One proposed finding is peering and hybrid forwarding tests fail because the same destination range is locally assigned on both sides of the interconnection. This would indicate another failure; here NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. NCC interconnects network spokes using documented route exchange, but attachment alone does not guarantee every route propagates.

D:

The alternative observation, cluster control-plane access configuration includes address blocks outside the documented authorized management perimeter, concerns a different dependency. This incident is distinguished by NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. NCC interconnects network spokes using documented route exchange, but attachment alone does not guarantee every route propagates.

Question 277

In fictional Cobalt Client Solutions, operators encountered: A VPC spoke is attached to an NCC hub but one spoke cannot learn remote hybrid prefixes required for a permitted service. Evidence: NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. They propose: Review the supported NCC hub topology and spoke route advertisement and filter rules for the needed authorized prefixes. Which independent result best confirms the change works?

  1. For fictional Cobalt Client Solutions, VPC implementation engineers: Branch workloads reach sanctioned hub services but a prohibited branch-to-branch connectivity test fails.
  2. For fictional Cobalt Client Solutions, VPC implementation engineers: Specific translated services become reachable and a negative test confirms unrelated overlapping networks remain inaccessible.
  3. For fictional Cobalt Client Solutions, VPC implementation engineers: An approved enterprise flow retains the intended Pod identity where the network design supports it and unrelated internet egress remains protected.
  4. For fictional Cobalt Client Solutions, VPC implementation engineers: A test path reaches the intended remote service while disallowed prefixes stay isolated from the spoke.

Explanation

Correct Answer

D:

Success requires a test path reaches the intended remote service while disallowed prefixes stay isolated from the spoke. That result tests the previously observed condition: NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. NCC interconnects network spokes using documented route exchange, but attachment alone does not guarantee every route propagates.

Incorrect Answers

A:

Even verifying branch workloads reach sanctioned hub services but a prohibited branch-to-branch connectivity test fails leaves the reported failure unproven. An acceptance test must show that a test path reaches the intended remote service while disallowed prefixes stay isolated from the spoke.

B:

The alternative outcome is specific translated services become reachable and a negative test confirms unrelated overlapping networks remain inaccessible. It may validate a separate setting, but not the required action: review the supported NCC hub topology and spoke route advertisement and filter rules for the needed authorized prefixes. The required observation is a test path reaches the intended remote service while disallowed prefixes stay isolated from the spoke.

C:

An approved enterprise flow retains the intended Pod identity where the network design supports it and unrelated internet egress remains protected. The evidence relevant to this incident is NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. Confirm the corresponding recovery result: A test path reaches the intended remote service while disallowed prefixes stay isolated from the spoke.

Question 278

At fictional Cobalt Client Solutions, the VPC implementation engineers reviews: A VPC spoke is attached to an NCC hub but one spoke cannot learn remote hybrid prefixes required for a permitted service. Evidence: NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. Which Google Cloud networking design principle best explains the required correction?

  1. For fictional Cobalt Client Solutions, VPC implementation engineers: Private NAT can enable constrained connectivity where address overlap prevents direct unambiguous routing.
  2. For fictional Cobalt Client Solutions, VPC implementation engineers: NCC interconnects network spokes using documented route exchange, but attachment alone does not guarantee every route propagates.
  3. For fictional Cobalt Client Solutions, VPC implementation engineers: Topology and route exchange must reflect the trust boundaries of hub-and-spoke applications.
  4. For fictional Cobalt Client Solutions, VPC implementation engineers: Network range expansion must preserve unique primary and secondary address assignments across connected resources.

Explanation

Correct Answer

B:

The governing distinction is that NCC interconnects network spokes using documented route exchange, but attachment alone does not guarantee every route propagates. Here, NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. Review the supported NCC hub topology and spoke route advertisement and filter rules for the needed authorized prefixes.

Incorrect Answers

A:

Private NAT can enable constrained connectivity where address overlap prevents direct unambiguous routing. The decisive observation, NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings, requires a different explanation: NCC interconnects network spokes using documented route exchange, but attachment alone does not guarantee every route propagates.

C:

A different principle is: topology and route exchange must reflect the trust boundaries of hub-and-spoke applications. The causal link actually supported by NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings is NCC interconnects network spokes using documented route exchange, but attachment alone does not guarantee every route propagates.

D:

Network range expansion must preserve unique primary and secondary address assignments across connected resources. However, it does not explain NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. The applicable principle is that NCC interconnects network spokes using documented route exchange, but attachment alone does not guarantee every route propagates.

Question 279

At fictional Cobalt Client Solutions, the observed incident is: A VPC spoke is attached to an NCC hub but one spoke cannot learn remote hybrid prefixes required for a permitted service. The diagnostic finding is: NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. Which action AND separate measurable verification best address this case?

  1. For fictional Cobalt Client Solutions, VPC implementation engineers: Action: Review the supported NCC hub topology and spoke route advertisement and filter rules for the needed authorized prefixes. Independent proof: A test path reaches the intended remote service while disallowed prefixes stay isolated from the spoke.
  2. For fictional Cobalt Client Solutions, VPC implementation engineers: Action: Select a supported star topology and appropriate route policies with firewall enforcement for central-only access. Independent proof: Branch workloads reach sanctioned hub services but a prohibited branch-to-branch connectivity test fails.
  3. For fictional Cobalt Client Solutions, VPC implementation engineers: Action: Evaluate supported Private NAT and NCC deployment semantics to translate the authorized traffic while preserving controlled routes. Independent proof: Specific translated services become reachable and a negative test confirms unrelated overlapping networks remain inaccessible.
  4. For fictional Cobalt Client Solutions, VPC implementation engineers: Action: Set a reviewed dynamic routing mode and appropriate Cloud Router advertisement and priority design for approved multi-region connectivity. Independent proof: A controlled regional link interruption triggers the expected reachable alternate route for the application workload.

Explanation

Correct Answer

A:

The documented evidence is NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. The proportionate response is to review the supported NCC hub topology and spoke route advertisement and filter rules for the needed authorized prefixes; its success must be shown by a test path reaches the intended remote service while disallowed prefixes stay isolated from the spoke.

Incorrect Answers

B:

Action: Select a supported star topology and appropriate route policies with firewall enforcement for central-only access. Independent proof: Branch workloads reach sanctioned hub services but a prohibited branch-to-branch connectivity test fails. The pair does not resolve the observed NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. Use review the supported NCC hub topology and spoke route advertisement and filter rules for the needed authorized prefixes and verify a test path reaches the intended remote service while disallowed prefixes stay isolated from the spoke.

C:

The alternate plan combines Action: Evaluate supported Private NAT and NCC deployment semantics to translate the authorized traffic while preserving controlled routes. Independent proof: Specific translated services become reachable and a negative test confirms unrelated overlapping networks remain inaccessible. The identified fault is NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. Closing it requires a test path reaches the intended remote service while disallowed prefixes stay isolated from the spoke.

D:

The alternative proposal is Action: Set a reviewed dynamic routing mode and appropriate Cloud Router advertisement and priority design for approved multi-region connectivity. Independent proof: A controlled regional link interruption triggers the expected reachable alternate route for the application workload. It does not address the current evidence: NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. The appropriate action is review the supported NCC hub topology and spoke route advertisement and filter rules for the needed authorized prefixes.

Question 280

At fictional Meridian Business Group, the infrastructure provisioning team automates service-project and network connectivity controls. A Google Cloud network issue is reported: A VPC spoke is attached to an NCC hub but one spoke cannot learn remote hybrid prefixes required for a permitted service. The decisive observation is: NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. Which scoped engineering response is most appropriate?

  1. For fictional Meridian Business Group, infrastructure provisioning team: Select a supported star topology and appropriate route policies with firewall enforcement for central-only access.
  2. For fictional Meridian Business Group, infrastructure provisioning team: Evaluate supported Private NAT and NCC deployment semantics to translate the authorized traffic while preserving controlled routes.
  3. For fictional Meridian Business Group, infrastructure provisioning team: Review the supported NCC hub topology and spoke route advertisement and filter rules for the needed authorized prefixes.
  4. For fictional Meridian Business Group, infrastructure provisioning team: Configure an appropriate supported non-masquerade destination policy while validating routes and return-path security.

Explanation

Correct Answer

C:

NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. Instead of unrelated changes, review the supported NCC hub topology and spoke route advertisement and filter rules for the needed authorized prefixes. The expected result is a test path reaches the intended remote service while disallowed prefixes stay isolated from the spoke.

Incorrect Answers

A:

Select a supported star topology and appropriate route policies with firewall enforcement for central-only access. It could be useful for another problem, but it does not change NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. The response needs to review the supported NCC hub topology and spoke route advertisement and filter rules for the needed authorized prefixes.

B:

An alternative action is evaluate supported Private NAT and NCC deployment semantics to translate the authorized traffic while preserving controlled routes. This incident instead involves NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. Confirm the scoped change through a test path reaches the intended remote service while disallowed prefixes stay isolated from the spoke.

D:

Configure an appropriate supported non-masquerade destination policy while validating routes and return-path security. That would not correct the reported NCC route tables and effective VPC routes show the relevant spoke route is filtered or excluded under current route-exchange settings. The supported response is to review the supported NCC hub topology and spoke route advertisement and filter rules for the needed authorized prefixes.

Professional Cloud Network Engineer Practice Tests