400-007 Exam Dumps - Cisco Certified Design Expert (CCDE v3.1)

In 802.1d STP, convergence is influenced by hello timer, max_age, and forward_delay.

While hello_timer typically remains at 2 seconds, lowering max_age (default 20s) and forward_delay (default 15s) can speed up convergence.

Forward_delay controls the time spent in listening and learning states; max_age determines how long a BPDU is considered valid before recalculating topology.

Why other options are incorrect:

A, B, D: These timers (transit_delay, bpdu_delay, maximum_transmission_halt_delay) are not directly adjustable parameters in 802.1d implementations.

—

B (Encrypt data when it is at rest and in motion): In hybrid cloud deployments, encryption is one of the most critical mechanisms to protect sensitive enterprise data both during storage (at rest) and while being transmitted (in motion). This ensures confidentiality and integrity across both private and public cloud environments.

Other options explained:

A: Using standard protocols is a general best practice but insufficient without encryption.

C: Communication of risks is part of compliance but does not enforce technical security.

D: Using standard protocols without encryption exposes data to risks.

—

B (East-West API between controllers):In multicontroller SDN architectures, East-West APIs allow controllers to synchronize state, policies, and tasks, enabling distributed control while presenting a unified control plane view. This ensures that tasks can be performed on any controller consistently.

Other options explained:

A: Root controllers are not standard in modern SDN distributed architectures.

C: Physical connectivity alone doesn ' t synchronize state or tasks.

D: OpenFlow governs switch forwarding, not controller-to-controller interaction.

The issue described is classic route flapping, where a single unstable prefix (10.1.5.0/24) causes repeated route withdrawals and advertisements, triggering churn in the BGP control plane across the entire network. This behavior can be mitigated using the following scalable and non-disruptive design approach:

D. Route Aggregation: Aggregating routes at the edge router (in this case, the LA router) means that multiple more specific prefixes (such as 10.1.4.0/24 through 10.1.7.0/24) are advertised as a single summarized prefix (e.g., 10.1.4.0/22). As a result, the instability of 10.1.5.0/24 will not affect upstream routers (Chicago and New York), as they will only see the aggregated route.

Key benefits aligned with CCDE v3.1 design guidance:

Isolates flapping to the edge while maintaining reachability

Reduces control plane churn in BGP

Preserves scalability and simplifies the routing table in upstream routers

Why other options are incorrect:

A (Route dampening): While effective, route dampening is less favored today due to convergence delay and side effects; it’s also a reactive measure versus a design-based solution.

B and C (Filtering): Filtering the route prevents reachability to that subnet, which violates availability requirements and causes data black-holing.

Thus, aggregation is the most scalable, nondisruptive, and design-aligned choice in this context.

C (SPF hold time): Controls the minimum amount of time between Shortest Path First (SPF) recalculations in link-state protocols like OSPF and IS-IS. This mechanism prevents frequent SPF runs due to rapid or transient topology changes, providing stability.

Other options explained:

A: Transmit delay affects LSA propagation but not routing protocol recalculation timing.

B: Throttle timers are related but primarily control LSA generation intervals.

D: Interface dampening suppresses flapping i

—

Let’s calculate total 1-year cost for each option using the provided table:

DWDM over dark fiber:

CAPEX = $250,000

OPEX (1 year) = $100,000

Installation fee = $30,000

Total = $250,000 + $100,000 + $30,000 = $380,000

CWDM over dark fiber:

CAPEX = $150,000

OPEX (1 year) = $100,000

Installation fee = $25,000

Total = $150,000 + $100,000 + $25,000 = $275,000

MPLS wires only:

CAPEX = $50,000

OPEX (1 year) = $80,000

Installation fee = $5,000

Total = $50,000 + $80,000 + $5,000 = $135,000

BUT: MPLS does not allow customer-controlled QoS policies as stated in the requirement (cannot run its own varying QoS profiles without SP interaction). Therefore disqualified.

Metro Ethernet:

CAPEX = $45,000

OPEX (1 year) = $100,000

Installation fee = $5,000

Total = $45,000 + $100,000 + $5,000 = $150,000

BUT: Metro Ethernet is also typically a service provider-managed solution where customer-controlled QoS is usually limited depending on SP capabilities. May not fully meet the requirement.

—

The key technical requirement:

“Be able to run its own varying QoS profiles without service provider interaction.”

This clearly favors dark fiber solutions (CWDM and DWDM), as these give full Layer 1 control to the customer, allowing complete freedom in managing QoS, traffic engineering, and prioritization internally.

Among the two dark fiber options, CWDM over dark fiber is the most cost-effective choice for one year at $275,000.

—

Therefore, final correct answer: