Google Professional Cloud Network Engineer Practice Test 59 - 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 59

Question 580

In fictional Pinecrest Digital, operators encountered: A third-party router appliance is attached as an NCC spoke but a remote region cannot learn its advertised service prefix. Evidence: Route advertisements and Cloud Router peering checks show the appliance prefix does not appear in the selected hub route table. They propose: Validate the supported router appliance spoke, BGP, and hub route exchange configuration before changing application paths. Which independent result best confirms the change works?

  1. For fictional Pinecrest Digital, multicloud backbone operations team: An allowed branch-to-branch test passes through documented paths while disallowed traffic remains restricted.
  2. For fictional Pinecrest Digital, multicloud backbone operations team: A test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.
  3. For fictional Pinecrest Digital, multicloud backbone operations team: A controlled first-tunnel loss restores authorized application routing through the remaining permitted tunnel.
  4. For fictional Pinecrest Digital, multicloud backbone operations team: The intended prefix appears in approved route inventories and test traffic traverses the authorized appliance.

Explanation

Correct Answer

D:

The intended prefix appears in approved route inventories and test traffic traverses the authorized appliance. Without that result, the finding route advertisements and Cloud Router peering checks show the appliance prefix does not appear in the selected hub route table would remain unresolved.

Incorrect Answers

A:

A test that an allowed branch-to-branch test passes through documented paths while disallowed traffic remains restricted would not demonstrate closure of this condition. The needed proof is the intended prefix appears in approved route inventories and test traffic traverses the authorized appliance.

B:

A test from the required source reaches the exact authorized destination and unrelated spokes remain isolated. That does not demonstrate the case-specific success condition: the intended prefix appears in approved route inventories and test traffic traverses the authorized appliance. Router appliances participate in NCC routing only under the documented spoke and control-plane attachment model.

C:

A controlled first-tunnel loss restores authorized application routing through the remaining permitted tunnel. That result does not test the original problem, identified by route advertisements and Cloud Router peering checks show the appliance prefix does not appear in the selected hub route table. Recovery must show that the intended prefix appears in approved route inventories and test traffic traverses the authorized appliance.

Question 581

At fictional Pinecrest Digital, the multicloud backbone operations team reviews: A third-party router appliance is attached as an NCC spoke but a remote region cannot learn its advertised service prefix. Evidence: Route advertisements and Cloud Router peering checks show the appliance prefix does not appear in the selected hub route table. Which Google Cloud networking design principle best explains the required correction?

  1. For fictional Pinecrest Digital, multicloud backbone operations team: NCC hybrid spoke attachment and authorized inter-spoke traffic are distinct deployment controls.
  2. For fictional Pinecrest Digital, multicloud backbone operations team: NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit.
  3. For fictional Pinecrest Digital, multicloud backbone operations team: BGP custom advertisement policy is an access and routing design responsibility, not merely a convenience setting.
  4. For fictional Pinecrest Digital, multicloud backbone operations team: Router appliances participate in NCC routing only under the documented spoke and control-plane attachment model.

Explanation

Correct Answer

D:

Router appliances participate in NCC routing only under the documented spoke and control-plane attachment model. The diagnostic record, route advertisements and Cloud Router peering checks show the appliance prefix does not appear in the selected hub route table, fits that mechanism rather than a separate system issue.

Incorrect Answers

A:

A proposed explanation is NCC hybrid spoke attachment and authorized inter-spoke traffic are distinct deployment controls. The present evidence is route advertisements and Cloud Router peering checks show the appliance prefix does not appear in the selected hub route table, which instead follows from router appliances participate in NCC routing only under the documented spoke and control-plane attachment model.

B:

NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit. This describes another relationship, not the cause of a third-party router appliance is attached as an NCC spoke but a remote region cannot learn its advertised service prefix. Router appliances participate in NCC routing only under the documented spoke and control-plane attachment model.

C:

The rule BGP custom advertisement policy is an access and routing design responsibility, not merely a convenience setting does not account for route advertisements and Cloud Router peering checks show the appliance prefix does not appear in the selected hub route table. This case is governed by router appliances participate in NCC routing only under the documented spoke and control-plane attachment model.

Question 582

At fictional Pinecrest Digital, the observed incident is: A third-party router appliance is attached as an NCC spoke but a remote region cannot learn its advertised service prefix. The diagnostic finding is: Route advertisements and Cloud Router peering checks show the appliance prefix does not appear in the selected hub route table. Which action AND separate measurable verification best address this case?

  1. For fictional Pinecrest Digital, multicloud backbone operations team: Action: Validate the supported router appliance spoke, BGP, and hub route exchange configuration before changing application paths. Independent proof: The intended prefix appears in approved route inventories and test traffic traverses the authorized appliance.
  2. For fictional Pinecrest Digital, multicloud backbone operations team: Action: Configure the supported NCC hybrid-spoke site-to-site data transfer model and verify network and firewall policy. Independent proof: An allowed branch-to-branch test passes through documented paths while disallowed traffic remains restricted.
  3. For fictional Pinecrest Digital, multicloud backbone operations team: Action: Document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design. Independent proof: A test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.
  4. For fictional Pinecrest Digital, multicloud backbone operations team: Action: Configure appropriate custom advertised prefixes with exact source authorization and verify the intended Cloud Router propagation policy. Independent proof: The partner learns only sanctioned destinations and a negative test confirms other internal prefixes remain unavailable.

Explanation

Correct Answer

A:

Router appliances participate in NCC routing only under the documented spoke and control-plane attachment model. The action is to validate the supported router appliance spoke, BGP, and hub route exchange configuration before changing application paths; the independent test is that the intended prefix appears in approved route inventories and test traffic traverses the authorized appliance.

Incorrect Answers

B:

Action: Configure the supported NCC hybrid-spoke site-to-site data transfer model and verify network and firewall policy. Independent proof: An allowed branch-to-branch test passes through documented paths while disallowed traffic remains restricted. It misses the relevant dependency because router appliances participate in NCC routing only under the documented spoke and control-plane attachment model. Instead verify that the intended prefix appears in approved route inventories and test traffic traverses the authorized appliance.

C:

The proposed pair addresses Action: Document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design. Independent proof: A test from the required source reaches the exact authorized destination and unrelated spokes remain isolated. Here route advertisements and Cloud Router peering checks show the appliance prefix does not appear in the selected hub route table. The bounded response is validate the supported router appliance spoke, BGP, and hub route exchange configuration before changing application paths with proof that the intended prefix appears in approved route inventories and test traffic traverses the authorized appliance.

D:

The alternative action and test—Action: Configure appropriate custom advertised prefixes with exact source authorization and verify the intended Cloud Router propagation policy. Independent proof: The partner learns only sanctioned destinations and a negative test confirms other internal prefixes remain unavailable—would measure a different issue. This case requires validate the supported router appliance spoke, BGP, and hub route exchange configuration before changing application paths and confirmation that the intended prefix appears in approved route inventories and test traffic traverses the authorized appliance.

Question 583

At fictional Fairview Cooperative, the hybrid connectivity engineering team maintains on-premises and cloud transport links. A Google Cloud network issue is reported: Three networks connect through distinct peering and NCC resources, but a team expects an arbitrary third-party prefix to propagate end to end. The decisive observation is: The effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. Which scoped engineering response is most appropriate?

  1. For fictional Fairview Cooperative, hybrid connectivity engineering team: Validate the supported router appliance spoke, BGP, and hub route exchange configuration before changing application paths.
  2. For fictional Fairview Cooperative, hybrid connectivity engineering team: Document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design.
  3. For fictional Fairview Cooperative, hybrid connectivity engineering team: Configure the supported NCC hybrid-spoke site-to-site data transfer model and verify network and firewall policy.
  4. For fictional Fairview Cooperative, hybrid connectivity engineering team: Configure the supported required HA VPN tunnel and peer redundancy topology and verify BGP route selection across both interfaces.

Explanation

Correct Answer

B:

The effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit. The case-specific correction is to document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design. Confirm that a test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.

Incorrect Answers

A:

Another possible response is to validate the supported router appliance spoke, BGP, and hub route exchange configuration before changing application paths. The case evidence instead shows that the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit.

C:

Configure the supported NCC hybrid-spoke site-to-site data transfer model and verify network and firewall policy. This does not address the reported incident: three networks connect through distinct peering and NCC resources, but a team expects an arbitrary third-party prefix to propagate end to end. The effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. The case-specific correction is to document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design.

D:

One alternative would be to configure the supported required HA VPN tunnel and peer redundancy topology and verify BGP route selection across both interfaces. The observed evidence instead shows that the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. The more relevant correction is to document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design.

Question 584

The hybrid connectivity engineering team at fictional Fairview Cooperative investigates: Three networks connect through distinct peering and NCC resources, but a team expects an arbitrary third-party prefix to propagate end to end. Which particular observation would most directly distinguish the network cause before changing production resources?

  1. For fictional Fairview Cooperative, hybrid connectivity engineering team: The effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms.
  2. For fictional Fairview Cooperative, hybrid connectivity engineering team: Hub configuration and route tables show the required site-to-site data transfer behavior or spoke route exchange is not enabled for this topology.
  3. For fictional Fairview Cooperative, hybrid connectivity engineering team: Route advertisements and Cloud Router peering checks show the appliance prefix does not appear in the selected hub route table.
  4. For fictional Fairview Cooperative, hybrid connectivity engineering team: The current attachment has no supported dynamic route learning and its static selectors do not cover newly introduced application subnets.

Explanation

Correct Answer

A:

The effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. That observation distinguishes the reported incident because NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit. The appropriate response is to document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design.

Incorrect Answers

B:

Hub configuration and route tables show the required site-to-site data transfer behavior or spoke route exchange is not enabled for this topology. It does not account for the observation the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms in the reported situation.

C:

One proposed finding is route advertisements and Cloud Router peering checks show the appliance prefix does not appear in the selected hub route table. This would indicate another failure; here the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit.

D:

The alternative observation, the current attachment has no supported dynamic route learning and its static selectors do not cover newly introduced application subnets, concerns a different dependency. This incident is distinguished by the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit.

Question 585

In fictional Fairview Cooperative, operators encountered: Three networks connect through distinct peering and NCC resources, but a team expects an arbitrary third-party prefix to propagate end to end. Evidence: The effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. They propose: Document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design. Which independent result best confirms the change works?

  1. For fictional Fairview Cooperative, hybrid connectivity engineering team: The intended prefix appears in approved route inventories and test traffic traverses the authorized appliance.
  2. For fictional Fairview Cooperative, hybrid connectivity engineering team: An allowed branch-to-branch test passes through documented paths while disallowed traffic remains restricted.
  3. For fictional Fairview Cooperative, hybrid connectivity engineering team: A test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.
  4. For fictional Fairview Cooperative, hybrid connectivity engineering team: Tunnel negotiation succeeds and a protected subnet test proves encrypted bidirectional application connectivity.

Explanation

Correct Answer

C:

Verify the change by checking that a test from the required source reaches the exact authorized destination and unrelated spokes remain isolated. The original clue was the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. The test is meaningful because NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit.

Incorrect Answers

A:

Even verifying the intended prefix appears in approved route inventories and test traffic traverses the authorized appliance leaves the reported failure unproven. An acceptance test must show that a test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.

B:

The alternative outcome is an allowed branch-to-branch test passes through documented paths while disallowed traffic remains restricted. It may validate a separate setting, but not the required action: document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design. The required observation is a test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.

D:

Tunnel negotiation succeeds and a protected subnet test proves encrypted bidirectional application connectivity. The evidence relevant to this incident is the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. Confirm the corresponding recovery result: A test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.

Question 586

At fictional Fairview Cooperative, the hybrid connectivity engineering team reviews: Three networks connect through distinct peering and NCC resources, but a team expects an arbitrary third-party prefix to propagate end to end. Evidence: The effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. Which Google Cloud networking design principle best explains the required correction?

  1. For fictional Fairview Cooperative, hybrid connectivity engineering team: Router appliances participate in NCC routing only under the documented spoke and control-plane attachment model.
  2. For fictional Fairview Cooperative, hybrid connectivity engineering team: NCC hybrid spoke attachment and authorized inter-spoke traffic are distinct deployment controls.
  3. For fictional Fairview Cooperative, hybrid connectivity engineering team: NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit.
  4. For fictional Fairview Cooperative, hybrid connectivity engineering team: A physical interconnect and its logical VLAN and BGP route exchange must all be configured for usable hybrid connectivity.

