300-635 Sample Questions Answers

 The Cisco UCS PowerTool is a PowerShell module that provides an interface to Cisco Unified Computing System (UCS) Manager API. To initiate a connection to the Cisco UCS Manager, the ‘Connect-Ucs’ cmdlet is used. This cmdlet requires parameters such as the name of the UCS domain (in this case, ‘myucsm.example.com’) and credentials stored in a variable (here represented as ‘$ucsm_creds’). The credentials are typically created beforehand using the ‘New-Object’ cmdlet with a PSCredential object type, which securely stores the username and password required for authentication. References := Cisco UCS PowerTool Suite - PowerShell Libraries for Cisco UCS Manager

Cisco NX-OS iPXE supports both IPv4 and IPv6 network protocols. iPXE is an open-source network boot firmware that enhances the capabilities of the standard PXE by supporting additional protocols like HTTP and TFTP, which can operate over both IPv4 and IPv6 networks3.

References :=

Cisco Nexus 9000 Series NX-OS Programmability Guide, Release 10.1 (x)3

Zero Touch Provisioning Implementation and Troubleshooting Tips - Cisco4

In Cisco Application Centric Infrastructure (ACI), class names are composed by combining the package name with the class name, separated by a colon. This naming convention helps in organizing and referencing classes within the ACI’s object model, which is essential for automation and programmability in the data center.

References := Implementing Automation for Cisco Data Center Solutions (DCAUI)

Cisco UCS Director custom workflow tasks are scripted in Cloupia Script. This scripting language is specific to Cisco and is used for automating tasks across various components of data center operations.

References:

Cisco UCS Director Scripting Guide

 The network bootstrap program used by Cisco NX-OS for iPXE is called iPXE-POAP (Power-On Auto Provisioning). This process assists in automating the installation and configuration of Nexus switches. POAP automates the process of upgrading software images and installing configuration files on switches that are being deployed in the network for the first time. References: Cisco official documentation and training materials.

To enable the REST API browser within Cisco UCS Director, a user must edit their profile to enable developer options. This action provides access to the REST API browser, which is a powerful tool for automating tasks and operations within the Cisco UCS Director environment.

References := Implementing Automation for Cisco Data Center Solutions (DCAUI)

In Cisco NX-OS platforms, two common bootstrap technologies are supported: iPXE (Internet Protocol eXtensible Environment) and POAP (PowerOn Auto Provisioning). iPXE allows for network booting using software such as DHCP or TFTP to load an operating system over a network interface independently of data storage devices like hard disks or CD-ROM drives. POAP automates the process of upgrading software images and installing configuration files on switches that are being deployed in the network for the first time. References := Cisco NX-OS Software

The EEM script in the exhibit is designed to monitor for specific syslog messages. If any of the patterns specified (“copy bootflash:* running-config”, “copy run start”, or “Hello”) occur within a 120-second window, the script will trigger the reload of module 1 on the Cisco Nexus 9000 switch. This action is based on the occurrence of any one of the patterns, not all, which aligns with option B. References:

Implementing Automation for Cisco Data Center Solutions (DCAUI) course material

Cisco Nexus 9000 Series NX-OS System Management Configuration Guide

To access the REST API browser within Cisco UCS Director, one must enable the Developer menu from the Cisco UCS Director interface. After enabling this option, select ‘Orchestration’ and then choose ‘REST API Browser’. This allows users to interact with the various APIs provided by Cisco UCS Director for automation and orchestration purposes. References: Cisco UCS Director REST API Guide

 Cisco Intersight REST API uses HMAC for authentication, where the message content and headers are signed using an API Key ID (A), and the Cisco Intersight Web service verifies the signature with the RSA public key for the API Key ID ©. The SHA384 hash (B), RSA private key challenge (D), and SHA256 hash (E) are not described in the authentication method for Cisco Intersight REST API requests.

The top level in the ACI Management Information Tree is polUni. This is the top-level class for all policy definition and resolution objects within the Cisco ACI Policy Model. It serves as the root for policy namespace in the Management Information Tree12.

References :=

Cisco ACI Policy Model Guide1

Understanding the Cisco Application Policy Infrastructure Controller2

The command telemetry_receiver.py --ip-address -port  is used to start a Python network telemetry collector. This command specifies the IP address and port where the telemetry receiver will listen for incoming telemetry data from network devices

The API Inspector in Cisco’s APIC is used to capture and display API requests made by the APIC GUI. It helps users learn or identify the sequence of API calls for specific operations performed in the APIC GUI. This tool is useful for developers who want to automate tasks using RESTful APIs by providing them with exact API calls that can be replicated in scripts or applications. References :=

Implementing Automation for Cisco Data Center Solutions (DCAUI) course

The Python code in the exhibit is using the Cobra SDK to interact with Cisco’s Application Centric Infrastructure (ACI). The code performs the following actions:

It logs into the ACI fabric using credentials provided.

It creates a new Virtual Routing and Forwarding (VRF) instance named “DevNet_VRF” within a tenant named “DevNet_Tenant”.

It creates a new Bridge Domain (BD) named “DevNet_BD” within the same tenant and associates it with the previously created VRF.

It defines a subnet within this Bridge Domain with the network address “10.10.10.1/24”, which is labeled as “DevNet_Subnet”.

An Application Profile (AppProfile) named “DevNet_App” is created within the tenant.

An Endpoint Group (EPG) named “DevNet_EPG” is created and associated with both the AppProfile (“DevNet_App”) and BridgeDomain (“DevNet_BD”).

Therefore, options B and C are correct: B. This action creates an EPG called “DevNet_EPG” inside an AppProfile called “DevNet_App” located in an ACI tenant called “DevNet_Tenant”. The EPG is linked to a BridgeDomain called “DevNet_BD”. C. This action creates a subnet called “DevNet_Subnet” inside VRF “DevNet_VRF” located in an ACI tenant called “DevNet_Tenant” and sets its network address to “10.10.10.1/24”.

References :=For more information on automating Cisco Data Center Solutions, one can refer to Cisco’s official training course for Implementing Automation for Cisco Data Center Solutions (DCAUI): Cisco Training Course

Kubernetes deployed with the ACI CNI plug-in offers Namespace Isolation and Cluster Isolation. Namespace Isolation segregates resources within the same cluster using Kubernetes namespaces, while Cluster Isolation ensures complete separation between different clusters. References:

Cisco ACI Documentation

Cisco Learning Network

 The Cisco UCS Director script module serves as a centralized repository within the UCS Director platform. It allows users to store custom scripts, Java archives (jars), and customized lists of values, which are crucial for creating or modifying workflows to automate tasks in a data center environment. By utilizing the script module, administrators can enhance workflow functionality with their own scripts or existing ones, thereby streamlining operations.

References:

Cisco UCS Director Scripting Guide

Cisco Learning Network’s Data Center Training Videos

Simple Network Management Protocol (SNMP) traditionally operates on a pull model where the management system periodically polls or requests information from network devices at set intervals. In contrast, model-driven telemetry is designed to use a push model where information is sent by network devices to the management system proactively when certain conditions are met or at set intervals without waiting for an explicit request from the management system. References := Cisco IOS XE Model-Driven Telemetry