4A0-AI1 Nokia NSP IP Network Automation Professional Composite Exam Free Practice Exam Questions (2025 Updated)

A Postman account allows you to create a maximum of 3600 workspaces for free. Postman is an API development environment used to create, test, and document APIs. It allows users to send requests and receive responses in a variety of formats, as well as add parameters to requests, define variables to store and re-use values, and execute pre-request scripts before the main request. However, Postman accounts do not allow users to create a maximum of 3600 workspaces for free; users must upgrade their accounts to access this feature.

According to the Nokia NSP Learning and Certification Program2, there are four main NSP applications:

Service Fulfillment: Enables service providers to design, create, and deliver IP/MPLS services across a multi-vendor network.

Network Supervision: Provides real-time visibility and control of network performance, faults, and inventory across physical and virtual networks.

IP/MPLS Optimization: Optimizes network resources by applying advanced algorithms and machine learning techniques to automate traffic engineering and path computation.

Network Virtualization: Enables service providers to create and manage virtualized network functions (VNFs) and network slices using cloud-native technologies.

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

According to the NSP Network Services Platform Release 20.9 User Guide1, the attribute of the target-component that determines the component name displayed in the UI is i18n-text.

The i18n-text attribute specifies a key for a localized text string that is displayed as a label for this component in the UI. The actual text string is retrieved from a resource bundle file based on the user’s locale.

For example, if i18n-text is “Port Id”, then the UI will display “Port Id” as the component name.

This system action allows you to pause a workflow and prompt the user for input. You can use this action to confirm or deny a course of action, or to enter some data that isrequired for the workflow1. For example, you can use nsp.user_input to ask the user if they want to continue with a service deployment or rollback.

The other options are not correct because:

std.sleep is a standard Python function that pauses the execution of a script for a specified number of seconds2.

nsp.wait is a system action that waits for an event or condition to occur before resuming the workflow1. For example, you can use nsp.wait to wait for a service activation status change or a network element alarm.

nsp.pause_before is not a valid system action. There is no such action defined in the NSP documentation1.

a system token is a string that is used to authenticate requests to the NSP REST API. A system token can be obtained by sending a POST request to the /token endpoint with a valid username and password1. a system token is valid for 60 minutes before expiring. After expiration, a new system token must be obtained by repeating the authentication process2.

file actions are NSP actions that provide access to files and folders on the NSP server. The file actions can access all directories on the NSP server, but they are restricted by the permissions of the user who runs them. For example, if a file action is run by a user who does not have write permission to a directory, the action will fail.

CLI is not used in Model Driven Telemetry. Model Driven Telemetry is a technology that uses YANG data models, NETCONF, gRPC and KAFKA to monitor and collect data from network elements. It provides an abstracted view of the network element and is vendor agnostic.

Model Driven Telemetry is a method of collecting real-time data from network devices, allowing for more efficient network monitoring and troubleshooting. It uses a variety of protocols and standards, including NETCONF, gRPC, and Kafka. However, CLI is a text-based user interface used for issuing commands to a device, and it is not typically used for collecting telemetry data.

According to the Nokia Network Services Platform for industry and the public sector datasheet1, NSP model-driven telemetry framework supports the Nokia SR OS and third-party devices in configuring and collecting performance statistics using gRPC, SNMP, NETCONF and accounting files such as SAP QoS1. It also enables data to be persisted in a database and be made available (e.g., over a Kafka bus) for a variety of use cases1.

The Nokia NSP is an IP network automation platform that provides a unified view of the network and enables end-to-end automation of IP networks. It is designed to be vendor-agnostic and can manage a wide range of equipment from various vendors, making it the Source of Truth for the entire network. It uses NETCONF and YANG to provision the network and can act as a Path Computation Element (PCE).

Nokia NSP is a network automation platform that supports multi-vendor network infrastructure. It acts as the "Source of Truth" for the network, uses NETCONF and YANG to provision the network, and can act as a Path Computation Element (PCE) to optimize traffic flow across the network. It supports a wide range of network devices, including those from third-party vendors, making it a flexible and vendor-agnostic solution for network automation.

some of the statements about the Nokia NSP are:

It is a platform that provides service automation and network optimization across multiple network layers and domains.

It uses NETCONF and YANG to provision the network and supports various protocols such as BGP-LS, PCEP, SNMP, etc.

It can act as a Path Computation Element (PCE) and provide end-to-end path computation for traffic engineering applications.

It can manage equipment from multiple vendors and supports open interfaces and standards.

http://nsp.developer.nokia.com/

https://www.nokia.com/networks/training/nsp/

Model-Driven Mediation (MDM) is a component that provides mediation between model-driven NSP applications and Nokia or third-party network devices. It uses adaptors to convert NSP application requests to device specific directives using standard protocols such as NETCONF, SNMP and CLI over SSH or Telnet.

This statement is false because MDM can communicate with devices that only support CLI (Command Line Interface) using a translation module that converts CLI commands to NETCONF or RESTCONF protocols. MDM acts as a mediator between the northbound system and the southbound devices by translating device configuration to a standard format that can be consumed by the northbound system.

The other statements are true:

B. It is the foundation for supporting multi-vendor device management. C. It provides the translation between the AMI and device model. D. It can interface with devices that support OpenConfig gRPC Network Management Interface.

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.

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.

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.

According to the NSP Intent Manager Application Help, an intent type has to be in Released state for Intent Manager to provision a request. An intent type can be in Draft, Released or Phased-out state. A Draft state means that the intent type is under development and cannot be used for provisioning. A Phased-out state means that the intent type is no longer supported and cannot be used for provisioning

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 NSP Kafka service is a distributed messaging system that allows different applications to publish and subscribe to different event types. It provides an API client to receive event or alarm notifications and subscribe to different event types. However, it does not use NETCONF based operations and YANG models. Instead, it uses the Kafka protocol to send and receive messages between producers and consumers.

The script-content.js file contains all the back end implementations required for Intent configurations to be performed.

The script-content.js file is a JavaScript file that defines the logic for creating, updating, deleting and synchronizing intents. It also defines the validation rules and error handling mechanisms for intents.

For example, a script-content.js file could contain:

function createIntent(intent) { // logic for creating an intent }

function updateIntent(intent) { // logic for updating an intent }