Practice Exams:

Cisco 400-007 Dumps

EXAM: Cisco Certified Design Expert
Verified By Experts
Premium Bundle
$19.99
$54.99 $74.98

400-007 Premium Bundle


  • Premium File 349 Questions & Answers
  • Study Guide 934 Pages

Cisco 400-007 Practice Test 50

Question 490

A network design team is assessing this customer situation: An EVPN fabric moves virtual machines between racks but endpoint reachability converges too slowly. Out-of-hours operations staff cannot perform manual changes at every remote site. Which technical rationale best explains the proposed design choice under these constraints?

  1. VRF boundaries keep overlapping routes distinct while explicit import/export policy controls crossings
  2. EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state
  3. Explicit go/no-go measurements allow reversible progress before hidden state diverges too far
  4. A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point

Answer & Explanations

Correct answer: B

A.

The alternative principle is: VRF boundaries keep overlapping routes distinct while explicit import/export policy controls crossings. It instead explains this action: Use separate VRF routing contexts and tightly reviewed route leaking for approved shared endpoints. For the present requirement, the controlling mechanism is: EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state.

B.

EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state. This explains the action: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies. For the described facts—An EVPN fabric moves virtual machines between racks but endpoint reachability converges too slowly—test the outcome through: A VM move is reachable via the new leaf with correct MAC and IP policy and acceptable convergence.

C.

The alternative principle is: Explicit go/no-go measurements allow reversible progress before hidden state diverges too far. It instead explains this action: Define prechange snapshots, staged checkpoints and objective rollback triggers for each dependency. For the present requirement, the controlling mechanism is: EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state.

D.

The alternative principle is: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point. It instead explains this action: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. For the present requirement, the controlling mechanism is: EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state.

Question 491

A network design team is assessing this customer situation: An EVPN fabric moves virtual machines between racks but endpoint reachability converges too slowly. Out-of-hours operations staff cannot perform manual changes at every remote site. Which failure is the most direct risk of taking the tempting design shortcut?

  1. Routing feedback can create loops, unstable preference or unexpected reachability
  2. Mixed-family applications become inaccessible or return traffic is misrouted
  3. Stale endpoint entries can black-hole traffic after migrations
  4. A peer mistake can redirect sensitive traffic or exhaust routing resources

Answer & Explanations

Correct answer: C

A.

The offered consequence belongs to the alternative control path: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes. The relevant failure for the current situation is: Stale endpoint entries can black-hole traffic after migrations. The distinction follows from: EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state.

B.

The offered consequence belongs to the alternative control path: Design explicit dual-stack or translation points with tested application compatibility and state capacity. The relevant failure for the current situation is: Stale endpoint entries can black-hole traffic after migrations. The distinction follows from: EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state.

C.

Stale endpoint entries can black-hole traffic after migrations. That is the risk in the reported situation—An EVPN fabric moves virtual machines between racks but endpoint reachability converges too slowly. The corrective action is: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies. Technical basis: EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state.

D.

The offered consequence belongs to the alternative control path: Apply explicit import and export prefix and AS-path policies plus maximum-prefix safeguards. The relevant failure for the current situation is: Stale endpoint entries can black-hole traffic after migrations. The distinction follows from: EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state.

Question 492

A network design team is assessing this customer situation: An EVPN fabric moves virtual machines between racks but endpoint reachability converges too slowly. Out-of-hours operations staff cannot perform manual changes at every remote site. Which prerequisite should the architect confirm before choosing and defending this design?

  1. Check partner protocols, DNS synthesis needs, NAT64 or proxy support and dual-stack policy
  2. Agree backup validity, service checkpoints, authorized abort owner and maximum outage
  3. Measure east-west traffic, port speed, spine capacity, ECMP support and operational complexity
  4. Check EVPN route type support, MAC mobility sequence, proxy ARP/ND and failure handling

Answer & Explanations

Correct answer: D

A.

The offered preparation belongs with the alternative action: Design explicit dual-stack or translation points with tested application compatibility and state capacity. Here the necessary starting condition is: Check EVPN route type support, MAC mobility sequence, proxy ARP/ND and failure handling. It supports: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies.

B.

The offered preparation belongs with the alternative action: Define prechange snapshots, staged checkpoints and objective rollback triggers for each dependency. Here the necessary starting condition is: Check EVPN route type support, MAC mobility sequence, proxy ARP/ND and failure handling. It supports: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies.

C.

The offered preparation belongs with the alternative action: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. Here the necessary starting condition is: Check EVPN route type support, MAC mobility sequence, proxy ARP/ND and failure handling. It supports: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies.

