Cisco 350-601 Practice Test - Questions Answers, Page 13

When a Cisco Nexus 9000 series switch encounters a startup configuration corruption, the recovery process involves clearing the current configuration, restarting the device, and then restoring the configuration from a previously saved file. The correct sequence is to first clear the configuration to prevent the corrupted startup configuration from loading upon restart. After restarting the device, the previously saved configuration file should be copied to the running configuration. Finally, to ensure the switch starts with the correct configuration in future restarts, the running configuration should be saved to the startup configuration.

The requirement for the data center servers to reach services in the cloud and services behind redistributed routes, along with the condition that the exit point toward the internet should only be propagated when there is a dynamically learned default route, necessitates the use of the 'default-information originate' OSPF feature. This feature allows the advertisement of the default route in OSPF when it is present in the routing table, which is the case when it is dynamically learned from the upstream router.

https://learningnetwork.cisco.com/s/question/0D53i00000Kt544/defaultinformationoriginate-always

A characteristic of the install all command on the Cisco Nexus series switch is that it automatically checks the image integrity before performing the installation. The install all command is used to install a system image and kickstart image on the switch, as well as to upgrade the BIOS and other firmware components. The install all command performs a series of checks and validations before installing the images, such as verifying the compatibility, checksum, and signature of the images. This ensures that the images are not corrupted or tampered with, and that they match the hardware and software requirements of the switch. The install all command also performs a backup of the current configuration and images, and allows the user to abort the installation process if needed.Reference:=

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 3: Data Center LAN Network Connectivity, Lesson 3.4: Cisco Nexus 9000 Series Switches

Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 9.3(x), Chapter: Installing Software Images and EPLDs, Section: Installing System and Kickstart Images

The correct data structure to use within a POST message to receive a login token when configuring the Cisco APIC via REST API calls is an XML payload that includes thetags with nested<name>andtags for the username and password. This structure is shown in Option A, which is the standard format for authentication requests to the Cisco APIC.

The impact of the EPLD update of the supervisor module on the Cisco MDS 9000 switches is that the redundant supervisor takes over while the EPLD update is in progress and there is no service disruption. EPLD (Electronic Programmable Logic Device) is a firmware component that controls the functionality of various hardware modules on the switch, such as the supervisor, line cards, and fabric modules. The EPLD update is performed to enhance the performance and features of the hardware modules, and to fix any bugs or issues. The EPLD update process requires a reload of the affected module, which can cause a temporary loss of connectivity and traffic. However, if the switch has a redundant supervisor module configured in high availability mode, the EPLD update can be performed without any service disruption. This is because the redundant supervisor takes over the control plane functions while the active supervisor is being updated, and then switches back to the active supervisor when the update is completed. The EPLD update does not affect the data plane traffic, as the line cards and fabric modules continue to forward packets during the update process.Reference:=

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 7: Data Center Storage Connectivity, Lesson 7.3: Fibre Channel Protocol

Cisco MDS 9000 Family NX-OS System Management Configuration Guide, Chapter: Installing Software Images and EPLDs, Section: Updating EPLDs

When configuring an Intersight virtual application and claiming targets, the information required in the comma-separated value (CSV) file for provisioning includes the target type, hostname or IP address, user name, and password. This set of information is necessary to uniquely identify and authenticate each target for the claim process.

NFSv4 offers several advantages over Fibre Channel protocol, one of which is improved security. NFSv4 is designed to be more secure than its predecessors, providing strong security features that are not inherent in Fibre Channel. It includes mechanisms for authentication, integrity, and privacy, which are part of its standard protocol suite. NFSv4 also integrates well with security infrastructures like Kerberos, allowing for secure, authenticated access to file systems over a network.

The Cisco UCS firmware Auto Sync Server policy includes several configuration settings that determine how and when firmware on servers is synchronized. The two available settings from the options provided are 'User Acknowledge' and 'No Action'. 'User Acknowledge' requires an administrator to manually acknowledge firmware upgrades in the Pending Activities dialog box before they are applied. 'No Action' means no firmware upgrade is initiated on the server. These settings allow administrators to control the firmware synchronization process according to their operational policies and procedures.

The DCNM performance monitoring configuration parameter that must be implemented to achieve the result of triggering events when monitored traffic exceeds the configured percent utilization threshold is the Util% parameter. This parameter allows the administrator to set a utilization threshold as a percentage, which, when exceeded, triggers an event. The requirement to configure a maximum limit of 39860437 bytes directly relates to the statistics collected as a ratio of the total link capacity, which is effectively managed by setting the Util% parameter. This parameter is part of the Performance Manager Configuration Wizard in DCNM, which provides the ability to set up two thresholds that trigger events when the monitored traffic exceeds the percent utilization configured.These thresholds can be set as either Critical or Warning events that are reported on the DCNM-SAN web client Events browser page1.