Explanation
Comparing the actual and desired state of a network and taking action if they are not in sync. Intent-based networking is a method of managing a network by defining the intent of the network and then continuously comparing the actual and desired state of the network. If the two states are not in sync, the system will take action to bring the actual state in line with the desired one. This is different from manual processes of configuring networks or reacting to network issues. It also differs from dynamically changing the network infrastructure in real-time through one centralized location, or automatic discovery of cross domain links between IP and optical networks.

Explanation
Terminal emulation configuration is not one of the building blocks of NSP automation. The building blocks of NSP automation are Model-driven mediation, Analytics & telemetry, Multi-vendor support and Automation scripting. Model-driven mediation enables the automation of common tasks across multiple vendors and devices, and analytics & telemetry enables the gathering of critical data to ensure service quality. Multi-vendor support enables the automation of tasks across multiple vendors, and automation scripting enables the development of robust and secure automation scripts.
NSP automation is based on four key building blocks:
* Model-driven mediation: This enables NSP to communicate with various network devices and protocols using a common data model and abstraction layer. It supports YANG models, NETCONF, RESTCONF, SNMP, TL1 and CLI2.
* Analytics & telemetry: This enables NSP to collect and analyze network data using streaming telemetry, SNMP polling, syslog and other methods. It supports various analytics applications such as Network Insight, Service Assurance and Traffic Engineering
* Multi-vendor support: This enables NSP to manage and automate networks that consist of devices from different vendors and technologies. It supports Nokia SROS devices as well as third-party routers, switches and optical equipment
* Programmable APIs: This enables NSP to expose its functionality and data to external applications or systems using RESTful APIs. It supports various use cases such as network supervision, service fulfillment, fault management and workflow management

Explanation
NSP Workflow Manager (WFM) is a module that allows users to create and execute automated procedures using NSP or third-party APIs. A workflow is a sequence of actions that can be performed on various targets such as:
* NSP applications: These are the applications that run on NSP such as Network Insight, Service Assurance, Traffic Engineering and others. They can be accessed by using RESTful APIs2.
* Network elements: These are the devices that are managed by NSP such as routers, switches and optical equipment. They can be accessed by using CLI, NETCONF, RESTCONF, SNMP or TL12.
* UNIX servers: These are the servers that run UNIX-based operating systems such as Linux or Solaris. They can be accessed by using SSH or SCP

Explanation
YANG modules do not require proprietary MIBS. YANG modules are used to define the structure and content of a network configuration and are written in a structured language that consists of containers and leaves.
YANG modules are used in conjunction with NETCONF and RESTCONF to transport data, and they provide a separation of configuration and state data.

Explanation
This syntax assumes that there is a previous task that returns an object with an attribute named rtt that contains the round-trip time value1. The expression <% task().result.rtt %> evaluates to this value and assigns it to the variable rtt in the workflow context