D.

The necessary starting condition is: Check EVPN route type support, MAC mobility sequence, proxy ARP/ND and failure handling. This enables the action: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies. Validate the result with: A VM move is reachable via the new leaf with correct MAC and IP policy and acceptable convergence.

Question 493

In a separate customer architecture review, this issue arises: A multisite workload migrates across leaf pairs while L2 flood traffic grows. The network is in an incremental migration with old and new paths both active. Which high-level network design choice most directly meets the stated technical and operational requirement?

  1. Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies
  2. Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets
  3. Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes
  4. Limit access-layer L2 domains and use routed distribution boundaries with edge-loop safeguards

Answer & Explanations

Correct answer: A

A.

EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state. For the documented situation—A multisite workload migrates across leaf pairs while L2 flood traffic grows—the targeted response is: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies. Check: A VM move is reachable via the new leaf with correct MAC and IP policy and acceptable convergence.

B.

The alternative addresses: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. Its principle is: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point. In this case the needed action is: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies. Confirm by: A VM move is reachable via the new leaf with correct MAC and IP policy and acceptable convergence.

C.

The alternative addresses a different technical concern: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains. The governing mechanism here is: EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state. Accordingly, use: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies.

D.

Smaller broadcast domains and loop controls constrain accidental Layer 2 topology changes. That supports the alternative intervention: Limit access-layer L2 domains and use routed distribution boundaries with edge-loop safeguards. The present situation—A multisite workload migrates across leaf pairs while L2 flood traffic grows—instead calls for: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies. Technical basis: EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state.

Question 494

In a separate customer architecture review, this issue arises: A multisite workload migrates across leaf pairs while L2 flood traffic grows. The network is in an incremental migration with old and new paths both active. Which technical rationale best explains the proposed design choice under these constraints?

  1. MPLS VPN isolation depends on which VPN routes a PE installs, not only transport label existence
  2. EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state
  3. Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains
  4. A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point

Answer & Explanations

Correct answer: B

A.

The alternative principle is: MPLS VPN isolation depends on which VPN routes a PE installs, not only transport label existence. It instead explains this action: Restrict VPN import/export using explicit route targets and service-specific policy. For the present requirement, the controlling mechanism is: EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state.

B.

EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state. This explains the action: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies. For the described facts—A multisite workload migrates across leaf pairs while L2 flood traffic grows—test the outcome through: A VM move is reachable via the new leaf with correct MAC and IP policy and acceptable convergence.

C.

The alternative principle is: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains. It instead explains this action: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes. For the present requirement, the controlling mechanism is: EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state.

D.

The alternative principle is: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point. It instead explains this action: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. For the present requirement, the controlling mechanism is: EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state. The scenario is: A multisite workload migrates across leaf pairs while L2 flood traffic grows.

Question 495

In a separate customer architecture review, this issue arises: A multisite workload migrates across leaf pairs while L2 flood traffic grows. The network is in an incremental migration with old and new paths both active. Which acceptance result would most convincingly demonstrate that the design addresses the critical requirement?

  1. A probe from partner sites reaches the approved service but not unrelated customer prefixes
  2. A rack expansion test preserves target bisection throughput and controlled failover behavior
  3. A VM move is reachable via the new leaf with correct MAC and IP policy and acceptable convergence
  4. A branch link-flap test limits LSA churn to its intended domain while regional routes remain valid

Answer & Explanations

Correct answer: C

A.

The offered observation would test: Restrict VPN import/export using explicit route targets and service-specific policy. It would not establish that the stated requirement has been met. The direct evidence needed here is: A VM move is reachable via the new leaf with correct MAC and IP policy and acceptable convergence.

B.

The offered observation would test: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. It would not establish that the stated requirement has been met. The direct evidence needed here is: A VM move is reachable via the new leaf with correct MAC and IP policy and acceptable convergence.

C.

Direct verification: A VM move is reachable via the new leaf with correct MAC and IP policy and acceptable convergence. This is the relevant evidence for the action: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies. The reason is: EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state.

D.

The offered observation would test: Create area boundaries and resilient ABRs that localize topology changes without isolating reachability. It would not establish that the stated requirement has been met. The direct evidence needed here is: A VM move is reachable via the new leaf with correct MAC and IP policy and acceptable convergence.

Question 496

In a separate customer architecture review, this issue arises: A multisite workload migrates across leaf pairs while L2 flood traffic grows. The network is in an incremental migration with old and new paths both active. Which prerequisite should the architect confirm before choosing and defending this design?

  1. Document authorized prefixes, ownership, maximum-prefix budget and exception process
  2. Agree backup validity, service checkpoints, authorized abort owner and maximum outage
  3. Inventory L2 adjacency, redundant links, STP role and legitimate endpoint mobility needs
  4. Check EVPN route type support, MAC mobility sequence, proxy ARP/ND and failure handling

Answer & Explanations

Correct answer: D

A.

The offered preparation belongs with the alternative action: Apply explicit import and export prefix and AS-path policies plus maximum-prefix safeguards. Here the necessary starting condition is: Check EVPN route type support, MAC mobility sequence, proxy ARP/ND and failure handling. It supports: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies.

B.

The offered preparation belongs with the alternative action: Define prechange snapshots, staged checkpoints and objective rollback triggers for each dependency. Here the necessary starting condition is: Check EVPN route type support, MAC mobility sequence, proxy ARP/ND and failure handling. It supports: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies. The scenario is: A multisite workload migrates across leaf pairs while L2 flood traffic grows.

C.

The offered preparation belongs with the alternative action: Limit access-layer L2 domains and use routed distribution boundaries with edge-loop safeguards. Here the necessary starting condition is: Check EVPN route type support, MAC mobility sequence, proxy ARP/ND and failure handling. It supports: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies.

D.

The necessary starting condition is: Check EVPN route type support, MAC mobility sequence, proxy ARP/ND and failure handling. This enables the action: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies. Validate the result with: A VM move is reachable via the new leaf with correct MAC and IP policy and acceptable convergence. The scenario is: A multisite workload migrates across leaf pairs while L2 flood traffic grows.

Question 497

A network design team is assessing this customer situation: A managed provider hosts several customers with overlapping RFC1918 addresses. The customer requires clear acceptance tests before a new contract is signed. Which high-level network design choice most directly meets the stated technical and operational requirement?

  1. Use separate VRF routing contexts and tightly reviewed route leaking for approved shared endpoints
  2. Translate data classification and service ownership into explicit path and segmentation policy
  3. Use L1/L2 boundaries and leak only policy-approved interlevel routes
  4. Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets

Answer & Explanations

Correct answer: A

A.

VRF boundaries keep overlapping routes distinct while explicit import/export policy controls crossings. First establish the prerequisite: Enumerate tenant ownership, overlapping subnets, shared-service rules and route targets. The proposed response is: Use separate VRF routing contexts and tightly reviewed route leaking for approved shared endpoints. Validation: An overlapping-prefix test reaches only intended tenant resources and approved shared services.

B.

The alternative addresses a different technical concern: Reachability should reflect differentiated business constraints, not a single cheapest route for all traffic. The governing mechanism here is: VRF boundaries keep overlapping routes distinct while explicit import/export policy controls crossings. Accordingly, use: Use separate VRF routing contexts and tightly reviewed route leaking for approved shared endpoints.

C.

IS-IS hierarchy can keep detailed local topology from burdening the backbone while preserving needed reachability. That supports the alternative intervention: Use L1/L2 boundaries and leak only policy-approved interlevel routes. The present situation—A managed provider hosts several customers with overlapping RFC1918 addresses—instead calls for: Use separate VRF routing contexts and tightly reviewed route leaking for approved shared endpoints. Technical basis: VRF boundaries keep overlapping routes distinct while explicit import/export policy controls crossings.

D.

The alternative addresses: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. Its principle is: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point. In this case the needed action is: Use separate VRF routing contexts and tightly reviewed route leaking for approved shared endpoints. Confirm by: An overlapping-prefix test reaches only intended tenant resources and approved shared services.

Question 498

A network design team is assessing this customer situation: A managed provider hosts several customers with overlapping RFC1918 addresses. The customer requires clear acceptance tests before a new contract is signed. Which technical rationale best explains the proposed design choice under these constraints?

  1. Coexistence protects service continuity only when route ownership and address overlaps are resolved
  2. VRF boundaries keep overlapping routes distinct while explicit import/export policy controls crossings
  3. Address-family transition requires predictable protocol interworking rather than an assumed transparent conversion
  4. Multicast replicates at branching points rather than at the source for every receiver

Answer & Explanations

Correct answer: B

A.

The alternative principle is: Coexistence protects service continuity only when route ownership and address overlaps are resolved. It instead explains this action: Use a time-bounded dual-running migration with explicit route authority and per-site cutover controls. For the present requirement, the controlling mechanism is: VRF boundaries keep overlapping routes distinct while explicit import/export policy controls crossings.

B.

VRF boundaries keep overlapping routes distinct while explicit import/export policy controls crossings. This explains the action: Use separate VRF routing contexts and tightly reviewed route leaking for approved shared endpoints. For the described facts—A managed provider hosts several customers with overlapping RFC1918 addresses—test the outcome through: An overlapping-prefix test reaches only intended tenant resources and approved shared services.

C.

The alternative principle is: Address-family transition requires predictable protocol interworking rather than an assumed transparent conversion. It instead explains this action: Design explicit dual-stack or translation points with tested application compatibility and state capacity. For the present requirement, the controlling mechanism is: VRF boundaries keep overlapping routes distinct while explicit import/export policy controls crossings.

D.

The alternative principle is: Multicast replicates at branching points rather than at the source for every receiver. It instead explains this action: Use a scoped multicast distribution design where membership, provider support and security policy justify it. For the present requirement, the controlling mechanism is: VRF boundaries keep overlapping routes distinct while explicit import/export policy controls crossings.

Question 499

A network design team is assessing this customer situation: A managed provider hosts several customers with overlapping RFC1918 addresses. The customer requires clear acceptance tests before a new contract is signed. Which acceptance result would most convincingly demonstrate that the design addresses the critical requirement?

  1. A lab-induced access loop is contained to its edge segment while routed services remain reachable
  2. Join and leave tests deliver subscribed traffic across intended sites without leaking to others
  3. An overlapping-prefix test reaches only intended tenant resources and approved shared services
  4. A probe from partner sites reaches the approved service but not unrelated customer prefixes

Answer & Explanations

Correct answer: C

A.

The offered observation would test: Limit access-layer L2 domains and use routed distribution boundaries with edge-loop safeguards. It would not establish that the stated requirement has been met. The direct evidence needed here is: An overlapping-prefix test reaches only intended tenant resources and approved shared services.

B.

The offered observation would test: Use a scoped multicast distribution design where membership, provider support and security policy justify it. It would not establish that the stated requirement has been met. The direct evidence needed here is: An overlapping-prefix test reaches only intended tenant resources and approved shared services.

C.

Direct verification: An overlapping-prefix test reaches only intended tenant resources and approved shared services. This is the relevant evidence for the action: Use separate VRF routing contexts and tightly reviewed route leaking for approved shared endpoints. The reason is: VRF boundaries keep overlapping routes distinct while explicit import/export policy controls crossings.

D.

The offered observation would test: Restrict VPN import/export using explicit route targets and service-specific policy. It would not establish that the stated requirement has been met. The direct evidence needed here is: An overlapping-prefix test reaches only intended tenant resources and approved shared services.

Question 500

A network design team is assessing this customer situation: A managed provider hosts several customers with overlapping RFC1918 addresses. The customer requires clear acceptance tests before a new contract is signed. Which failure is the most direct risk of taking the tempting design shortcut?

  1. Extranet connectivity can inadvertently bridge previously separate customer routing domains
  2. Increasing rack density creates hot spots and tail latency spikes
  3. Control-plane churn and database scale can degrade backbone convergence
  4. Routes collide and customer data may cross unauthorized trust boundaries

Answer & Explanations

Correct answer: D

A.

The offered consequence belongs to the alternative control path: Restrict VPN import/export using explicit route targets and service-specific policy. The relevant failure for the current situation is: Routes collide and customer data may cross unauthorized trust boundaries. The distinction follows from: VRF boundaries keep overlapping routes distinct while explicit import/export policy controls crossings.

B.

The offered consequence belongs to the alternative control path: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. The relevant failure for the current situation is: Routes collide and customer data may cross unauthorized trust boundaries. The distinction follows from: VRF boundaries keep overlapping routes distinct while explicit import/export policy controls crossings.

C.

The offered consequence belongs to the alternative control path: Use L1/L2 boundaries and leak only policy-approved interlevel routes. The relevant failure for the current situation is: Routes collide and customer data may cross unauthorized trust boundaries. The distinction follows from: VRF boundaries keep overlapping routes distinct while explicit import/export policy controls crossings.

D.

Routes collide and customer data may cross unauthorized trust boundaries. That is the risk in the reported situation—A managed provider hosts several customers with overlapping RFC1918 addresses. The corrective action is: Use separate VRF routing contexts and tightly reviewed route leaking for approved shared endpoints. Technical basis: VRF boundaries keep overlapping routes distinct while explicit import/export policy controls crossings.

Cisco Certified Design Expert (400-007) Practice Tests