Explanation

Correct Answer

C:

The underlying rule is that NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit. The effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. A suitable correction is to document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design.

Incorrect Answers

A:

Router appliances participate in NCC routing only under the documented spoke and control-plane attachment model. The decisive observation, the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms, requires a different explanation: NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit.

B:

A different principle is: NCC hybrid spoke attachment and authorized inter-spoke traffic are distinct deployment controls. The causal link actually supported by the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms is NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit.

D:

A physical interconnect and its logical VLAN and BGP route exchange must all be configured for usable hybrid connectivity. However, it does not explain the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. The applicable principle is that NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit.

Question 587

At fictional Fairview Cooperative, the observed incident is: Three networks connect through distinct peering and NCC resources, but a team expects an arbitrary third-party prefix to propagate end to end. The diagnostic finding is: The effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. Which action AND separate measurable verification best address this case?

  1. For fictional Fairview Cooperative, hybrid connectivity engineering team: Action: Configure the supported NCC hybrid-spoke site-to-site data transfer model and verify network and firewall policy. Independent proof: An allowed branch-to-branch test passes through documented paths while disallowed traffic remains restricted.
  2. For fictional Fairview Cooperative, hybrid connectivity engineering team: Action: Document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design. Independent proof: A test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.
  3. For fictional Fairview Cooperative, hybrid connectivity engineering team: Action: Validate the supported router appliance spoke, BGP, and hub route exchange configuration before changing application paths. Independent proof: The intended prefix appears in approved route inventories and test traffic traverses the authorized appliance.
  4. For fictional Fairview Cooperative, hybrid connectivity engineering team: Action: Plan supported redundant Cross-Cloud Interconnect topology, VLAN attachments, and failover routing for the agreed critical systems. Independent proof: A controlled loss of the primary interconnect leaves required application traffic using an approved recovery path.

Explanation

Correct Answer

B:

The underlying clue is the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. Correct it by document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design and confirm that a test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.

Incorrect Answers

A:

Action: Configure the supported NCC hybrid-spoke site-to-site data transfer model and verify network and firewall policy. Independent proof: An allowed branch-to-branch test passes through documented paths while disallowed traffic remains restricted. The pair does not resolve the observed the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. Use document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design and verify a test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.

C:

The alternate plan combines Action: Validate the supported router appliance spoke, BGP, and hub route exchange configuration before changing application paths. Independent proof: The intended prefix appears in approved route inventories and test traffic traverses the authorized appliance. The identified fault is the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. Closing it requires a test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.

D:

The alternative proposal is Action: Plan supported redundant Cross-Cloud Interconnect topology, VLAN attachments, and failover routing for the agreed critical systems. Independent proof: A controlled loss of the primary interconnect leaves required application traffic using an approved recovery path. It does not address the current evidence: the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. The appropriate action is document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design.

Question 588

At fictional Seabright Utilities, the multicloud backbone operations team operates BGP, HA VPN and interconnect recovery. A Google Cloud network issue is reported: Three networks connect through distinct peering and NCC resources, but a team expects an arbitrary third-party prefix to propagate end to end. The decisive observation is: The effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. Which scoped engineering response is most appropriate?

  1. For fictional Seabright Utilities, multicloud backbone operations team: Validate the supported router appliance spoke, BGP, and hub route exchange configuration before changing application paths.
  2. For fictional Seabright Utilities, multicloud backbone operations team: Configure the supported NCC hybrid-spoke site-to-site data transfer model and verify network and firewall policy.
  3. For fictional Seabright Utilities, multicloud backbone operations team: Document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design.
  4. For fictional Seabright Utilities, multicloud backbone operations team: Reconcile advertised BGP route priorities and supported best-path selection behavior at the applicable Cloud Router and VPC scope.

Explanation

Correct Answer

C:

