4A0-AI1 Nokia NSP IP Network Automation Professional Composite Exam Questions and Answers

Service Fulfilment API does not provide alarm monitoring; rather, it allows customers to quickly and easily order and provision services from a single interface, allowing for increased service agility and reduced human error.

According to the Nokia NSP Service Fulfilment API User Guide, Service Fulfilment API offers the following benefits:

A. Increases service agility by providing a programmable interface for automated service provisioning and management, allowing network operators to quickly respond to customer demands and network changes.

B. Reduces human errors by automating the service provisioning process, which minimizes the risk of manual configuration errors and improves service quality.

C. Allows multi-vendor service provisioning by providing a vendor-agnostic interface that supports different types of network equipment and technologies, reducing vendor lock-in and enabling greater network flexibility.

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

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.

Nokia NSP is a platform that enables management, control and automation of IP/Optical networks. It supports various levels of network automation, from static networking to autonomous networking.

The process of moving to SDN based self-regulated networking involves four stages:

• Static networking: The network is manually configured and operated by human operators. There is no automation or intelligence involved.
• Action-based networking: The network is partially automated by using predefined actions or scripts that are triggered by events or commands. There is still human intervention required for complex tasks or exceptions.
• Adaptive networking: The network is dynamically automated by using policies, analytics and machine learning that can adjust the network behavior based on changing conditions and objectives. There is minimal human intervention required for oversight and validation.
• Autonomous networking: The network is fully automated by using artificial intelligence and closed-loop feedback that can optimize the network performance and reliability without any human involvement. The network can self-heal, self-optimize and self-protect.

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 }

According to the Mistral Workflow Language (v2) documentation1, which is one of the technologies that can be used in a NSP workflow2, with-items is a task property that allows the action associated with a task to be run multiple times over a list of items1. The syntax for using with-items is:

task_name:

action:

input:

:<%item()%>

with-items:itemin

You need to replace , , and  with your desired values. You can also use other properties such as concurrency, retry, or count to control how many iterations are executed in parallel, how many times an iteration is retried if it fails, or how many times an iteration is executed respectively1.

nsp.netconf is a nodal communication action that uses NETCONF protocol to communicate with network devices. The host input represents the management IP address of the device that is being configured by NSP. It is one of the inputs required for nsp.netconf along with username, password, port and command.

Infrastructure Lure Intents are a type of Network Intent that describe how network resources should be allocated and configured for a specific service or application.

L2/L3 VPN configuration of multiple services is NOT a characteristic of Infrastructure Lure Intents, because it is more related to service provisioning than resource allocation.

According to the Nokia NSP Workflow Design and Management course12, a workflow is a sequence of tasks that are executed to achieve a certain goal. Data flow in a workflow refers to passing data between tasks12. Therefore, the correct answer is B.

Data flow can be defined using input, output, and publish parameters in a workflow definition3. Input parameters are used to pass data into a workflow, output parameters are used to return data from a workflow, and publish parameters are used to share data between tasks within a workflow3.