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

NFS (Network File System) is a distributed file system protocol that allows users on client computers to access files over a network in a manner similar to how local storage is accessed. NFS uses a Kerberos-based security model to provide authentication, integrity, and confidentiality of data. It ensures that unauthorized users do not have access and protects the data from eavesdropping and tampering as it moves across the network. The other options are not features of NFS. Role-based access control is a method of restricting access to resources based on the roles of users. Block-based file access is a type of storage access that transfers data in fixed-sized blocks. Zone-based access control is a feature of Fibre Channel SANs that allows traffic isolation within a VSAN.Reference:

Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide, Release 9.3(x) - Configuring NFS [Cisco Nexus 9000 Series Switches], Configuring NFS, NFS Overview

Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide, Release 9.3(x) - Configuring NFS [Cisco Nexus 9000 Series Switches], Configuring NFS, Configuring NFS Security

Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide, Release 9.3(x) - Configuring iSCSI [Cisco Nexus 9000 Series Switches], Configuring iSCSI, iSCSI Overview

Cisco Nexus 9000 Series NX-OS SAN Switching Configuration Guide, Release 9.3(x) - Configuring VSANs [Cisco Nexus 9000 Series Switches], Configuring VSANs, Configuring Zone-Based Access Control

The exhibit shows a process of restoring the configuration of Cisco UCS using a backup file. In this context, the system configuration backup is required to restore the Cisco UCS configuration. The system configuration includes all setup information, policies, pools, templates, service profiles, VLANs/Fabric interconnect configurations etc., which are essential for the operational restoration of Cisco UCS. The other backup types are not suitable for this scenario. The all configuration backup includes the system configuration and the logical configuration, but it also includes the statistics and the faults, which are not needed for the restoration. The logical configuration backup includes the policies, pools, templates, and service profiles, but it does not include the setup information and the VLANs/Fabric interconnect configurations, which are also needed for the restoration. The full state backup includes the entire state of the system, including the firmware versions and the BIOS settings, but it is only used for disaster recovery, not for configuration restoration.Reference:

Cisco UCS Manager Backup and Restore Management Guide, Release 4.0 - Backup and Restore Overview [Cisco UCS Manager], Backup and Restore Overview, Backup Types

Cisco UCS Manager Backup and Restore Management Guide, Release 4.0 - Backup and Restore Overview [Cisco UCS Manager], Backup and Restore Overview, System Configuration Backup

Cisco UCS Manager Backup and Restore Management Guide, Release 4.0 - Backup and Restore Overview [Cisco UCS Manager], Backup and Restore Overview, All Configuration Backup

Cisco UCS Manager Backup and Restore Management Guide, Release 4.0 - Backup and Restore Overview [Cisco UCS Manager], Backup and Restore Overview, Logical Configuration Backup

Cisco UCS Manager Backup and Restore Management Guide, Release 4.0 - Backup and Restore Overview [Cisco UCS Manager], Backup and Restore Overview, Full State Backup

Option A is the correct configuration set to create an EEM script that saves a copy of the running configuration on bootflash and writes a message to syslog when a user saves the configuration to a Cisco Nexus switch. The EEM script uses the event manager applet command to define the applet name and the event that triggers the script. In this case, the event is the CLI pattern ''copy running-config startup-config'' which matches the command that a user would use to save the configuration. The action commands specify the commands that the script will execute when the event occurs. In this case, the script will copy the running configuration to bootflash, write a message to syslog, and exit. The other options have incorrect commands or syntax errors. For example, option B uses the wrong event keyword, option C uses the wrong action keyword, and option D uses the wrong file name.Reference:

Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 9.3(x) - Configuring Embedded Event Manager [Cisco Nexus 9000 Series Switches], Configuring Embedded Event Manager, Configuring EEM Policies Using the CLI

Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 9.3(x) - Configuring Embedded Event Manager [Cisco Nexus 9000 Series Switches], Configuring Embedded Event Manager, Configuring EEM Event Statements

Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 9.3(x) - Configuring Embedded Event Manager [Cisco Nexus 9000 Series Switches], Configuring Embedded Event Manager, Configuring EEM Action Statements

Option C is the correct adjacency server configuration to make two OTV edge devices located in the same site bring up the dual-site adjacency. The adjacency server is a logical entity that maintains the control plane information for the OTV overlay network. The adjacency server can be configured in unicast-only mode, which means that the OTV edge devices use unicast packets to exchange control plane information. To enable dual-site adjacency, which means that the OTV edge devices can form adjacencies with devices in the same site as well as devices in different sites, the adjacency server must be configured with the same IP address on both devices in the same site. The other options have incorrect configurations or IP addresses. For example, option A uses different IP addresses for the adjacency server on the same site, option B uses the same IP address for the adjacency server on different sites, and option D uses an invalid IP address for the adjacency server.Reference:

Cisco Nexus 7000 Series NX-OS OTV Configuration Guide, Release 6.x - Configuring Basic OTV [Cisco Nexus 7000 Series Switches], Configuring Basic OTV, Configuring the OTV Adjacency Server

Cisco Nexus 7000 Series NX-OS OTV Configuration Guide, Release 6.x - Configuring Basic OTV [Cisco Nexus 7000 Series Switches], Configuring Basic OTV, Configuring Dual-Site Adjacency

Cisco Nexus 7000 Series NX-OS OTV Configuration Guide, Release 6.x - Configuring Basic OTV [Cisco Nexus 7000 Series Switches], Configuring Basic OTV, Configuring the OTV Adjacency Server IP Address

To configure multiple EPGs on a single access port in a large Cisco ACI fabric without using VMM integration, the EPGs must be linked to the correct physical domain (Option B) and configured as static ports (Option E). The physical domain is associated with VLAN namespaces and determines the VLAN encapsulation at the interface level. The static ports are used to manually assign the EPGs to the access port. The other options are not required for this configuration. A contract is used to define the communication policy between EPGs, but it is not necessary to create one for this scenario. The EPGs do not link directly to the AAEP, but rather to the interface policy group that is associated with the AAEP. The bridge domains do not need to be configured in legacy mode, which is a mode that allows communication with non-ACI networks.Reference:

Cisco Application Centric Infrastructure Fundamentals, Release 4.x - Endpoint Groups (EPGs) [Cisco Application Centric Infrastructure], Endpoint Groups (EPGs), Physical Domain

Cisco Application Centric Infrastructure Fundamentals, Release 4.x - Endpoint Groups (EPGs) [Cisco Application Centric Infrastructure], Endpoint Groups (EPGs), Static Ports

Cisco Application Centric Infrastructure Fundamentals, Release 4.x - Endpoint Groups (EPGs) [Cisco Application Centric Infrastructure], Endpoint Groups (EPGs), Contracts

Cisco Application Centric Infrastructure Fundamentals, Release 4.x - Endpoint Groups (EPGs) [Cisco Application Centric Infrastructure], Endpoint Groups (EPGs), Attachable Access Entity Profile

Cisco Application Centric Infrastructure Fundamentals, Release 4.x - Bridge Domains [Cisco Application Centric Infrastructure], Bridge Domains, Legacy Mode

Option C is the correct configuration to apply a power redundancy policy on a Cisco UCS C-Series Rack Server that supports two power sources. The power redundancy policy determines how the server uses the available power supplies to optimize power usage. The grid option means that the server uses power from both power supplies simultaneously. If one power supply fails, the server continues to operate with the remaining power supply. The other options are not suitable for this requirement. The n+1 option means that the server uses one fewer power supply than the number of power supplies that are installed. If a power supply fails, the server uses the extra power supply. The non-redundant option means that the server uses only one power supply, regardless of the number of power supplies that are installed. If the power supply fails, the server shuts down. The ps-redundant option means that the server uses power from the most efficient power supply. If the power supply fails, the server switches to another power supply.Reference:

Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration Guide, Release 4.0 - Configuring Server Power [Cisco Integrated Management Controller], Configuring Server Power, Configuring the Power Policy

Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration Guide, Release 4.0 - Configuring Server Power [Cisco Integrated Management Controller], Configuring Server Power, Power Redundancy Modes

The configuration shown in the exhibit indicates that FCIP (Fibre Channel over IP) is configured with ip-compression mode2 enabled on a Cisco MDS 9000 Series switch. This means compression is performed by using software (Option D), as mode2 refers to software-based compression in FCIP configurations. The other options are not correct based on the configuration. The switch does not attempt to make two TCP connections, as there is no tcp-connections command in the configuration. Compression is not performed by using hardware, as mode1 refers to hardware-based compression in FCIP configurations. Mode2 is not enabled by default, as the default mode for FCIP compression is none.Reference:

Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide, Release 8.x - Configuring FCIP [Cisco MDS 9000 NX-OS and SAN-OS Software], Configuring FCIP, Configuring FCIP Compression

Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide, Release 8.x - Configuring FCIP [Cisco MDS 9000 NX-OS and SAN-OS Software], Configuring FCIP, Configuring the Number of TCP Connections for an FCIP Interface

In a two-node Cisco HyperFlex Edge deployment, the witness is deployed to Cisco Intersight. This cloud-based management platform provides intelligent insights and automation that scales with the business. It aids in managing all HyperFlex Edge deployments globally from a single cloud-based interface.Reference:

Cisco HyperFlex Edge Data Sheet - Cisco, Cisco HyperFlex Edge Data Sheet, Cisco HyperFlex Edge Deployment Options

Cisco HyperFlex Edge Installation Guide, Release 4.0 - Deploying HyperFlex Edge Clusters [Cisco HyperFlex HX Data Platform], Deploying HyperFlex Edge Clusters, Deploying a Two-Node HyperFlex Edge Cluster

NFS 4 reduces file locks by using leasing, which is an improvement over the locking mechanisms used in previous versions of NFS like NFS 3 or CIFS/SMB. Leasing allows clients to cache file data locally, reducing the need for frequent and potentially costly network operations.Reference:

Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide, Release 9.3(x) - Configuring NFS [Cisco Nexus 9000 Series Switches], Configuring NFS, NFS Overview

Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide, Release 9.3(x) - Configuring NFS [Cisco Nexus 9000 Series Switches], Configuring NFS, Configuring NFSv4 Leasing