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

Question 241. Which protocol does gNMI use as its transport

1. NETCONF
2. gRPC
3. RESTCONF
4. SNMP

Correct Answer: 2. gRPC

Explanation:

gNMI uses gRPC as its transport protocol for model driven management and telemetry operations. Cisco NX OS supports gNMI on supported Nexus platforms so external applications can interact with device information through structured interfaces. gNMI uses YANG modeled data and can provide operations such as capabilities discovery, retrieving information, changing configuration, and subscribing to telemetry updates depending on the platform and release. This approach is useful for scalable automation because applications can work with structured data instead of parsing traditional command output.

Question 242. Which gNMI operation lets a collector request streaming updates

1. Delete
2. Commit
3. Copy
4. Subscribe

Correct Answer: 4. Subscribe

Explanation:

The gNMI Subscribe operation allows an external application to request telemetry information from a network device. Cisco NX OS supports subscription behavior where a collector can select the telemetry paths it needs rather than receiving every available data element. Depending on the subscription type, the switch can provide current values once or continue streaming updates. This selective model can reduce unnecessary data transfer and processing compared with repeatedly polling large collections of counters through traditional management protocols. gNMI also supports other remote operations on supported Nexus releases, including Capabilities, Get, and Set.

Question 243. Which telemetry model allows an application to connect to the switch and request data

1. Dial in
2. Dial out
3. Broadcast
4. Flooding

Correct Answer: 1. Dial in

Explanation:

In a dial in telemetry model, the collector or management application initiates the connection toward the network device. Cisco describes gNMI as supporting dial in subscriptions on Nexus switches. The application connects to the switch, discovers supported capabilities, and subscribes to the specific telemetry information it requires. This differs from traditional dial out telemetry, where the network device initiates the connection and pushes information toward a configured collector. Dial in operation can be useful when the monitoring system needs direct control over what information it requests and when subscriptions are created or changed.

Question 244. In dial out telemetry who initiates the connection

1. DNS server
2. Collector
3. Network device
4. Storage array

Correct Answer: 3. Network device

Explanation:

With dial out telemetry, the network device initiates the connection toward a configured telemetry receiver or collector. Cisco NX OS model driven telemetry can push selected operational information continuously according to configured subscriptions. This differs from dial in operation, where the external application connects to the network device and requests data. Streaming telemetry can provide faster and more efficient operational visibility than repeated command or SNMP polling because updates can be delivered according to subscription parameters. Designers should consider collector availability, transport security, data volume, and network reachability when selecting a telemetry architecture.

Question 245. What does an NX OS telemetry sensor group define

1. Data paths to monitor
2. Fabric power limits
3. Server boot order
4. Fibre Channel zones

Correct Answer: 1. Data paths to monitor

Explanation:

A sensor group defines the data paths that the telemetry system should monitor and stream. Cisco NX OS telemetry configuration uses sensor groups to identify the operational or configuration data of interest. A separate destination group identifies where the information should be sent, while a subscription ties the sensor information and destination together. This modular structure allows administrators to reuse the same sensor definitions with different collectors or apply different sampling behavior. YANG based paths can be used so monitoring is based on structured data models rather than unstructured command output.

Question 246. What does an NX OS telemetry destination group define

1. YANG schema version
2. Telemetry receiver information
3. Server BIOS policy
4. VSAN membership

Correct Answer: 4. Telemetry receiver information

Explanation:

A destination group identifies where Cisco NX OS should send telemetry information. It can define the receiver address, port, protocol, encoding, and other transport related characteristics supported by the software release. Sensor groups separately define the data being monitored, and subscriptions connect those sensor paths to destination groups. Separating data selection from collector configuration makes telemetry designs easier to reuse and modify. An organization can send the same operational data to different analysis systems or direct different sensor groups to specialized collectors according to monitoring requirements.

Question 247. What connects a telemetry sensor group to a destination group

1. VRF
2. Subscription
3. VSAN
4. Zone set

Correct Answer: 2. Subscription

Explanation:

A telemetry subscription ties together the data defined in a sensor group and the collector defined in a destination group. The subscription can also include parameters such as the sampling interval according to the selected telemetry method. This allows administrators to define what data should be collected, where it should be sent, and how frequently the information should be produced. Cisco NX OS telemetry uses this structured configuration so monitoring designs can be changed without rebuilding every component. Subscriptions support scalable operational visibility across large data center switch deployments.

