Command: netconf max-message <1-2147483> Kbytes. The engineer gets output from the command show line, but not from show running-config, because max-message is too small, it is not enough for data of running-config.

The Python script shown in the exhibit uses the NETCONF protocol to retrieve the configuration of a specified extended access list (named ftp) from a Cisco IOS XE device. Here's what it does:
The <get-config> NETCONF operation retrieves the running configuration for the specified

access list filter.
The data is processed using the Python library xmltodict, which converts the XML response into

a dictionary for easy manipulation and analysis.
The resulting dictionary contains the access list statements, making them accessible for further

processing or display.
This script does not configure or modify the access list; instead, it retrieves and structures the access list into a dictionary list.

POST: This method creates a data resource or invokes an operations resource.

The Lightweight AP (LAP) can discover controllers through your domain name server (DNS). For the access point (AP) to do so, you must configure your DNS to return controller IP addresses in response to CISCO-LWAPP-CONTROLLER.localdomain, where localdomain is the AP domain name. When an AP receives an IP address and DNS information from a DHCP server, it contacts the DNS to resolve CISCO-CAPWAP-CONTROLLER.localdomain. When the DNS sends a list of controller IP addresses, the AP sends discovery requests to the controllers.
The AP will attempt to resolve the DNS name CISCO-CAPWAP-CONTROLLER.localdomain.
When the AP is able to resolve this name to one or more IP addresses, the AP sends a unicast CAPWAP Discovery Message to the resolved IP address(es). Each WLC that receives the CAPWAP Discovery Request Message replies with a unicast CAPWAP Discovery Response to the AP.
Reference: https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan- controllers/107606-dns-wlc-config.html