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

Workflow Manager is a module of Nokia NSP that allows users to create and execute automated procedures and closed loop automation using Nokia NSP or third party APIs3. It uses Mistral as the workflow engine and supports various technologies that can be used in a workflow2.

Some of the technologies that are supported by Workflow Manager out of the box are:

REST/RESTCONF APIs

CLI command execution on SROS and third party routers

Optical integration using TL1

SNMP traps

Email notifications

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.

some of the operations that can be performed on an Intent are:

Create

Synchronize

Audit

Update

Delete

Therefore, based on this source, the answer that CANNOT be performed on an Intent is C. Phase-out.

The Nokia NSP Model-driven Mediation (MDM) framework is based on the YANG data model, uses the NETCONF protocol, and provides an abstracted view of the network element. However, it is designed to be vendor-specific, meaning it is designed to only manage Nokia equipment.

It provides an abstracted view of the network element is FALSE regarding Nokia's Network Services Platform (NSP) Model-driven Mediation (MDM) framework. MDM provides a way to interface between the Nokia NSP and network elements from different vendors. It is based on the YANG data model and uses the NETCONF protocol to provide configuration and management capabilities for network devices. However, MDM does not provide an abstracted view of the network element. Instead, it translates the native configuration of the network element into a standardized YANG model, allowing the NSP to manage the network element in a vendor-agnostic way.

According to the NSP NSD and NRC 18.6 Planning Guide1, Model-Driven Mediation (MDM) is a component within the NSP architecture that provides mediation between model-driven NSP applications and Nokia or third-party network devices. MDM provides an adaptation layer which uses adaptors to convert NSP application requests to device specific directives using standard protocols such as NETCONF, SNMP and CLI over SSH or Telnet12. MDM also provides an abstracted view of the network element3.

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.

NSP APIs allow for supervision of network elements, help with the definition and activation of network services, and allow for an OSS and NSP server to talk to each other. However, they do not support GraphQL, which is a query language for APIs. 

According to Nokia NSP IP Network Automation Professional guide, NSP APIs support REST/RESTCONF, SOAP/XML and GraphQlll, and help with the definition and activation of network services, and they also allow for supervision of network elements and an OSS and NSP server to talk to each other. Therefore, statement B is false as it states that NSP APIs support Kafka which is not mentioned in the guide as a supported API.

location services are part of the NSP REST API, which provides a full list of NSP REST API service names, endpoints and URLs. Therefore, correct answer is A. REST Reference: https://www.nokia.com/networks/training/nsp/self-paced/programmable-network-automation/ https://documentation.nokia.com/cgi-bin/dbaccessfilename.cgi/3HE12075AAACTQZZA01_V1_NSP%2017.6%20API%20Programmer%20Guide.pdf

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.

YANG is a data modeling language used to model configuration and state data for network devices. It defines a tree-like structure for data and is used to store, configure, and retrieve information from network devices. It is human readable and can be used to define actions and operations.