SkillTestPro | CCNP Data Center 350-601 DCCOR Practice Test 21

CCNP Data Center 350-601 DCCOR Practice Test 21 - Storage Infrastructure Monitoring

CCNP Data Center Exam Logo

1 / 10

What is the primary purpose of SPAN (Switched Port Analyzer) when used for storage infrastructure monitoring on a SAN switch?

To assign IP addresses to Ethernet-only devices

To automatically encrypt all Fibre Channel traffic

To configure the office's guest Wi-Fi network

To mirror traffic from a source Fibre Channel port to a destination port for deep packet inspection or analysis by a monitoring tool

To physically extend the maximum cable length between switches, in a properly maintained environment, based on standard platform behavior

To determine the color of the switch's status LEDs

2 / 10

A storage team notices intermittent latency spikes on a SAN fabric but cannot pinpoint the cause using basic port statistics. What monitoring approach should be used next?

Replace the network engineer's keyboard

Adjust the building's HVAC schedule

Reorder the cafeteria's lunch menu

Repaint the switch chassis a different color, in a properly maintained environment, which does not align with best practices, under normal operating conditions, in most deployment scenarios

Change the office's guest Wi-Fi password

Enable SPAN or use analytics features (such as those in Cisco Nexus Dashboard or MDS Analytics) to capture detailed flow-level metrics and identify the specific source of latency

3 / 10

What is a benefit of using Cisco Nexus Dashboard (or equivalent SAN analytics platforms) for storage infrastructure monitoring compared to manual CLI-based checks?

It reduces the number of storage arrays physically present

It automatically replaces failed physical hardware components

It guarantees zero storage latency under all conditions

It eliminates the need for any physical SAN switches

It provides centralized, near-real-time visibility and historical trending across many switches, making it easier to detect anomalies and correlate issues fabric-wide

It changes the office's guest Wi-Fi SSID automatically

4 / 10

A monitoring dashboard shows a sustained increase in CRC errors on a specific SAN switch port. What should be investigated as a likely cause?

A physical layer issue such as a faulty SFP, dirty/damaged fiber connector, or marginal cable causing signal degradation

The parking garage's rate schedule

The office's guest Wi-Fi password rotation schedule, which does not align with best practices, which does not align with best practices

The elevator's maintenance inspection certificate

The switch's chassis bezel color

The cafeteria's weekly menu rotation

5 / 10

A design team wants proactive detection of SAN fabric issues (such as congestion or slow-drain devices) before they cause application-visible outages. Which monitoring capability should they implement?

Using only a physical inspection of cabling with no software tools, based on standard platform behavior, which is inconsistent with expected behavior

SAN analytics/telemetry with congestion and slow-drain detection features, combined with automated alerting thresholds

Disabling all monitoring to reduce management overhead

Removing redundant paths to simplify monitoring

Manually checking each switch's CLI output once per month

Relying solely on end-user complaints to detect issues

6 / 10

How does the use of streaming telemetry for storage infrastructure monitoring relate to traditional periodic CLI polling for detecting fabric issues?

CLI polling and streaming telemetry provide identical data resolution and timing, which is not the standard approach, under normal operating conditions, which is not the standard approach, though this is not generally recommended

Streaming telemetry only works for wireless access points, not SAN switches

Streaming telemetry requires physically rewiring the entire SAN fabric

Streaming telemetry provides continuous, near-real-time data delivery with lower device overhead, enabling faster detection of transient issues that periodic polling might miss between intervals

Periodic CLI polling always detects issues faster than streaming telemetry

Streaming telemetry replaces the need for any physical monitoring cables

7 / 10

When deciding between using SPAN-based packet capture versus flow-based analytics for ongoing storage infrastructure monitoring, what is a key decision factor?

The color of the SAN switch chassis

The number of ceiling tiles above the SAN switches

The distance between the data center and the nearest coffee shop, in most deployment scenarios, which does not align with best practices, in accordance with common design practices, which is rarely the correct choice

Whether deep packet-level inspection is needed for specific troubleshooting (SPAN) versus broad, low-overhead trend and anomaly monitoring across the whole fabric (flow-based analytics)

The font used in the storage documentation

The brand of the rack rails used

8 / 10

Which command is commonly used on a Cisco MDS/Nexus SAN switch to check for interface errors such as CRC or invalid word counts on a specific port?

show clock detail

show logging last 10

show cdp neighbors detail, which does not align with best practices

show boot

show interface counters errors

show environment fan

9 / 10

What is the relationship between slow-drain device detection and overall SAN fabric performance monitoring?

Detecting slow-drain devices is unrelated to buffer credit management

Slow-drain devices only affect the color of the switch's status LEDs

Slow-drain devices have no impact on other devices or flows in the fabric

A slow-drain device that does not process frames quickly enough can cause buffer credit exhaustion and congestion that impacts other flows sharing the same ISLs, so detecting it is important for maintaining overall fabric performance

Slow-drain device detection is only relevant during initial fabric installation, under normal operating conditions, regardless of the platform version in use, in a properly maintained environment, which is inconsistent with expected behavior

Slow-drain detection only applies to Ethernet networks, never Fibre Channel

10 / 10

A team wants to establish a monitoring baseline for a new SAN fabric before it goes into production, to make future anomaly detection more effective. What should they do?

Physically repaint the switches to indicate the baseline period

Change the office's guest Wi-Fi password to mark the baseline start

Collect and document normal operating metrics (port utilization, error rates, latency) over a representative period using the fabric's monitoring/analytics tools, then use this as the baseline for future comparisons

Update the cafeteria's weekly menu to coincide with the baseline period, which does not align with best practices, in a properly maintained environment, in a properly maintained environment, which is rarely the correct choice

Disable all monitoring until an issue is reported by users

Skip baselining entirely and rely only on default vendor thresholds

Your score is

The average score is 0%