cert
cert-1
cert-2

Pass Cisco 300-610 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
300-610 Exam - Verified By Experts
300-610 Premium File

300-610 Premium File

$69.99
$76.99
  • Premium File 350 Questions & Answers. Last Update: Nov 13, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 10 downloads in the last 7 days
block-screenshots
Cisco 300-610 Practice Test 18

Question 170

At a regulated private-cloud campus, a post-incident design review focuses on preventing: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?

  1. Retune thresholds on hardware or link-speed changes.
  2. Review QoS shares when application proportions change.
  3. Recheck DSCP and 802.1p mappings when new services are added.
  4. Document which queues truly require no-drop behavior.

Explanation

Correct Answer

D:

The most relevant ongoing safeguard is: Document which queues truly require no-drop behavior. The risk it addresses is: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. This check is tied to the technical principle: Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback. The immediate correction remains: Adopt class-specific supported PFC/ECN design instead of indiscriminate link-level pause. Periodically validate the safeguard through two different observations. Review whether global pause or PFC is actually negotiated Measure impact on ordinary TCP and control flows during a test burst. The continuing acceptance target is: RoCE loss goals are met without unnecessarily suspending all traffic on the link.

Incorrect Answers

A:

This is a continuing control for ecn marking before pfc; its underlying principle is: ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport. The recurring risk here is different: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The intended long-term acceptance condition remains: RoCE loss goals are met without unnecessarily suspending all traffic on the link.

B:

This is a continuing control for ets bandwidth for rdma and storage; its underlying principle is: Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class. The recurring risk here is different: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. The intended long-term acceptance condition remains: RoCE loss goals are met without unnecessarily suspending all traffic on the link.

C:

This is a continuing control for pfc head-of-line blocking; its underlying principle is: PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking. The recurring risk here is different: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The intended long-term acceptance condition remains: RoCE loss goals are met without unnecessarily suspending all traffic on the link.

Question 171

At a dual-spine infrastructure project, during a controlled design review, the team discovers: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?

  1. Align supported anycast gateway identities and VNIs throughout the intended VXLAN EVPN fabric.
  2. Evaluate supported multicast or replication options and constrain EVI membership before expanding L2 reach.
  3. Map each routed subnet and anycast gateway to the right tenant VRF and Layer 3 VNI.
  4. Extend only segments with justified mobility requirements and prefer routed boundaries for other workloads.

Explanation

Correct Answer

D:

The relevant failure is: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The technical distinction is: VXLAN EVPN can extend a broadcast domain, but a stretched fault domain increases MAC, flood and failure exposure. The targeted correction is: Extend only segments with justified mobility requirements and prefer routed boundaries for other workloads. Before changing the design, check two independent observations. Map which applications need IP preservation across sites Estimate BUM replication and failure domains for each proposed extension. Accept the change only if: Only required networks span sites while other traffic remains routed and isolated.

Incorrect Answers

A:

This action targets anycast gateway consistency in vxlan, where the mechanism is: Distributed anycast gateway designs require aligned gateway IP/MAC semantics and consistent tenant VNIs across eligible leaves. That is a separate condition from the problem in this question: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. Even a successful repair of the alternative would not establish the required result: Only required networks span sites while other traffic remains routed and isolated. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

B:

This action targets vxlan head-end replication capacity, where the mechanism is: VXLAN ingress replication can multiply BUM frames across many tunnel peers and must be sized for the membership scale. That is a separate condition from the problem in this question: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. Even a successful repair of the alternative would not establish the required result: Only required networks span sites while other traffic remains routed and isolated. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

C:

This action targets vxlan l3vni design for routed services, where the mechanism is: Inter-subnet EVPN routing needs a tenant VRF and supported L3VNI/IRB relationship, not only L2VNI membership. That is a separate condition from the problem in this question: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. Even a successful repair of the alternative would not establish the required result: Only required networks span sites while other traffic remains routed and isolated. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

Question 172

At a low-latency GPU workload fabric, before changing the fabric, the team observes: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. Acceptance requires evidence from the running system, not just the saved design. Which pair of observations most directly tests the proposed diagnosis before a change?

  1. Inspect EVPN route types and RTs crossing the border; test a legitimate mobile endpoint and a prohibited tenant prefix.
  2. Inspect gateway SVI/VRF bindings and L3VNI routes; trace a test packet from one tenant subnet to another across the fabric.
  3. Inspect received route-target extended communities; compare receiving EVI import targets and local MAC installation.
  4. Map which applications need IP preservation across sites; estimate BUM replication and failure domains for each proposed extension.

Explanation

Correct Answer

D:

The first observation is: Map which applications need IP preservation across sites The independent second observation is: Estimate BUM replication and failure domains for each proposed extension. Together they test the proposed diagnosis of this incident: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The underlying technical principle is: VXLAN EVPN can extend a broadcast domain, but a stretched fault domain increases MAC, flood and failure exposure. If those checks confirm it, the appropriate next action is: Extend only segments with justified mobility requirements and prefer routed boundaries for other workloads. The expected measurable result is: Only required networks span sites while other traffic remains routed and isolated.

Incorrect Answers

A:

These observations investigate inter-dc evpn route policy; they would be useful if the symptoms were: Two data centers exchange all EVPN MAC routes without filtering and accidentally reveal one site's private tenant routes to another tenant. That alternative rests on the principle: Inter-site EVPN design needs deliberate RT, route type, and gateway boundary policy, not unconditional exchange of all advertisements. The question instead asks for evidence about: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The discriminating observations here are: Map which applications need IP preservation across sites Estimate BUM replication and failure domains for each proposed extension.

B:

These observations investigate vxlan l3vni design for routed services; they would be useful if the symptoms were: Two tenant subnets are bridged by EVPN but routed inter-subnet traffic falls back to an unintended global route table. That alternative rests on the principle: Inter-subnet EVPN routing needs a tenant VRF and supported L3VNI/IRB relationship, not only L2VNI membership. The question instead asks for evidence about: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The discriminating observations here are: Map which applications need IP preservation across sites Estimate BUM replication and failure domains for each proposed extension.

C:

These observations investigate evpn rt import for tenant vni; they would be useful if the symptoms were: An EVPN MAC route is visible in the global BGP table but not installed in the remote tenant EVI. That alternative rests on the principle: Route targets control import of EVPN routes into relevant Ethernet VPN instances, distinct from the presence of BGP advertisements. The question instead asks for evidence about: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The discriminating observations here are: Map which applications need IP preservation across sites Estimate BUM replication and failure domains for each proposed extension.

Question 173

At a two-region enterprise VXLAN fabric, the data-center team needs to explain this behavior: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?

  1. Inter-subnet EVPN routing needs a tenant VRF and supported L3VNI/IRB relationship, not only L2VNI membership.
  2. Route targets control import of EVPN routes into relevant Ethernet VPN instances, distinct from the presence of BGP advertisements.
  3. VXLAN EVPN can extend a broadcast domain, but a stretched fault domain increases MAC, flood and failure exposure.
  4. Inter-site EVPN design needs deliberate RT, route type, and gateway boundary policy, not unconditional exchange of all advertisements.

Explanation

Correct Answer

C:

The controlling technical principle is: VXLAN EVPN can extend a broadcast domain, but a stretched fault domain increases MAC, flood and failure exposure. This matters because the reported design failure is: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The first diagnostic check is: Map which applications need IP preservation across sites The independent check is: Estimate BUM replication and failure domains for each proposed extension. These facts support the targeted intervention: Extend only segments with justified mobility requirements and prefer routed boundaries for other workloads. Confirm that the resulting design meets this condition: Only required networks span sites while other traffic remains routed and isolated.

Incorrect Answers

A:

The offered principle describes vxlan l3vni design for routed services: Inter-subnet EVPN routing needs a tenant VRF and supported L3VNI/IRB relationship, not only L2VNI membership. That is useful for a distinct incident, such as: Two tenant subnets are bridged by EVPN but routed inter-subnet traffic falls back to an unintended global route table. It does not account for the reported failure: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The governing principle in this situation is: VXLAN EVPN can extend a broadcast domain, but a stretched fault domain increases MAC, flood and failure exposure.

B:

The offered principle describes evpn rt import for tenant vni: Route targets control import of EVPN routes into relevant Ethernet VPN instances, distinct from the presence of BGP advertisements. That is useful for a distinct incident, such as: An EVPN MAC route is visible in the global BGP table but not installed in the remote tenant EVI. It does not account for the reported failure: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The governing principle in this situation is: VXLAN EVPN can extend a broadcast domain, but a stretched fault domain increases MAC, flood and failure exposure.

D:

The offered principle describes inter-dc evpn route policy: Inter-site EVPN design needs deliberate RT, route type, and gateway boundary policy, not unconditional exchange of all advertisements. That is useful for a distinct incident, such as: Two data centers exchange all EVPN MAC routes without filtering and accidentally reveal one site's private tenant routes to another tenant. It does not account for the reported failure: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The governing principle in this situation is: VXLAN EVPN can extend a broadcast domain, but a stretched fault domain increases MAC, flood and failure exposure.

Question 174

At a 60-rack compute cluster, the team completed an authorized repair for: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?

  1. Only required networks span sites while other traffic remains routed and isolated.
  2. Tenant MACs import into the right EVI without cross-tenant MAC learning.
  3. A migrated endpoint retains intended default-gateway connectivity.
  4. Allowed mobility works while unrelated route and MAC information stays isolated.

Explanation

Correct Answer

A:

The relevant measurable success criterion is: Only required networks span sites while other traffic remains routed and isolated. It addresses the original reported defect: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Map which applications need IP preservation across sites Estimate BUM replication and failure domains for each proposed extension. The correction being evaluated is: Extend only segments with justified mobility requirements and prefer routed boundaries for other workloads. The underlying reason that correction matters is: VXLAN EVPN can extend a broadcast domain, but a stretched fault domain increases MAC, flood and failure exposure.

Incorrect Answers

B:

This metric would help validate a correction to evpn rt import for tenant vni, rather than the original reported issue. The other issue is: An EVPN MAC route is visible in the global BGP table but not installed in the remote tenant EVI. Here the defect to be resolved is: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The expected measurable outcome for the actual incident is: Only required networks span sites while other traffic remains routed and isolated. A positive result for the other service would not prove this requirement is met.

C:

This metric would help validate a correction to anycast gateway consistency in vxlan, rather than the original reported issue. The other issue is: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. Here the defect to be resolved is: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The expected measurable outcome for the actual incident is: Only required networks span sites while other traffic remains routed and isolated. A positive result for the other service would not prove this requirement is met.

D:

This metric would help validate a correction to inter-dc evpn route policy, rather than the original reported issue. The other issue is: Two data centers exchange all EVPN MAC routes without filtering and accidentally reveal one site's private tenant routes to another tenant. Here the defect to be resolved is: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The expected measurable outcome for the actual incident is: Only required networks span sites while other traffic remains routed and isolated. A positive result for the other service would not prove this requirement is met.

Question 175

At a virtualized application data center, the architecture standards group considers the recurring risk: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?

  1. Check RT uniqueness and import symmetry on each tenant rollout.
  2. Revisit stretched-subnet membership when application mobility requirements end.
  3. Validate L2-to-L3 VNI mapping with each new tenant network.
  4. Audit gateway and VNI templates across leaf additions.

Explanation

Correct Answer

B:

The most relevant ongoing safeguard is: Revisit stretched-subnet membership when application mobility requirements end. The risk it addresses is: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. This check is tied to the technical principle: VXLAN EVPN can extend a broadcast domain, but a stretched fault domain increases MAC, flood and failure exposure. The immediate correction remains: Extend only segments with justified mobility requirements and prefer routed boundaries for other workloads. Periodically validate the safeguard through two different observations. Map which applications need IP preservation across sites Estimate BUM replication and failure domains for each proposed extension. The continuing acceptance target is: Only required networks span sites while other traffic remains routed and isolated.

Incorrect Answers

A:

This is a continuing control for evpn rt import for tenant vni; its underlying principle is: Route targets control import of EVPN routes into relevant Ethernet VPN instances, distinct from the presence of BGP advertisements. The recurring risk here is different: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: An EVPN MAC route is visible in the global BGP table but not installed in the remote tenant EVI. The intended long-term acceptance condition remains: Only required networks span sites while other traffic remains routed and isolated.

C:

This is a continuing control for vxlan l3vni design for routed services; its underlying principle is: Inter-subnet EVPN routing needs a tenant VRF and supported L3VNI/IRB relationship, not only L2VNI membership. The recurring risk here is different: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: Two tenant subnets are bridged by EVPN but routed inter-subnet traffic falls back to an unintended global route table. The intended long-term acceptance condition remains: Only required networks span sites while other traffic remains routed and isolated.

D:

This is a continuing control for anycast gateway consistency in vxlan; its underlying principle is: Distributed anycast gateway designs require aligned gateway IP/MAC semantics and consistent tenant VNIs across eligible leaves. The recurring risk here is different: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The intended long-term acceptance condition remains: Only required networks span sites while other traffic remains routed and isolated.

Question 176

At an AI-training data-center pod, a proposed deployment has this failure mode: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?

  1. Correct only the authorized EVI route-target import/export policy and preserve other tenant separation.
  2. Map each routed subnet and anycast gateway to the right tenant VRF and Layer 3 VNI.
  3. Align supported anycast gateway identities and VNIs throughout the intended VXLAN EVPN fabric.
  4. Extend only segments with justified mobility requirements and prefer routed boundaries for other workloads.

Explanation

Correct Answer

C:

The relevant failure is: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The technical distinction is: Distributed anycast gateway designs require aligned gateway IP/MAC semantics and consistent tenant VNIs across eligible leaves. The targeted correction is: Align supported anycast gateway identities and VNIs throughout the intended VXLAN EVPN fabric. Before changing the design, check two independent observations. Compare gateway MAC and subnet settings on both leaves Inspect EVPN MAC/IP routes and moved-host neighbor resolution. Accept the change only if: A migrated endpoint retains intended default-gateway connectivity.

Incorrect Answers

A:

This action targets evpn rt import for tenant vni, where the mechanism is: Route targets control import of EVPN routes into relevant Ethernet VPN instances, distinct from the presence of BGP advertisements. That is a separate condition from the problem in this question: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. Even a successful repair of the alternative would not establish the required result: A migrated endpoint retains intended default-gateway connectivity. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

B:

This action targets vxlan l3vni design for routed services, where the mechanism is: Inter-subnet EVPN routing needs a tenant VRF and supported L3VNI/IRB relationship, not only L2VNI membership. That is a separate condition from the problem in this question: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. Even a successful repair of the alternative would not establish the required result: A migrated endpoint retains intended default-gateway connectivity. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

D:

This action targets evpn vxlan l2 extension scope, where the mechanism is: VXLAN EVPN can extend a broadcast domain, but a stretched fault domain increases MAC, flood and failure exposure. That is a separate condition from the problem in this question: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. Even a successful repair of the alternative would not establish the required result: A migrated endpoint retains intended default-gateway connectivity. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

Question 177

At a regulated private-cloud campus, the cause remains unconfirmed for this reported issue: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. Acceptance requires evidence from the running system, not just the saved design. Which pair of observations most directly tests the proposed diagnosis before a change?

  1. Compare gateway MAC and subnet settings on both leaves; inspect EVPN MAC/IP routes and moved-host neighbor resolution.
  2. Measure BUM fan-out and replication traffic per VTEP; compare expected receiver count and actual overlay flood list.
  3. Inspect received route-target extended communities; compare receiving EVI import targets and local MAC installation.
  4. Inspect EVPN route types and RTs crossing the border; test a legitimate mobile endpoint and a prohibited tenant prefix.

Explanation

Correct Answer

A:

The first observation is: Compare gateway MAC and subnet settings on both leaves The independent second observation is: Inspect EVPN MAC/IP routes and moved-host neighbor resolution. Together they test the proposed diagnosis of this incident: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The underlying technical principle is: Distributed anycast gateway designs require aligned gateway IP/MAC semantics and consistent tenant VNIs across eligible leaves. If those checks confirm it, the appropriate next action is: Align supported anycast gateway identities and VNIs throughout the intended VXLAN EVPN fabric. The expected measurable result is: A migrated endpoint retains intended default-gateway connectivity.

Incorrect Answers

B:

These observations investigate vxlan head-end replication capacity; they would be useful if the symptoms were: A single tenant bridge domain spans hundreds of VTEPs and unicast traffic is healthy but BUM bursts saturate leaf uplinks. That alternative rests on the principle: VXLAN ingress replication can multiply BUM frames across many tunnel peers and must be sized for the membership scale. The question instead asks for evidence about: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The discriminating observations here are: Compare gateway MAC and subnet settings on both leaves Inspect EVPN MAC/IP routes and moved-host neighbor resolution.

C:

These observations investigate evpn rt import for tenant vni; they would be useful if the symptoms were: An EVPN MAC route is visible in the global BGP table but not installed in the remote tenant EVI. That alternative rests on the principle: Route targets control import of EVPN routes into relevant Ethernet VPN instances, distinct from the presence of BGP advertisements. The question instead asks for evidence about: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The discriminating observations here are: Compare gateway MAC and subnet settings on both leaves Inspect EVPN MAC/IP routes and moved-host neighbor resolution.

D:

These observations investigate inter-dc evpn route policy; they would be useful if the symptoms were: Two data centers exchange all EVPN MAC routes without filtering and accidentally reveal one site's private tenant routes to another tenant. That alternative rests on the principle: Inter-site EVPN design needs deliberate RT, route type, and gateway boundary policy, not unconditional exchange of all advertisements. The question instead asks for evidence about: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The discriminating observations here are: Compare gateway MAC and subnet settings on both leaves Inspect EVPN MAC/IP routes and moved-host neighbor resolution.

Question 178

At a dual-spine infrastructure project, a failure review must identify the central technical cause of: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?

  1. Inter-subnet EVPN routing needs a tenant VRF and supported L3VNI/IRB relationship, not only L2VNI membership.
  2. Distributed anycast gateway designs require aligned gateway IP/MAC semantics and consistent tenant VNIs across eligible leaves.
  3. Inter-site EVPN design needs deliberate RT, route type, and gateway boundary policy, not unconditional exchange of all advertisements.
  4. Route targets control import of EVPN routes into relevant Ethernet VPN instances, distinct from the presence of BGP advertisements.

Explanation

Correct Answer

B:

The controlling technical principle is: Distributed anycast gateway designs require aligned gateway IP/MAC semantics and consistent tenant VNIs across eligible leaves. This matters because the reported design failure is: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The first diagnostic check is: Compare gateway MAC and subnet settings on both leaves The independent check is: Inspect EVPN MAC/IP routes and moved-host neighbor resolution. These facts support the targeted intervention: Align supported anycast gateway identities and VNIs throughout the intended VXLAN EVPN fabric. Confirm that the resulting design meets this condition: A migrated endpoint retains intended default-gateway connectivity.

Incorrect Answers

A:

The offered principle describes vxlan l3vni design for routed services: Inter-subnet EVPN routing needs a tenant VRF and supported L3VNI/IRB relationship, not only L2VNI membership. That is useful for a distinct incident, such as: Two tenant subnets are bridged by EVPN but routed inter-subnet traffic falls back to an unintended global route table. It does not account for the reported failure: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The governing principle in this situation is: Distributed anycast gateway designs require aligned gateway IP/MAC semantics and consistent tenant VNIs across eligible leaves.

C:

The offered principle describes inter-dc evpn route policy: Inter-site EVPN design needs deliberate RT, route type, and gateway boundary policy, not unconditional exchange of all advertisements. That is useful for a distinct incident, such as: Two data centers exchange all EVPN MAC routes without filtering and accidentally reveal one site's private tenant routes to another tenant. It does not account for the reported failure: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The governing principle in this situation is: Distributed anycast gateway designs require aligned gateway IP/MAC semantics and consistent tenant VNIs across eligible leaves.

D:

The offered principle describes evpn rt import for tenant vni: Route targets control import of EVPN routes into relevant Ethernet VPN instances, distinct from the presence of BGP advertisements. That is useful for a distinct incident, such as: An EVPN MAC route is visible in the global BGP table but not installed in the remote tenant EVI. It does not account for the reported failure: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The governing principle in this situation is: Distributed anycast gateway designs require aligned gateway IP/MAC semantics and consistent tenant VNIs across eligible leaves.

Question 179

At a low-latency GPU workload fabric, the service owner needs evidence of resolution for: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?

  1. A migrated endpoint retains intended default-gateway connectivity.
  2. Only required networks span sites while other traffic remains routed and isolated.
  3. Allowed mobility works while unrelated route and MAC information stays isolated.
  4. Inter-subnet forwarding stays within the approved tenant context.

Explanation

Correct Answer

A:

The relevant measurable success criterion is: A migrated endpoint retains intended default-gateway connectivity. It addresses the original reported defect: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Compare gateway MAC and subnet settings on both leaves Inspect EVPN MAC/IP routes and moved-host neighbor resolution. The correction being evaluated is: Align supported anycast gateway identities and VNIs throughout the intended VXLAN EVPN fabric. The underlying reason that correction matters is: Distributed anycast gateway designs require aligned gateway IP/MAC semantics and consistent tenant VNIs across eligible leaves.

Incorrect Answers

B:

This metric would help validate a correction to evpn vxlan l2 extension scope, rather than the original reported issue. The other issue is: A proposal stretches every application VLAN between two sites simply because the VXLAN overlay supports it. Here the defect to be resolved is: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The expected measurable outcome for the actual incident is: A migrated endpoint retains intended default-gateway connectivity. A positive result for the other service would not prove this requirement is met.

C:

This metric would help validate a correction to inter-dc evpn route policy, rather than the original reported issue. The other issue is: Two data centers exchange all EVPN MAC routes without filtering and accidentally reveal one site's private tenant routes to another tenant. Here the defect to be resolved is: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The expected measurable outcome for the actual incident is: A migrated endpoint retains intended default-gateway connectivity. A positive result for the other service would not prove this requirement is met.

D:

This metric would help validate a correction to vxlan l3vni design for routed services, rather than the original reported issue. The other issue is: Two tenant subnets are bridged by EVPN but routed inter-subnet traffic falls back to an unintended global route table. Here the defect to be resolved is: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The expected measurable outcome for the actual incident is: A migrated endpoint retains intended default-gateway connectivity. A positive result for the other service would not prove this requirement is met.

Question 180

At a two-region enterprise VXLAN fabric, after correction, the team wants to prevent recurrence of: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?

  1. Audit gateway and VNI templates across leaf additions.
  2. Validate L2-to-L3 VNI mapping with each new tenant network.
  3. Check RT uniqueness and import symmetry on each tenant rollout.
  4. Track EVI peer counts and BUM rates as tenant topology grows.

Explanation

Correct Answer

A:

The most relevant ongoing safeguard is: Audit gateway and VNI templates across leaf additions. The risk it addresses is: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. This check is tied to the technical principle: Distributed anycast gateway designs require aligned gateway IP/MAC semantics and consistent tenant VNIs across eligible leaves. The immediate correction remains: Align supported anycast gateway identities and VNIs throughout the intended VXLAN EVPN fabric. Periodically validate the safeguard through two different observations. Compare gateway MAC and subnet settings on both leaves Inspect EVPN MAC/IP routes and moved-host neighbor resolution. The continuing acceptance target is: A migrated endpoint retains intended default-gateway connectivity.

Incorrect Answers

B:

This is a continuing control for vxlan l3vni design for routed services; its underlying principle is: Inter-subnet EVPN routing needs a tenant VRF and supported L3VNI/IRB relationship, not only L2VNI membership. The recurring risk here is different: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: Two tenant subnets are bridged by EVPN but routed inter-subnet traffic falls back to an unintended global route table. The intended long-term acceptance condition remains: A migrated endpoint retains intended default-gateway connectivity.

C:

This is a continuing control for evpn rt import for tenant vni; its underlying principle is: Route targets control import of EVPN routes into relevant Ethernet VPN instances, distinct from the presence of BGP advertisements. The recurring risk here is different: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: An EVPN MAC route is visible in the global BGP table but not installed in the remote tenant EVI. The intended long-term acceptance condition remains: A migrated endpoint retains intended default-gateway connectivity.

D:

This is a continuing control for vxlan head-end replication capacity; its underlying principle is: VXLAN ingress replication can multiply BUM frames across many tunnel peers and must be sized for the membership scale. The recurring risk here is different: A virtual machine moves between two leafs and loses reachability because its default gateway differs between VTEPs. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A single tenant bridge domain spans hundreds of VTEPs and unicast traffic is healthy but BUM bursts saturate leaf uplinks. The intended long-term acceptance condition remains: A migrated endpoint retains intended default-gateway connectivity.

Designing Cisco Data Center Infrastructure for Traditional and AI Workloads (300-610) Practice Tests