Three networks connect through distinct peering and NCC resources, but a team expects an arbitrary third-party prefix to propagate end to end. The clue the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms supports the bounded action: Document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design. Confirm that a test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.

Incorrect Answers

A:

Validate the supported router appliance spoke, BGP, and hub route exchange configuration before changing application paths. It could be useful for another problem, but it does not change the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. The response needs to document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design.

B:

An alternative action is configure the supported NCC hybrid-spoke site-to-site data transfer model and verify network and firewall policy. This incident instead involves the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. Confirm the scoped change through a test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.

D:

Reconcile advertised BGP route priorities and supported best-path selection behavior at the applicable Cloud Router and VPC scope. That would not correct the reported the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. The supported response is to document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design.

Question 589

The multicloud backbone operations team at fictional Seabright Utilities investigates: Three networks connect through distinct peering and NCC resources, but a team expects an arbitrary third-party prefix to propagate end to end. Which particular observation would most directly distinguish the network cause before changing production resources?

  1. For fictional Seabright Utilities, multicloud backbone operations team: Route advertisements and Cloud Router peering checks show the appliance prefix does not appear in the selected hub route table.
  2. For fictional Seabright Utilities, multicloud backbone operations team: Hub configuration and route tables show the required site-to-site data transfer behavior or spoke route exchange is not enabled for this topology.
  3. For fictional Seabright Utilities, multicloud backbone operations team: The effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms.
  4. For fictional Seabright Utilities, multicloud backbone operations team: BGP export records show an approved peer receiving routes for business units outside its contracted connectivity scope.

Explanation

Correct Answer

C:

The effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit. This finding supports the targeted response: Document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design.

Incorrect Answers

A:

Route advertisements and Cloud Router peering checks show the appliance prefix does not appear in the selected hub route table. That finding does not isolate the reported issue: three networks connect through distinct peering and NCC resources, but a team expects an arbitrary third-party prefix to propagate end to end. The determining evidence is the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms.

B:

That alternative instead describes hub configuration and route tables show the required site-to-site data transfer behavior or spoke route exchange is not enabled for this topology. The actual diagnostic record shows the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms instead. The difference matters because NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit.

D:

Even if BGP export records show an approved peer receiving routes for business units outside its contracted connectivity scope, it would not establish the cause here. The effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. The case-specific correction is to document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design.

Question 590

In fictional Seabright Utilities, operators encountered: Three networks connect through distinct peering and NCC resources, but a team expects an arbitrary third-party prefix to propagate end to end. Evidence: The effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. They propose: Document supported NCC spoke types and network-to-network route propagation, then add a valid approved connectivity design. Which independent result best confirms the change works?

  1. For fictional Seabright Utilities, multicloud backbone operations team: An allowed branch-to-branch test passes through documented paths while disallowed traffic remains restricted.
  2. For fictional Seabright Utilities, multicloud backbone operations team: A test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.
  3. For fictional Seabright Utilities, multicloud backbone operations team: The intended prefix appears in approved route inventories and test traffic traverses the authorized appliance.
  4. For fictional Seabright Utilities, multicloud backbone operations team: A controlled loss of the primary interconnect leaves required application traffic using an approved recovery path.

Explanation

Correct Answer

B:

A test from the required source reaches the exact authorized destination and unrelated spokes remain isolated. This measures whether the response corrected the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms rather than merely completing a configuration step.

Incorrect Answers

A:

A test that an allowed branch-to-branch test passes through documented paths while disallowed traffic remains restricted would not demonstrate closure of this condition. The needed proof is a test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.

C:

The intended prefix appears in approved route inventories and test traffic traverses the authorized appliance. That does not demonstrate the case-specific success condition: a test from the required source reaches the exact authorized destination and unrelated spokes remain isolated. NCC connectivity and peering each have defined route propagation limits that cannot be treated as universal transit.

D:

A controlled loss of the primary interconnect leaves required application traffic using an approved recovery path. That result does not test the original problem, identified by the effective route table has no advertised destination and the intended path depends on an unsupported combination of transitivity mechanisms. Recovery must show that a test from the required source reaches the exact authorized destination and unrelated spokes remain isolated.

Professional Cloud Network Engineer Practice Tests