350-601 Exam Dumps - Cisco CCNP Data Center Questions and Answers

A Multi-Site Orchestrator deployment requires two orchestrators to be deployed, one in each of the two main data center sites. The Multi-Site Orchestrator is a software component that enables the management and orchestration of multiple Cisco Application Centric Infrastructure (ACI) fabrics that are geographically distributed across different locations. The Multi-Site Orchestrator provides a single pane of glass for configuring, monitoring, and troubleshooting the ACI fabrics, as well as synchronizing policies and tenants across the sites. The Multi-Site Orchestrator also supports disaster recovery and high availability scenarios by allowing the replication of data and services between the sites. The Multi-Site Orchestrator deployment consists of two orchestrators that form a cluster and communicate with each other using a secure channel. Each orchestrator is connected to one or more ACI fabrics in the same site, and acts as a proxy for the other orchestrator to access the ACI fabrics in the remote site. The orchestrators use a leader-election algorithm to determine which one is the active orchestrator and which one is the standby orchestrator. The active orchestrator handles all the requests from the users and the applications, while the standby orchestrator monitors the health and status of the active orchestrator and takes over in case of a failure. The orchestrators also perform periodic data synchronization to ensure consistency and reliability. References :=

• Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 6: Cisco ACI, Lesson 6.4: Cisco ACI Multi-Site
• Cisco ACI Multi-Site Orchestrator User Guide, Chapter: Cisco ACI Multi-Site Orchestrator Overview

To create a certificate request in Cisco UCS Manager, the correct command set involves navigating to the security scope, selecting the appropriate keyring, and then creating the certificate request with the specified IP address and subject name. The commands in option D correctly follow this procedure. The commit-buffer command is used to commit the changes in UCS-A, which is the primary fabric.

References: This process is documented in the Cisco UCS Manager certificate management guidelines, which provide step-by-step instructions on creating certificate requests using the CLI

The logical configuration backup type in Cisco UCS Manager includes all logical configuration settings such as service profiles, VLANs, VSANs, pools, and policies. This backup type is suitable for the engineer’s requirements as it contains all vNIC, vHBA, and service profile template settings. Additionally, the logical configuration backup is in XML format, which allows for validation before import1.

References:

• Cisco documentation on “Backing Up and Restoring the Configuration” provides detailed information on the different backup types and their contents1.
• For further reading on UCS Manager backup operations and types, refer to the Cisco UCS Manager Administration Management Guide

The virtual-service resize command (D) is used to modify the resource allocation for a Linux container on a Cisco Nexus Series Switch1. This command allows the administrator to specify the amount of CPU and memory allocated to the container, ensuring it has the necessary resources to run successfully. In this case, the command would be used to allocate 10 percent of the CPU and 1024 MB of RAM to the container1.

References: The usage of the virtual-service resize command for managing resources in a Linux container can be found in the Cisco Nexus 9000 Series NX-OS Programmability Guide1.

To install the “Markdown” package from the Python package manager on a Cisco Nexus 93108 Series Switch, the engineer must ensure that the guest shell has internet access to reach the Python package repository. This is achieved by adding the nameserver configuration to /etc/resolv.conf, which allows the system to resolve domain names into IP addresses. After configuring the nameserver, the engineer must run the command sudo chvrf management pip install Markdown to install the package within the management Virtual Routing and Forwarding (VRF) context, which has access to the internet.

References: = For more information on managing packages in the guest shell of Cisco Nexus switches, refer to the Cisco Nexus 9000 Series NX-OS Programmability Guide.

To complete the PowerOn Auto Provisioning (POAP) operation on a Cisco Nexus 9000 Series Switch, the script must include the necessary network information such as the interface IP address, gateway, and DNS server IP addresses. Option C likely contains this information, which is essential for the switch to locate a DHCP server, bootstrap itself, and download the configuration script for software image installation and configuration

 To meet the objective of sending a copy of all VLAN 11 traffic on N5K_1 to the Traffic Capturing Device, creating a LAN traffic monitoring session is the necessary action. This session will capture the specified VLAN traffic and forward it to the designated capturing device for analysis or monitoring purposes. The existing configuration in Cisco UCS Manager needs to be complemented with this session to achieve the desired traffic capture.

 The correct code snippet to ensure that the Cisco NX-OS scheduler runs every day at 3:00 a.m. is “time daily 3:00”. This command configures the scheduler to execute the specified job daily at the given time, without the need for a ‘start’ keyword, which is not required in the syntax for daily repetitive tasks.

References: This explanation is based on the Cisco NX-OS documentation, which provides guidelines on how to schedule tasks using the NX-OS scheduler feature. The documentation is part of the Cisco Data Center Core Technologies study materials.

The History Count setting in a user management system is used to prevent the reuse of old passwords. It specifies the number of unique new passwords that must be used before an old password can be reused. This helps enhance security by ensuring that passwords are not easily guessable and that users are not cycling through a small set of favorite passwords.

To monitor and export traffic to a Network Analyzer, particularly ingress traffic from Host-A and all traffic for VLAN 20 from Host-B, the engineer must implement a configuration that captures the specified traffic and directs it to the Network Analyzer tool. The correct configuration will depend on the capabilities of the network devices in use and the specifics of the Network Analyzer’s requirements.

 The configuration must include setting up a SPAN (Switched Port Analyzer) or RSPAN (Remote SPAN) session that mirrors the desired traffic to a port connected to the Network Analyzer. This would involve specifying the source interfaces or VLANs and the destination port for the mirrored traffic. Additionally, the configuration should ensure that the Network Analyzer is capable of receiving and processing the mirrored traffic, which may require additional settings on the Network Analyzer itself.