Cisco Updated 400-007 Exam Questions and Answers by aysha

C (PIM Sparse Mode with RP located at the hub):DMVPN networks typically leverage sparse mode multicast due to their efficiency in dynamic topologies. Locating the Rendezvous Point (RP) at the hub simplifies multicast state management, since the hub serves as the central aggregation point and ensures optimal rendezvous functionality without requiring complex RP placement across spokes.

Other options explained:

A: Dense mode is inefficient and generates unnecessary flooding, especially in WAN environments.

B/D: Placing RPs at remote sites introduces unnecessary complexity and operational challenges.

C (More consistent device configuration):Centralized control allows uniform policy application, eliminating configuration drift across devices.

E (Configure features at network-level rather than device-level):Controller-based networks abstract network services from individual devices, enabling network-wide configuration from a single source of truth.

Other options explained:

A: Forwarding tables still exist in both architectures.

B: Traditional networks offer per-device flexibility; controllers abstract this.

D: APIs are usually provided at controller level, not per device.

The SDN architecture separates the control plane from the data plane. In this model, the SDN controller is the central element responsible for:

Receiving application intent via northbound APIs

Translating intent into traffic policies

Communicating with infrastructure devices using southbound APIs

The SDN controller enforces policies such as path selection, QoS, and access control rules across the network fabric, ensuring traffic flows align with administrator-defined logic. Neither northbound nor southbound APIs enforce policy themselves; they serve as communication interfaces.

The packet forwarding engine (Option A) simply performs data-plane functions based on instructions, but does not interpret or apply policies.

==========

—

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: