Cisco 400-007 Dumps
Cisco 400-007 Practice Test 49
Question 480
In a separate customer architecture review, this issue arises: A regional company stretches access VLANs between buildings and experiences STP reconvergence outages. Service ownership is divided between cloud, network, and application teams. Which failure is the most direct risk of taking the tempting design shortcut?
Answer & Explanations
Correct answer: D
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: A single wiring error can propagate broadcast storms across the campus. The distinction follows from: Smaller broadcast domains and loop controls constrain accidental Layer 2 topology changes.
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: A single wiring error can propagate broadcast storms across the campus. The distinction follows from: Smaller broadcast domains and loop controls constrain accidental Layer 2 topology changes.
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: A single wiring error can propagate broadcast storms across the campus. The distinction follows from: Smaller broadcast domains and loop controls constrain accidental Layer 2 topology changes.
A single wiring error can propagate broadcast storms across the campus. That is the risk in the reported situation—A regional company stretches access VLANs between buildings and experiences STP reconvergence outages. The corrective action is: Limit access-layer L2 domains and use routed distribution boundaries with edge-loop safeguards. Technical basis: Smaller broadcast domains and loop controls constrain accidental Layer 2 topology changes.
Question 481
A network design team is assessing this customer situation: A data center growth plan adds many racks but the existing three-tier core is oversubscribed. Audit evidence must be retained separately from the devices under change. Which technical rationale best explains the proposed design choice under these constraints?
Answer & Explanations
Correct answer: A
A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point. This explains the action: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. For the described facts—A data center growth plan adds many racks but the existing three-tier core is oversubscribed—test the outcome through: A rack expansion test preserves target bisection throughput and controlled failover behavior.
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: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point.
The alternative principle is: Business expansion changes administrative domains, latency demands and allowed traffic paths. It instead explains this action: Define regional route, policy and service boundaries from business geography and data constraints. For the present requirement, the controlling mechanism is: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point.
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: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point.
Question 482
A network design team is assessing this customer situation: A data center growth plan adds many racks but the existing three-tier core is oversubscribed. Audit evidence must be retained separately from the devices under change. Which acceptance result would most convincingly demonstrate that the design addresses the critical requirement?
Answer & Explanations
Correct answer: B
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 rack expansion test preserves target bisection throughput and controlled failover behavior.
Direct verification: A rack expansion test preserves target bisection throughput and controlled failover behavior. This is the relevant evidence for the action: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. The reason is: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point.
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: A rack expansion test preserves target bisection throughput and controlled failover behavior.
The offered observation would test: Allocate hierarchical IPv6 prefixes per region and role with room for subnet growth. It would not establish that the stated requirement has been met. The direct evidence needed here is: A rack expansion test preserves target bisection throughput and controlled failover behavior.
Question 483
A network design team is assessing this customer situation: A data center growth plan adds many racks but the existing three-tier core is oversubscribed. Audit evidence must be retained separately from the devices under change. Which failure is the most direct risk of taking the tempting design shortcut?
Answer & Explanations
Correct answer: C
The offered consequence belongs to the alternative control path: Allocate hierarchical IPv6 prefixes per region and role with room for subnet growth. The relevant failure for the current situation is: Increasing rack density creates hot spots and tail latency spikes. The distinction follows from: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point.
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: Increasing rack density creates hot spots and tail latency spikes. The distinction follows from: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point.
Increasing rack density creates hot spots and tail latency spikes. That is the risk in the reported situation—A data center growth plan adds many racks but the existing three-tier core is oversubscribed. The corrective action is: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. Technical basis: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point.
The offered consequence belongs to the alternative control path: Define prechange snapshots, staged checkpoints and objective rollback triggers for each dependency. The relevant failure for the current situation is: Increasing rack density creates hot spots and tail latency spikes. The distinction follows from: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point.
Question 484
A network design team is assessing this customer situation: A data center growth plan adds many racks but the existing three-tier core is oversubscribed. Audit evidence must be retained separately from the devices under change. Which prerequisite should the architect confirm before choosing and defending this design?
Answer & Explanations
Correct answer: D
The offered preparation belongs with the alternative action: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies. Here the necessary starting condition is: Measure east-west traffic, port speed, spine capacity, ECMP support and operational complexity. It supports: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets.
The offered preparation belongs with the alternative action: Restrict VPN import/export using explicit route targets and service-specific policy. Here the necessary starting condition is: Measure east-west traffic, port speed, spine capacity, ECMP support and operational complexity. It supports: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets.
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: Measure east-west traffic, port speed, spine capacity, ECMP support and operational complexity. It supports: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets.
The necessary starting condition is: Measure east-west traffic, port speed, spine capacity, ECMP support and operational complexity. This enables the action: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. Validate the result with: A rack expansion test preserves target bisection throughput and controlled failover behavior.
Question 485
In a separate customer architecture review, this issue arises: An application platform wants predictable east-west bandwidth as server pods expand. Capacity forecasts include a planned period of rapid site expansion. Which high-level network design choice most directly meets the stated technical and operational requirement?
Answer & Explanations
Correct answer: A
Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. The relevant technical reason is: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point. Confirm through: A rack expansion test preserves target bisection throughput and controlled failover behavior.
The alternative addresses a different technical concern: Explicit go/no-go measurements allow reversible progress before hidden state diverges too far. The governing mechanism here is: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point. Accordingly, use: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets.
Reachability should reflect differentiated business constraints, not a single cheapest route for all traffic. That supports the alternative intervention: Translate data classification and service ownership into explicit path and segmentation policy. The present situation—An application platform wants predictable east-west bandwidth as server pods expand—instead calls for: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. Technical basis: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point.
The alternative addresses: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies. Its principle is: EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state. In this case the needed action is: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. Confirm by: A rack expansion test preserves target bisection throughput and controlled failover behavior.
Question 486
In a separate customer architecture review, this issue arises: An application platform wants predictable east-west bandwidth as server pods expand. Capacity forecasts include a planned period of rapid site expansion. Which acceptance result would most convincingly demonstrate that the design addresses the critical requirement?
Answer & Explanations
Correct answer: B
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 rack expansion test preserves target bisection throughput and controlled failover behavior. The scenario is: An application platform wants predictable east-west bandwidth as server pods expand.
Direct verification: A rack expansion test preserves target bisection throughput and controlled failover behavior. This is the relevant evidence for the action: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. The reason is: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point. The scenario is: An application platform wants predictable east-west bandwidth as server pods expand.
The offered observation would test: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies. It would not establish that the stated requirement has been met. The direct evidence needed here is: A rack expansion test preserves target bisection throughput and controlled failover behavior.
The offered observation would test: Translate data classification and service ownership into explicit path and segmentation policy. It would not establish that the stated requirement has been met. The direct evidence needed here is: A rack expansion test preserves target bisection throughput and controlled failover behavior.
Question 487
In a separate customer architecture review, this issue arises: An application platform wants predictable east-west bandwidth as server pods expand. Capacity forecasts include a planned period of rapid site expansion. Which failure is the most direct risk of taking the tempting design shortcut?
Answer & Explanations
Correct answer: C
The offered consequence belongs to the alternative control path: Partition modules by failure, ownership and change cadence with carefully designed routed boundaries. The relevant failure for the current situation is: Increasing rack density creates hot spots and tail latency spikes. The distinction follows from: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point.
The offered consequence belongs to the alternative control path: Define prechange snapshots, staged checkpoints and objective rollback triggers for each dependency. The relevant failure for the current situation is: Increasing rack density creates hot spots and tail latency spikes. The distinction follows from: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point. The scenario is: An application platform wants predictable east-west bandwidth as server pods expand.
Increasing rack density creates hot spots and tail latency spikes. That is the risk in the reported situation—An application platform wants predictable east-west bandwidth as server pods expand. The corrective action is: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. Technical basis: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point.
The offered consequence belongs to the alternative control path: Limit access-layer L2 domains and use routed distribution boundaries with edge-loop safeguards. The relevant failure for the current situation is: Increasing rack density creates hot spots and tail latency spikes. The distinction follows from: A Clos topology scales horizontal capacity by adding equal-cost fabric paths rather than funneling traffic through one choke point.
Question 488
In a separate customer architecture review, this issue arises: An application platform wants predictable east-west bandwidth as server pods expand. Capacity forecasts include a planned period of rapid site expansion. Which prerequisite should the architect confirm before choosing and defending this design?
Answer & Explanations
Correct answer: D
The offered preparation belongs with the alternative action: Translate data classification and service ownership into explicit path and segmentation policy. Here the necessary starting condition is: Measure east-west traffic, port speed, spine capacity, ECMP support and operational complexity. It supports: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets.
The offered preparation belongs with the alternative action: Restrict VPN import/export using explicit route targets and service-specific policy. Here the necessary starting condition is: Measure east-west traffic, port speed, spine capacity, ECMP support and operational complexity. It supports: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. The scenario is: An application platform wants predictable east-west bandwidth as server pods expand.
The offered preparation belongs with the alternative action: Define regional route, policy and service boundaries from business geography and data constraints. Here the necessary starting condition is: Measure east-west traffic, port speed, spine capacity, ECMP support and operational complexity. It supports: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets.
The necessary starting condition is: Measure east-west traffic, port speed, spine capacity, ECMP support and operational complexity. This enables the action: Use a scalable leaf-spine fabric with designed ECMP paths and explicit oversubscription targets. Validate the result with: A rack expansion test preserves target bisection throughput and controlled failover behavior. The scenario is: An application platform wants predictable east-west bandwidth as server pods expand.
Question 489
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 high-level network design choice most directly meets the stated technical and operational requirement?
Answer & Explanations
Correct answer: A
EVPN route advertisement can limit flooding and signal endpoint changes through control-plane state. First establish the prerequisite: Check EVPN route type support, MAC mobility sequence, proxy ARP/ND and failure handling. The proposed response is: Use control-plane learned endpoint reachability with bounded mobility and ARP or ND suppression policies. Validation: A VM move is reachable via the new leaf with correct MAC and IP policy and acceptable convergence.
MPLS VPN isolation depends on which VPN routes a PE installs, not only transport label existence. That supports the alternative intervention: Restrict VPN import/export using explicit route targets and service-specific policy. The present situation—An EVPN fabric moves virtual machines between racks but endpoint reachability converges too slowly—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.
The alternative addresses: Design explicit dual-stack or translation points with tested application compatibility and state capacity. Its principle is: Address-family transition requires predictable protocol interworking rather than an assumed transparent conversion. 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.
The alternative addresses a different technical concern: Structured allocation enables summarization and prevents operational renumbering pressure. 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.
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?
Answer & Explanations
Correct answer: B
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.
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.
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.
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.
Cisco Certified Design Expert (400-007) Practice Tests
- Cisco 400-007 Practice Test 47 - 10 Questions (Last Reviewed 03-Oct-2026)
- Cisco 400-007 Practice Test 48 - 10 Questions (Last Reviewed 02-Oct-2026)
- Cisco 400-007 Practice Test 49 - 10 Questions (Last Reviewed 01-Oct-2026)
- Cisco 400-007 Practice Test 50 - 10 Questions (Last Reviewed 30-Sep-2026)
- Cisco 400-007 Practice Test 51 - 10 Questions (Last Reviewed 29-Sep-2026)