Free Practice Questions for Cisco 400-007 Exam

FCoE (Fibre Channel over Ethernet) requires a lossless Ethernet transport, typically achieved using Data Center Bridging (DCB) features such as Priority Flow Control (PFC). Only technologies that can preserve Ethernet frames end-to-end and support lossless characteristics can properly carry FCoE:

A. DWDM (Dense Wavelength Division Multiplexing): Operates at the physical layer and is transparent to Ethernet, preserving frame integrity and lossless characteristics across long distances.

B. EoMPLS (Ethernet over MPLS): Carries Ethernet frames directly over MPLS and can be engineered to support low-loss, low-latency transport appropriate for FCoE.

Why other options are incorrect:

C. SONET/SDH encapsulates Ethernet but is not suitable for FCoE due to differences in timing and buffering.

D. Multichassis EtherChannel over pseudowire may introduce additional control plane complexity and loss characteristics.

E. VPLS introduces MAC learning, flooding, and buffering behaviors that can cause frame loss, which is not compatible with FCoE requirements.

—

The performance degradation is caused by output queue drops on the 1 Gbps server port. Increasing the queue size allows more data to be buffered during transient congestion periods, preventing packet loss and retransmissions which significantly degrade iSCSI performance.

iSCSI is sensitive to packet loss due to its reliance on TCP.

Increasing the queue depth is a simple, cost-effective method to absorb bursts.

Changing to CIFS (A) is irrelevant since CIFS would suffer similar TCP congestion.

WRED (C) intentionally drops packets during congestion, which is undesirable here.

Enabling TCP Nagle (D) would likely introduce latency and reduce throughput for large data transfers.

—

Control plane hardening is a critical aspect of securing infrastructure devices. Recommended measures include:

A. Routing protocol authentication: Prevents unauthorized devices from injecting false routes by requiring secure key-based authentication (e.g., MD5 or SHA for OSPF/BGP).

B. SNMPv3: Provides secure management through authentication and encryption, preventing interception or modification of SNMP traffic.

C. Control Plane Policing (CoPP): Enforces rate limits and filtering for traffic directed to the device ' s CPU, protecting against DoS and control plane overloads.

Why other options are incorrect:

D. Redundant AAA servers support authentication resilience but are more about access control than direct control plane protection.

E. Warning banners are a legal and administrative best practice, not a technical control plane defense.

F. Enabling unused services is the opposite of best practices and increases the attack surface.

These control-plane protections are emphasized in CCDE v3.1 design guidance for resilient and secure infrastructure designs.

A (Roaming delay):Voice requires seamless roaming with minimal handoff delay to avoid call drops.

B (Uniform radio coverage):Consistent signal coverage is essential for maintaining voice call quality throughout the facility.

Other options explained:

C: High channel utilization affects capacity but not directly the initial readiness assessment.

D: Latency is important but typically captured during ongoing performance testing, not pre-assessment.

E: TX power changes indicate instability but are not primary readiness criteria.

Comprehensive and Detailed Explanation:

Central command and control refers to a unified, centralized security policy and management platform that integrates and coordinates all security components—regardless of physical location or form factor (virtual, physical, cloud). It streamlines operations, reduces overhead, and improves visibility and control.

D is correct because central control simplifies policy enforcement and visibility.

A (threat-centric protection) focuses more on response and defense rather than architecture.

B (integrated actionable intelligence) refers to threat feeds, not central management.

C (distributed enforcement) is an implementation strategy, not a management component.

==========

FCAPS stands for Fault, Configuration, Accounting, Performance, and Security.

D (Authentication) is not a management category within the FCAPS framework.

Authentication is part of security functions but not a standalone FCAPS category.

Why other options are correct FCAPS components:

A: Configuration management

B: Security management

C: Performance management

E: Fault management

—

Cisco SD-WAN Cloud OnRamp SaaS optimizes cloud application performance by dynamically measuring SaaS application paths from multiple branch edges toward the Microsoft 365 cloud.

It automatically selects the best-performing path, continuously monitors SLA metrics (latency, loss, jitter), and dynamically reroutes based on real-time performance.

This directly addresses SaaS resiliency across multiple ISPs with minimal manual intervention and is aligned with CCDE v3.1 SD-WAN design methodologies for SaaS optimization.

Why other options are incorrect:

A: Cloud OnRamp gateway is for IaaS optimization (AWS, Azure), not SaaS.

B: Cloud OnRamp SWG (Secure Web Gateway) is for internet-bound security inspection, not SaaS path optimization.

C: " Cloud OnRamp " alone is too general; SaaS is the specific solution for this SaaS use case.

STP Bridge Assuranceis a mechanism used to protect againstunidirectional link failureson point-to-point STP connections in environments likeRapid PVST+ and MST. When Bridge Assurance is enabled, BPDUs are expected on all BPDUs-capable interfaces. If a switch stops receiving BPDUs on a point-to-point link where Bridge Assurance is enabled, it assumes the link has failed and transitions the port to blocking to prevent a loop.

This is especially useful in high-availability enterprise designs that require protection from unexpected switch behavior or partial link failures.

Why other options are incorrect:

A. BPDU Guard: Protects access ports by placing them in an err-disabled state if BPDUs are received—useful at the edge, not for core loop protection.

C. MSTP: Refers to the protocol itself but does not solve the unidirectional link issue on its own.

D. TRILL: A different architecture (layer 2 routing) and not applicable to Rapid PVST+ or MST-specific protection.