Pass the Nokia Nokia Certified NSP IP Network Automation Professional 4A0-AI1 Questions and answers with CertsForce

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.

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 Engineering2.

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 equipment3.

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 management2.

Workflow Manager is a tool that allows users to design and execute workflows for network automation using NSP actions and expression functions. The Workflow Manager supports data encoding/decoding formats such as JSON, CSV, XML and Base64. However, it does not support BER (Basic Encoding Rules), which is a format used for encoding data structures for transmission or storage. 

The template-mappings can only be viewed by making a RESTCONF call to query an existing intent.

The template-mappings are a set of key-value pairs that map the abstract YANG model attributes to concrete NFM-P templates and parameters. They are not exposed in the UI or the ibn:intent model, but they are stored internally in the NSP database.

For example, a template-mapping could be: /network=IP/service=VPN -> nsp-ip-vpn-template.

The main sections of an abstract YANG module file are arguments and statements.

An argument is a string that provides additional information about a statement. A statement is a keyword followed by an argument and optionally enclosed by braces ({ }) containing substatements.

For example, an abstract YANG module file could start with:

module ibn-intent { namespace “urn:nokia.com:ibn:intent”; prefix ibn;

This defines the module name, namespace and prefix as arguments for the module, namespace and prefix statements respectively.

According to the Mistral Workflow Language (v2) website1, Mistral Workflow Language supports YAQL and Jinja2 expression languages to reference workflow context variables and thereby implements passing data between workflow tasks. It’s also referred to as Data Flow mechanism. YAQL is a simple but powerful query language that allows to extract needed information from JSON structured data1.

The correct answer is B. Fault Management API. The Fault Management API can be used to identify the root cause(s) of issues in the network, such as hardware or software faults, configuration errors, and other problems. It provides a unified interface to receive and analyze fault information from multiple network elements.

The API that can identify the root cause(s) of issues in the network is the Fault Management API. This API allows network operators to monitor network faults and events in real-time, and diagnose and resolve issues quickly and efficiently. It provides information about the root cause(s) of the fault and the affected network elements, as well as enabling automated fault handling and resolution.

The character used to separate the attributes of a Target with multiple attributes is /.

For example, a Target with multiple attributes could be: /network=IP/service=VPN.

The statement that best describes the Intent Manager application is: "It generates and validates the configuration of the network." Intent Manager is responsible for collecting the user's intent, verifying the user's input, and converting the user's intent into a device-specific configuration. It uses a high-level language to abstract the network complexity, enabling the network operator to define intent in simple terms. Once the intent is defined, Intent Manager automatically generates a device-specific configuration for each network element. It then validates the intent by checking the network's current state against the user's desired intent. If there is a mismatch, it will take corrective action to bring the network to the desired intent state.