300-435: Automating and Programming Cisco Enterprise SolutionsDemo

Cisco Meraki Dashboard API v1 splits a combined network by calling POST /networks/{networkId}/split. With ENAUTO as the network ID, the required request URL is https://api.meraki.com/api/v1/networks/ENAUTO/split.

Cisco Meraki defines the operation to split a combined network into individual networks as POST /networks/{networkId}/split. A POST request with the configured headers and empty payload invokes that action.

Scanning API location estimates use observations from access points. The placement of APs affects the geometry and signal observations used for estimation, while a client device’s orientation can alter its observed radio signal characteristics. Cisco Meraki identifies both AP placement and client device orientation as factors that influence X,Y location estimation.

The interface name is a configuration leaf within the interface list. That list is nested under interfaces, which is under each vlan entry in vlans; therefore the complete node path is vlans/vlan/interfaces/interface/name.

Data preprocessing transforms input data into a cleaner, structured, or otherwise suitable form so downstream AI-assisted logic can use it effectively.

For on-change subscriptions, Cisco's model-driven telemetry implementation requires the dampening-period to be explicitly set to 0, indicating that no dampening period is applied. This holds true whether the on-change publication is configured via the standards-based YANG-push (RFC 8641) mechanism or through the OpenConfig telemetry model — no other value is supported for on-change publications in either case, since dampening (which aggregates and delays updates) is not compatible with immediate on-change notification behavior.

Cisco DNA Center triggers device configuration synchronization through the PUT operation on /dna/intent/api/v1/network-device, which synchronizes the supplied device input, and through PUT /dna/intent/api/v1/network-device/sync, the Sync Devices operation. The latter operation is documented as synchronizing devices and supports the optional forceSync parameter.

NETCONF supports multiple configuration datastores, including a candidate datastore that can be edited and then validated with the <validate> operation before being committed to the running configuration. RESTCONF does not implement the concept of a candidate datastore or datastore validation; it operates directly against a single datastore (the running configuration), so this validation capability is unique to NETCONF.

RESTCONF on Cisco IOS XE uses HTTP authentication, and a Base64-encoded Basic credential is sent as the value of the Authorization header with the Basic scheme. Cisco documents that RESTCONF connections require AAA authentication. X-XSRF-TOKEN, secure-token, and x-auth-token are not the HTTP Basic authentication header used here.

The SD-Access Fabric creation endpoint accepts a JSON object whose fabricName field identifies the fabric. Passing a Python dictionary through requests.post(..., json=sda_fabric_info) serializes it as the required JSON body: {"fabricName": "DNAC_Guide_Fabric"}.

Cisco IOS XE ZTP works by having the device request a Python bootstrap script (typically via DHCP options) and then execute that script to apply the device configuration. This script runs inside the IOS XE Guest Shell, a Linux container environment built into IOS XE that hosts the Python interpreter and associated libraries needed for on-box automation. Cisco's ZTP documentation specifies that the Guest Shell must be enabled on the device for the ZTP provisioning script to run and complete the automated configuration process.

The Meraki create-network operation uses POST on an organization's /networks collection and returns HTTP 201 when the network is created successfully.

The exhibited JSON has "data" as the top-level key, whose value is a list; the first item in that list (index 0) is a dictionary containing the key "host-name". To retrieve this value in Python, you must use square-bracket indexing with the keys given as quoted strings, in the correct nested order: d["data"][0]["host-name"]. This matches standard Python dictionary/list access syntax, where dictionary keys must be quoted strings and list elements are accessed by integer index using square brackets. Omitting quotes around keys, using parentheses instead of brackets, or reversing the key order/using curly braces all produce invalid or incorrect Python syntax for this data structure.

The Cisco Catalyst Center network-device list endpoint uses an HTTP GET request to return managed network devices. PUT is not the supported retrieval method for that endpoint, so changing the request method to GET allows the script to obtain the list. Cisco DevNet: Get Device list

Threat identification uses signature matching to recognize known malicious patterns in traffic or events and trigger warnings or alerts.

A YANG list is shown with an asterisk and its key leaf or leaves in brackets. Here, ip is the key for the repeatable address entries.

Network event notifications are published to an external REST endpoint through the Network Events for REST API Endpoint integration bundle. This is the bundle for delivering Cisco DNA Center network-event data to a receiving system such as a dashboard integration; CMDB synchronization and ITSM enrichment serve different workflows.

Ansible provides agentless automation for Cisco IOS XE: playbooks are executed from the Ansible control node and can manage a device over SSH without installing Ansible software modules on that device. Its automation framework is also platform-independent, enabling a common approach across different device types and operating systems.