Nokia 4A0-AI1 Practice Test - Questions Answers, Page 4

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 closedloop feedback that can optimize the network performance and reliability without any human involvement. The network can self-heal, self-optimize and self-protect.

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

According to the Nokia NSP Programmable Network Automation website1, NSP API documentation and downloadable sample codes are available on the Nokia Network Developer Portal. The NSP Workflow Manager allows the design and management of workflows to automate network operations using Mistral DSL v2 which is based on YAML2. YAML definesexpressions in workflow and action definitions. The formatting of the YAML must comply with Mistral DSL v2 specifications3

The {{...}} syntax is used to reference a workflow variable when using Jinja2. Jinja2 is a templating language used to generate dynamic text based on input variables, and the {{...}} syntax is used to access the value of a workflow variable within a Jinja2 template. The other syntaxes provided are not valid for referencing workflow variables in Jinja2.

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.

According to the Mistral Workflow Language (v2) website1, a workflow definition consists of several attributes that define its properties and behavior. The common workflow attributes are: name, description, type, input, output and vars1.

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.

According to the Mistral Workflow Language (v2) documentation1, which is one of the technologies that can be used in a NSP workflow2, flow control attributes are used to define how a task behaves depending on its execution status. The valid flow control attributes are on-success, on-error, oncomplete, and on-cancel1. Therefore, the correct answer is A.