Question 248. Which open data model is supported by NX OS telemetry

1. COBOL
2. SQL
3. OpenConfig
4. HTML

Correct Answer: 3. OpenConfig

Explanation:

Cisco NX OS model driven telemetry supports OpenConfig YANG models in addition to Cisco device specific YANG models on supported releases. OpenConfig provides vendor neutral data models intended to create more consistent automation and telemetry workflows across equipment from different vendors. This can reduce the amount of platform specific code required by management systems. Cisco also retains device specific models for features that require deeper platform capabilities. Designers can therefore choose the model that best matches portability, functionality, and operational requirements for the automation or monitoring platform being deployed.

Question 249. What is a benefit of streaming telemetry compared with repeated polling

1. More timely operational updates
2. Removes all collectors
3. Eliminates routing
4. Disables YANG

Correct Answer: 4. More timely operational updates

Explanation:

Streaming telemetry can provide operational updates continuously or at defined intervals without requiring a management station to repeatedly poll the switch for the same information. This can improve visibility into rapidly changing conditions and reduce the overhead associated with repeated request and response cycles. Cisco NX OS supports structured model driven telemetry using YANG based data and several transport and encoding options. The design is particularly valuable in large data centers where traditional polling can become inefficient as the number of devices and monitored variables grows. Collector capacity and telemetry volume should still be planned carefully.

Question 250. Which UCS backup type is intended for disaster recovery

1. Logical configuration
2. Full state
3. System configuration
4. All configuration

Correct Answer: 1. Full state

Explanation:

A Full State backup is the Cisco UCS Manager backup type intended for complete disaster recovery. It creates a binary snapshot of the entire system that can be used to restore or rebuild the original Fabric Interconnect configuration or recreate it on another supported Fabric Interconnect. Cisco distinguishes this backup from XML based configuration exports, which can be imported but are not used for full system restoration. A Full State backup should therefore form part of a UCS disaster recovery plan, especially before significant infrastructure maintenance or configuration changes.

Question 251. What file format does a UCS Full State backup use

1. JSON
2. Binary
3. YAML
4. CSV

Correct Answer: 3. Binary

Explanation:

Cisco UCS Manager creates a Full State backup as a binary file containing a snapshot of the complete system state. The file is designed for restore operations rather than ordinary configuration import. Cisco specifically distinguishes this format from All Configuration, System Configuration, and Logical Configuration backups, which are XML files intended for import workflows. The Full State format provides the information necessary to rebuild a UCS Manager environment during disaster recovery. Administrators should store backup files securely and ensure they are available independently of the infrastructure that may need to be recovered.

Question 252. What format does an All Configuration UCS backup use

1. Binary
2. Plain text
3. XML
4. SQL

Correct Answer: 2. XML

Explanation:

An All Configuration backup in Cisco UCS Manager is created as an XML file. It contains both system configuration and logical configuration settings and can be imported into the original Fabric Interconnect environment or another supported Fabric Interconnect. Cisco notes that this file is not used as a full system restore file. That distinction belongs to the Full State backup. All Configuration exports are useful when administrators want to recreate or transfer configuration while maintaining a human readable structured representation of the system and logical configuration objects.

Question 253. Which UCS backup includes usernames roles and locales

1. System configuration
2. Logical configuration
3. Full state only
4. Firmware backup

Correct Answer: 1. System configuration

Explanation:

A System Configuration backup contains system level UCS Manager settings such as usernames, roles, and locales. Cisco creates this backup as an XML file that can be imported into the original Fabric Interconnect environment or another supported system. It is not used for a complete disaster recovery restore. Logical objects such as service profiles, VLANs, VSANs, pools, and policies belong to the Logical Configuration backup instead. Separating system configuration from logical configuration allows administrators to back up and transfer only the portions of UCS configuration needed for a particular operational task. (cisco.com)

Question 254. Which UCS backup contains service profiles VLANs VSANs pools and policies

1. Full state only
2. User database
3. Logical configuration
4. System configuration

Correct Answer: 4. Logical configuration

Explanation:

The Logical Configuration backup contains logical UCS Manager objects such as service profiles, VLANs, VSANs, identity pools, and policies. Cisco creates this backup as an XML file and allows it to be imported into the original system or another supported Fabric Interconnect environment. It does not provide a complete disaster recovery system restore. This backup is useful when administrators want to reproduce logical server, LAN, and SAN configuration without necessarily importing system administration settings such as local users, roles, and locales.

Question 255. Which UCS backup types can be scheduled

1. System and Logical only
2. Full State and All Configuration
3. Logical and Firmware only
4. Full State only

Correct Answer: 3. Full State and All Configuration

Explanation:

Cisco UCS Manager supports scheduled backup policies for Full State and All Configuration backups. Other backup types can be created manually but are not supported by the same scheduled backup mechanism. Scheduling Full State backups provides regular disaster recovery snapshots, while scheduling All Configuration backups creates recurring XML exports of the complete logical and system configuration. Automated backup scheduling reduces the risk that administrators discover after a failure that their most recent usable configuration backup is outdated. Backup files should also be stored somewhere independent from the UCS domain being protected.

Question 256. What software requirement applies when restoring a UCS Full State backup

1. The software version must match
2. Any version can be used
3. Only a newer version is allowed
4. Only a lower version is allowed

Correct Answer: 2. The software version must match

Explanation:

Cisco states that a Full State backup can be used to restore a UCS system only when the target is running the same software version as the system from which the backup was created. This protects against incompatibilities between internal data structures and configuration formats across different UCS Manager releases. Cisco also notes that the relevant software bundles associated with the backup should remain available. Administrators should therefore coordinate software lifecycle management with backup retention and verify recovery procedures before depending on a Full State file during an actual disaster.

Question 257. What is the default MDS policy for devices not placed in an explicit zone

1. Permit
2. Read only
3. Deny
4. Broadcast only

Correct Answer: 4. Deny

Explanation:

Cisco MDS uses a default zone policy that denies communication among devices that are not members of an explicitly configured zone. This provides a secure default posture because newly attached or unzoned devices do not automatically gain access to one another. Administrators can change the default zone policy to permit, but Cisco documents deny as the factory default. Explicit zoning is generally preferred because it limits communication to known initiator and target relationships and reduces unnecessary visibility among SAN devices. Consistent default zone policy is also important when several switches participate in the same VSAN.

Question 258. Which MDS zoning database is distributed by default

1. Active zone set only
2. Full database only
3. Startup database only
4. No zoning database

Correct Answer: 1. Active zone set only

Explanation:

Cisco MDS distributes only the active zone set by default. The full zoning database is not distributed to every switch unless full zone set distribution is explicitly enabled. The active zone set represents the zoning policy currently enforced in the VSAN, while the full database can contain additional zones and zone sets that are being prepared for future activation. Understanding this distinction is important when administrators manage zoning from several switches because a device may know the active configuration without automatically receiving every unactivated zoning object defined elsewhere.

Question 259. What must occur before changes in the full MDS zoning database become active

1. Server reboot
2. Zone set activation
3. FSPF restart
4. VSAN deletion

Correct Answer: 2. Zone set activation

Explanation:

Changes made to the full MDS zoning database do not affect production traffic until the appropriate zone set is activated. The active database represents the zoning configuration currently enforced in the VSAN. Administrators can therefore create or modify zones and zone sets in the full database before deciding when those changes should become operational. Activating a zone set updates the active zoning database across the fabric according to the configured distribution behavior. This separation gives SAN administrators a controlled workflow for preparing changes before they affect communication between hosts and storage targets. 

Question 260. What is the default state of enhanced zoning on Cisco MDS

1. Enabled
2. Mandatory
3. Disabled
4. Read only

Correct Answer: 3. Disabled

Explanation:

Cisco documentation lists enhanced zoning as disabled by default. Basic zoning is therefore the normal starting mode unless administrators explicitly enable enhanced zoning. Enhanced zoning introduces additional coordination and configuration controls that can help maintain consistent zoning management across a Fibre Channel fabric. Because zoning information is critical to storage access, changes to zoning mode should be planned carefully and applied consistently across participating switches. Administrators should also confirm that all switches in the VSAN support the intended zoning behavior before changing the operational mode in a production SAN.