300-635 Automating Cisco Data Center Solutions (DCAUTO) Questions and Answers

To enable Bash shell on a Cisco Nexus 9000 Series Switch running NX-OS, the command feature bash-shell must be used. This command activates the Bash shell feature within NX-OS, allowing for advanced scripting and automation capabilities directly on the switch. It’s important to note that proper authorization should be ensured before using this command, and its implications for security and operations should be understood. References :=

Official Cisco Nexus 9000 Series NX-OS Fundamentals Configuration Guide

Cisco Community Discussion on Enabling Bash Shell

Without the exhibit or the complete Python code options (A, B, C, D), it is not possible to determine which snippet correctly creates an application policy named OrderProcess with two application endpoint groups under Tenant SuperEats using direct calls to the ACI REST API. The correct answer would depend on the specific API calls made and the structure of the JSON payload in the Python code.

References :=

Automating Cisco Data Center Solutions (DCAUI) v1

Cisco Application Centric Infrastructure (ACI) documentation

The Python script uses the ACI Cobra SDK to interact with Cisco’s Application Centric Infrastructure (ACI). It logs into the APIC and retrieves a list of all application profiles (‘fvAp’), then prints out their distinguished names (dn), which uniquely identify each application profile within the ACI fabric. References:

Cisco Developer Network

Cisco Learning Network

The output shown in the exhibit is a list of distinguished names (DNs) for Cisco Unified Computing System (UCS) blades within specific chassis. The correct PowerTool commands to provide this output would be those that retrieve information about UCS blade servers and then select their distinguished names. The command Get-UcsBlade | Select-Object Dn retrieves all the UCS blade servers and then pipes them to the Select-Object cmdlet to display only their distinguished names, which matches the pattern seen in the exhibit. Similarly, Get-UcsRackUnit | Select-Object Dn could potentially provide a similar output if rack units are named in a similar fashion to blades within the system’s naming conventions. References :=

Cisco UCS PowerTool Suite - PowerShell Libraries for Cisco UCS Manager: 1

Cisco UCS Manager CLI Configuration Guide: 2

git add .

git commit –m “new function”

git status

The Cisco Data Center Network Manager (DCNM) REST API provides a robust platform for automating various tasks in the data center. Two of its capabilities include:

A: The DCNM REST API uses the dcnm-token header for requests authentication after initial basic authentication. This token-based authentication is more secure as it reduces the need to repeatedly send credentials over the network.

E: The DCNM REST API is organized into different management areas such as Classic LAN, LAN Fabric, Media Controller, and SAN Management. This categorization allows for targeted automation and management within specific domains of the data center network.

References :=

Implementing Automation for Cisco Data Center Solutions (DCAUI) v1.0

Cisco Data Center Network Manager documentation

The ACI Cobra SDK is a Python library provided by Cisco for interacting with the Application Centric Infrastructure (ACI). The code in the image uses this SDK to log into an APIC controller, which is the central management entity for the ACI fabric. After logging in, it creates a class query for ‘fvCEp’, which stands for Fabric Endpoint. This class contains information about endpoints within the ACI fabric, including their MAC and IP addresses.

The ‘subtree’ property set to ‘full’ indicates that the query will return all objects within this class’s subtree, meaning it will retrieve detailed information about each endpoint. The mo_dir.query(cq) method executes this query against the APIC.

Finally, for each object returned by the query (each endpoint), it prints out two attributes: ‘mac’ and ‘ip’. These attributes correspond to the MAC address and IP address of each endpoint in the ACI fabric. Therefore, option C is correct as this code prints all endpoint MAC and IP addresses.

References:

Implementing Automation for Cisco Data Center Solutions (DCAUI)

Cisco Learning Network - Data Center Training Videos

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

 To retrieve server profiles with “WEST15” in the name, the correct GET API request is D. GET https://intersight.com/api/v1/server/Profiles?$select=Name &$filter=startswith(Name, ‘WEST15’). This request filters the server profiles to only those that start with “WEST15”. For updating the name, option E is correct. The BODY = {” Name”: sp_name.replace(‘WEST15’,’LXT14’)} uses the Python replace method to change “WEST15” to “LXT14” in the server profile name. References: Cisco Intersight API documentation and Python programming resources.

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

To add an additional NTP server to an existing NTP server policy in Cisco Intersight via API call, one would typically use the HTTP PATCH method to update the policy with the new server details. The PATCH method is used to apply partial modifications to a resource.

The image shows four different code snippets that are examples of API calls using different HTTP methods (POST and PATCH) for modifying NTP server policies in Cisco Intersight. However, without seeing the full context of options A, B, C, and D from the original question source, it’s impossible to determine which one correctly adds an additional NTP server to “My_NTP_Policy”.

Based on common practices for RESTful APIs and assuming that “My_NTP_Policy” already exists and we need to add another NTP server to it without removing existing ones:

One would use a PATCH request.

The URI (Uniform Resource Identifier) should target the specific policy by name or ID.

The body of the request should include only the properties that are being added or changed—in this case, adding a new NTP server address.

References :=

Implementing Automation for Cisco Data Center Solutions (DCAUI) - Cisco Training Course

The code snippet is intended to access a child managed object within Cisco’s ACI. The current placement of line 2 (dnQuery.subtree = 'parent') specifies that the query should look at the parent objects, not the children. To fix the code so that it accesses a child managed object, line 2 should be moved to after line 3, where tenantMo is defined. This change will ensure that the subtree of tenantMo is set to ‘parent’, which means that when defaultBDmo is called in line 4, it will correctly reference a child managed object under tenantMo. References :=

Cisco ACI documentation on Managed Objects

Cisco DevNet ACI Programmability Guide

The error message “Request failed ” indicates that the Ansible playbook is trying to connect to the Cisco NX-OS switch using HTTP but is unable to establish a connection. This can be due to the HTTP server feature not being enabled on the NX-OS device. Enabling an HTTP server on a Cisco NX-OS device allows for remote management of the device via HTTP, which is what the Ansible playbook is attempting to do.

To resolve this issue, one would need to enable the HTTP server on the Cisco NX-OS switch. The command http-server enabled specifically enables the HTTP server feature, allowing for remote connections such as those attempted by Ansible playbooks.

References :=

Implementing Automation for Cisco Data Center Solutions (DCAUI) - 6

Cisco Learning Network - Automating Cisco Data Center Solutions Videos - 7 

The default data encoding for the response output of the ACI APIC API inspector is JSON (JavaScript Object Notation). JSON is a lightweight data-interchange format that is easy for humans to read and write and easy for machines to parse and generate. References: Cisco ACI documentation and API guides.

 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.

REST, or Representational State Transfer, is an architectural style that is characterized by its stateless nature, meaning each request from a client to a server must contain all the information needed to understand and complete the request without relying on any stored context on the server. This increases reliability and scalability. However, ‘stateful’ is not a guiding principle of REST; instead, it is ‘statelessness’ that is a core principle. The other main guiding principles include a uniform interface, cacheability, and a layered system

conf t

Event manager applet link monitor

Event syslog pattern “IF_UP”

Action 1 cli command “source cdp_description.py”

Exit

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