View Full Cisco CCNP Data Center 300-610 Exam Dumps and Practice Test Dumps.

Question 321. What does an Intersight IPMI over LAN Policy control

1. VXLAN routing
2. Remote IPMI server access
3. Fibre Channel zoning
4. ACI contracts

Correct Answer: 2. Remote IPMI server access

Explanation:

An IPMI over LAN Policy controls whether the IPMI service is available over the network on supported UCS servers. The policy can define settings such as the privilege level and optional encryption information used for remote server management. IPMI is an out of band management technology, so administrators can use it for server control functions without depending on the operating system running normally. Intersight centralizes these settings through reusable server policies, helping organizations apply consistent management access requirements across several servers instead of configuring each CIMC endpoint separately.

Question 322. What does an Intersight Serial over LAN Policy provide

1. Fibre Channel tunneling
2. VXLAN encapsulation
3. GPU console access only
4. Remote serial console access**

Correct Answer: 4. Remote serial console access

Explanation:

A Serial over LAN Policy enables remote access to a server serial console across the network. Cisco Intersight can configure this service on supported UCS servers so administrators can access serial input and output without being physically connected to the server. The console can be reached through supported remote management methods such as SSH. This can be useful for operating system troubleshooting, boot diagnostics, and recovery when normal graphical management is unavailable. Intersight allows organizations to standardize Serial over LAN configuration through reusable server policies rather than setting each server independently.

Question 323. What does an Intersight Network Connectivity Policy primarily configure for server management

1. DNS settings
2. RAID groups
3. VXLAN VNIs
4. Fibre Channel zones

Correct Answer: 1. DNS settings

Explanation:

The Intersight Network Connectivity Policy configures DNS related settings used by the management interface on supported UCS systems. Administrators can define preferred and alternate DNS servers, obtain DNS server information through DHCP, enable IPv6 DNS settings, and configure Dynamic DNS when supported. Dynamic DNS can update DNS resource records using the current hostname, domain, and management address. Centralizing these settings helps provide consistent name resolution for server management interfaces and simplifies large deployments where many servers need identical DNS behavior.

Question 324. What does an Intersight NTP Policy provide

1. Storage multipathing
2. Link aggregation
3. Time synchronization
4. Server zoning

Correct Answer: 3. Time synchronization

Explanation:

An Intersight NTP Policy provides time synchronization for supported servers and infrastructure endpoints. Administrators can specify NTP server addresses or hostnames and configure the appropriate time zone. Accurate time is important for logs, authentication, security certificates, troubleshooting, and event correlation across a data center. Cisco supports multiple NTP servers so the management environment can maintain time even if one source becomes unavailable. When an NTP hostname is used, the appropriate DNS information must also be configured so the endpoint can resolve the server name successfully.

Question 325. What does an Intersight Local User Policy define

1. VXLAN routes
2. Local server management accounts
3. Storage LUN masking
4. BGP neighbors

Correct Answer: 2. Local server management accounts

Explanation:

A Local User Policy defines local user access for supported UCS servers managed through Intersight. Administrators can create a reusable policy containing the local accounts that need to exist on a server and apply that policy through server profiles. This helps maintain consistent administrative access across many systems while reducing manual account configuration. Local users are particularly useful when external authentication services are unavailable or when emergency management access must remain possible. Organizations should combine local accounts with appropriate password, privilege, and operational security policies so local credentials do not become an unnecessary security risk.

Question 326. What does an Intersight LDAP Policy enable

1. Directory based authentication
2. Ethernet congestion control
3. RAID configuration
4. VXLAN routing

Correct Answer: 1. Directory based authentication

Explanation:

An LDAP Policy allows supported UCS management endpoints to use a directory service for authentication and authorization. LDAP directories commonly store user, group, and organizational information that can be referenced when users attempt to access management interfaces. Cisco Intersight can configure secure LDAP access for devices such as Fabric Interconnects so administrators can authenticate through centralized directory services rather than relying only on local accounts. This improves operational consistency and can simplify account lifecycle management because users and groups are maintained centrally in the enterprise directory.

Question 327. What does an Intersight Virtual KVM Policy control

1. Fibre Channel routing
2. RAID rebuild speed
3. BGP timers
4. Remote keyboard video mouse access

Correct Answer: 4. Remote keyboard video mouse access

Explanation:

A Virtual KVM Policy controls remote keyboard, video, and mouse console access to supported UCS servers. The policy can define whether KVM access is enabled, how many concurrent sessions are allowed, which remote port is used, and whether video encryption is required. Remote KVM provides administrators with console level access that resembles sitting directly in front of the server. This is useful for BIOS configuration, operating system installation, boot troubleshooting, and recovery. Intersight allows these settings to be standardized across multiple servers using reusable policies.

Question 328. What does an Intersight Virtual Media Policy allow

1. BGP route injection
2. Fibre Channel trunking
3. Remote media mounting
4. VXLAN flooding

Correct Answer: 3. Remote media mounting

Explanation:

A Virtual Media Policy allows administrators to mount remote installation media or disk images to supported servers. This is commonly used to provide operating system installation media without inserting a physical disk or USB device at the server. Cisco Intersight can define mappings to remote file shares using supported protocols and present ISO or disk images to the server through its management controller. Virtual Media is often used together with Virtual KVM during remote provisioning and recovery. Central policy configuration helps ensure that remote media behavior is consistent across servers.

Question 329. What does an Intersight SNMP Policy primarily configure

1. Monitoring users and traps
2. VXLAN VNIs
3. Storage RAID levels
4. Fabric routing

Correct Answer: 1. Monitoring users and traps

Explanation:

An Intersight SNMP Policy configures SNMP management behavior on supported servers. Cisco supports SNMP versions including SNMPv1, SNMPv2c, and SNMPv3 depending on the managed platform and policy. The policy can define SNMP users and trap destinations so monitoring systems can receive fault and alert information from the managed devices. Applying SNMP configuration through a centralized policy helps operations teams maintain consistent monitoring settings across large server environments. Cisco notes that policy deployment can replace previously configured SNMP users and traps with those defined through Intersight.

Question 330. What does an Intersight SSH Policy configure

1. SAN zoning
2. GPU memory
3. ACI EPGs
4. Secure shell management access**

Correct Answer: 4. Secure shell management access

Explanation:

An Intersight SSH Policy controls the SSH service on supported UCS servers and management endpoints. It can specify whether SSH is enabled, which listener port is used, and how long an idle session can remain open. SSH provides encrypted command line management and is preferred over insecure remote terminal protocols. Standardizing SSH through a reusable policy allows administrators to apply consistent management access settings across multiple systems. Security teams can use this mechanism to control whether SSH is available and align session behavior with organizational management access requirements.

Question 331. What is a slow drain device in a Fibre Channel SAN

1. A device that cannot accept frames fast enough
2. A device with too many VLANs
3. A server with no UUID
4. A switch without BGP

Correct Answer: 2. A device that cannot accept frames fast enough

Explanation:

A slow drain device is an endpoint that does not accept Fibre Channel frames at the expected or negotiated rate. Because Fibre Channel relies on buffer credits for flow control, the transmitting switch can run out of credits while waiting for the slow endpoint. Congestion can then spread backward through shared interswitch links and affect unrelated storage flows. Cisco provides congestion analysis, port monitoring, and slow drain detection features to help identify these devices before their behavior causes widespread application performance problems. Slow drain troubleshooting should focus on tracing congestion toward the actual slow destination.

Question 332. Which counter is especially useful for identifying Fibre Channel transmit congestion

1. CRC only
2. Link reset only
3. TxWait
4. VLAN count

Correct Answer: 3. TxWait

Explanation:

TxWait measures the amount of time a Fibre Channel port is unable to transmit because the necessary buffer credits are unavailable. Cisco uses this counter as an important indicator of congestion and slow drain behavior. TxWait can also be expressed as a percentage over an interval, which helps operations teams understand how severe the congestion is. For example, a higher TxWait percentage means the interface spent more of the interval unable to send frames. Nexus Dashboard Fabric Controller Congestion Analysis displays TxWait information at switch and port level to simplify troubleshooting.

Question 333. What does Buffer to Buffer Credit Recovery correct

1. Lost Fibre Channel credits
2. Missing VLANs
3. Server UUID conflicts
4. BGP route loops

Correct Answer: 4. Lost Fibre Channel credits

Explanation:

Buffer to Buffer Credit Recovery detects and corrects Fibre Channel credit loss that can result from corrupted frames or receiver ready primitives. If a credit is lost and never replenished, available transmit credits can gradually decrease. In a severe case, a port can eventually lose all credits and stop sending frames in that direction. Cisco MDS implements standards based recovery mechanisms that allow directly attached peers to identify discrepancies and restore the missing credits without disrupting normal traffic. This improves SAN resiliency and is especially useful on links where physical errors can occasionally corrupt Fibre Channel primitives.

Question 334. What happens if all Fibre Channel transmit credits are lost

1. Frame transmission stops
2. The switch creates more VLANs
3. BGP restarts
4. The server changes UUID

Correct Answer: 1. Frame transmission stops

Explanation:

Fibre Channel uses Buffer to Buffer credits as a flow control mechanism. Each transmitted frame consumes a credit, and the receiving side returns credit information as it becomes ready for additional frames. If errors cause all available transmit credits to be lost, the sender cannot legally transmit more frames and communication in that direction stops. Cisco Buffer to Buffer Credit Recovery is designed to prevent or correct this condition by detecting lost frame or receiver ready information and restoring the proper credit count between directly connected peers.

Question 335. On which links is Buffer to Buffer Credit Recovery negotiated

1. Between unrelated fabrics
2. Through APIC
3. Between directly attached peer ports
4. Through an IP route reflector

Correct Answer: 3. Between directly attached peer ports

Explanation:

Buffer to Buffer Credit Recovery is a per hop feature negotiated between directly connected Fibre Channel peer ports when the link comes up. The ports exchange the required state change parameters and determine whether both sides support the recovery mechanism. Once operational, the peers can detect lost frames or lost receiver ready primitives and restore the corresponding credits. Because the feature works link by link, every relevant connection must support the mechanism for recovery to operate on that link. Cisco enables the feature by default on several supported MDS port types in modern NX OS releases.

Question 336. What does NDFC Congestion Analysis help identify

1. Server boot order
2. Slow drain conditions
3. ACI contract scope
4. GPU allocation

Correct Answer: 2. Slow drain conditions

Explanation:

Nexus Dashboard Fabric Controller Congestion Analysis helps administrators identify slow drain behavior and related SAN congestion. Cisco provides switch level and port level statistics and can display indicators such as TxWait, drops, credit loss recovery events, over utilization, and port monitor events. The tool presents the information graphically and can display the affected topology so administrators can trace congestion through the fabric. This reduces the amount of manual counter collection required when troubleshooting storage performance problems and can help identify the endpoint that is causing congestion for unrelated flows.

Question 337. Which NDFC metric indicates time spent waiting for transmit credits

1. TxWait
2. UUID usage
3. VLAN count
4. CPU clock

Correct Answer: 1. TxWait

Explanation:

TxWait reflects the time a Fibre Channel port cannot transmit because it lacks the credits required to send another frame. Cisco NDFC uses TxWait and peak TxWait values as major indicators when analyzing slow drain and fabric congestion. A sustained or high TxWait value suggests that downstream congestion is preventing normal frame transmission. Administrators can compare TxWait across switches and ports and then follow the congestion path toward the destination device causing the problem. This makes TxWait one of the most useful SAN troubleshooting measurements for detecting credit related performance issues.

Question 338. What data source does NDFC use for MDS NX OS 9 Fibre Channel performance monitoring

1. Telnet
2. TFTP
3. RADIUS
4. NX API

Correct Answer: 4. NX API

Explanation:

For Cisco MDS 9000 switches running NX OS Release 9 and later, Nexus Dashboard Fabric Controller uses NX API to poll Fibre Channel performance monitoring information. Cisco notes that NDFC automatically enables the NX API feature when necessary for this monitoring workflow. Older MDS releases use SNMP for the equivalent performance data collection. Using NX API provides a modern programmable interface for retrieving operational information and allows NDFC to display SAN performance, congestion, and slow drain statistics centrally. This reduces the need for administrators to gather counters manually from individual switches.

Question 339. What flow control primitive returns a Fibre Channel buffer credit

1. FLOGI
2. R RDY
3. ELS only
4. ARP

Correct Answer: 2. R RDY

Explanation:

Receiver Ready is the Fibre Channel primitive used to signal that the receiving side has buffer capacity available for another frame. When the sender transmits a frame it consumes a Buffer to Buffer credit. Receipt of the appropriate R RDY primitive replenishes that transmit credit. If the R RDY is corrupted or lost, the sender may fail to restore the credit even though the receiver has processed the frame. Cisco Buffer to Buffer Credit Recovery detects this type of discrepancy and can replenish lost credits before the link becomes unable to transmit.

Question 340. What can severe Fibre Channel congestion trigger to restore lost credits

1. DHCP renewal
2. BGP graceful restart
3. Link Credit Reset
4. VXLAN reencapsulation

Correct Answer: 3. Link Credit Reset

Explanation:

Severe Fibre Channel congestion can trigger Credit Loss Recovery using a Link Credit Reset primitive. Cisco describes this behavior when a port remains without credits for a continuous period and the congestion reaches the most severe level. The peer can respond with a Link Credit Reset Response so both directions restore their Buffer to Buffer credit state and normal forwarding resumes. If the response does not arrive or the receiving queue cannot be cleared, the link can fail instead. This mechanism provides a recovery path when normal credit behavior has broken down.