The Automating Cisco Enterprise Solutions (ENAUTO) (300-435)

The Cisco DNA Center API provides access to various network assurance features, including:

Site health : Monitoring the health and performance of network sites.

Client health : Assessing the health of connected clients (end-user devices).

References :

Cisco DevNet - Intent APIs

The error is due to Command Runner in Cisco DNA Center being designed to support only the execution of ‘show’ commands or other read-only commands. When an engineer tries to execute configuration commands or any commands that are not read-only, they will be blocklisted as these are not supported by Command Runner. This ensures that Command Runner is used strictly for retrieving information without making any configuration changes to devices.  References  := (Automating Cisco Enterprise Solutions Official Cert Guide)

The provided exhibit likely shows a POST request setup in an API testing tool like Postman, with JSON formatted data specifying commands for configuring a network device interface. These commands are not supported by Command Runner as it does not allow configuration changes, only read operations.

 When using the Cisco Meraki API to create a network, two mandatory parameters are “type” and “organizationId”. The ‘type’ parameter specifies what kind of network is being created (e.g., wireless, switch, security appliance), while ‘organizationId’ links the new network to a specific organization within Meraki’s system.  References  := ( Automating Cisco Enterprise Solutions Official Cert Guide )

It is a device-independent method for automation and can be used with any type of device or operating system :

Ansible is an open-source automation tool that works across various platforms, including network devices, servers, and cloud services.

It uses a declarative language (YAML) to define tasks, making it independent of the underlying device or operating system.

Ansible playbooks can be written once and applied consistently to different devices, regardless of their specific characteristics.

It does not require any modules of software except SSH to be loaded on the network device :

Ansible communicates with network devices (including Cisco IOS XE devices) over SSH.

Unlike some other automation tools, Ansible does not require additional software or agents to be installed on the network devices.

This simplicity and lightweight approach make Ansible an attractive choice for network automation.

Comprehensive and Detailed Step by Step Explanation :

It is a device-independent method for automation and can be used with any type of device or operating system :

Ansible uses a declarative approach, where users define the desired state of the system (tasks) rather than specifying how to achieve that state (procedural steps).

Playbooks written in YAML are device-agnostic and can be applied to various platforms.

Ansible modules provide abstractions for specific tasks (e.g., configuring interfaces, managing VLANs), allowing consistent automation across different devices.

It does not require any modules of software except SSH to be loaded on the network device :

Ansible communicates with network devices using SSH (Secure Shell).

No additional software or agents need to be installed on the network devices.

This simplicity minimizes the impact on the devices and ensures compatibility with a wide range of network equipment.

References :

Automating Cisco Enterprise Solutions Official Cert Guide

Ansible Documentation

 To create a new feature in a separate branch and check out the new version, the correct commands are needed. Option B provides the correct sequence of Git commands to achieve this task. The command  git checkout -b feature  creates a new branch named “feature” and switches to it immediately, which is exactly what is required when starting development on a new feature while keeping the production release intact in the “master” branch.  References  := ( Automating Cisco Enterprise Solutions Official Cert Guide )

The NETCONF statement type represented by “±-rw address* [ip]” is a ‘list’. In YANG, which is the data modeling language used by NETCONF, a ‘list’ statement defines a sequence of list entries. Each entry is like a row in a table. The “+” indicates that this is a configuration data node, “rw” means read-write, and the asterisk (*) signifies that multiple address entries are allowed (hence it’s a list), with “ip” being the key for each unique entry in the list.  References : Automating Cisco Enterprise Solutions Official Cert Guide

The  yp:xpath-filter  tag is used in YANG-push subscriptions to filter the YANG data model and specify which parts should trigger notifications, providing granular control over the data changes monitored.  References  := ( Automating Cisco Enterprise Solutions Official Cert Guide )

 In NETCONF telemetry subscriptions with Cisco IOS XE devices, the correct XML tag to complete the subscription is “period”. This tag defines the interval in milliseconds at which the telemetry data will be collected and sent. The “period” tag is used to set a fixed time interval for data collection, as opposed to other options like “frequency” which would imply a rate of occurrence or “cadence” which refers to the flow or rhythm of events.  References  := ( Automating Cisco Enterprise Solutions Official Cert Guide )

The Cisco SD-WAN vManage Certificate Management API is primarily used for certificate-related operations within the SD-WAN fabric. The correct purpose of using this API is:

A : To generate a Certificate Signing Request (CSR). The CSR is a request sent from an applicant to a certificate authority to apply for a digital identity certificate. It contains information that will be included in the certificate, such as the applicant’s public key and organization details.  Once the CSR is generated, it can be signed by a Certificate Authority (CA) to create a certificate 1 .

References :

Cisco Catalyst SD-WAN CloudOps - Certificate Management 1

Cisco SD-WAN API documentation 2

Understand the Web Certificate For vManage - Cisco