Practice Free 4A0-AI1 Nokia NSP IP Network Automation Professional Composite Exam Exam Questions Answers With Explanation

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.

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.

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.

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, on-complete, and on-cancel1. Therefore, the correct answer is A.

The HTTP methods that are supported by REST/RESTCONF are:

• GET: Used to retrieve a representation of a resource.
• PUT: Used to replace a resource or create it if it does not exist.
• DELETE: Used to delete a resource.
• PATCH: Used to apply a partial update to a resource.

The HTTP method ADD is not a standard HTTP method and is not supported by REST/RESTCONF.

This syntax assumes that there is a previous task that returns an object with an attribute named rtt that contains the round-trip time value1. The expression <% task().result.rtt %> evaluates to this value and assigns it to the variable rtt in the workflow context1.

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.

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.

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.

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/

According to the NSP Network Services Platform Release 20.6 Intent Manager Application Help1, an intent type consists of four components: general metadata, target, YANG model and script. The metadata in the meta-info.Json file appears in the General and Resources panels of the Edit Intent Type window

a workflow can use environments to make it portable if the workflow needs to be executed on either a development or production lab. Environments are files that contain key-value pairs that can be used as input parameters for workflows1. Environments allow workflows to be executed with different settings without modifying the workflow definition1.

containers in YANG modules can be thought of as branches in a tree, while leaves are the end of a branch where the information will sit.

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.

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.

Ad-hoc actions are wrappers around existing system actions that allow for more flexibility in terms of what can be done. They are not default actions provided by Workflow Manager, nor are they special actions for NSP applications. Ad-hoc actions can be used by multiple workflows.

Virtualization is not a characteristic of intent-based networking, but rather a technology that enables it. Virtualization is the process of creating virtual versions of physical resources, such as servers, storage, or networks1. Virtualization allows for more flexibility and scalability in network design and management, but does not imply any automation or intelligence.

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 NSP Intent Manager Application Help12, if you select “Modify” under “Behavior” in the WebUI and successfully modify an intent, the intent is updated in the Intent Manager database and compared with the configuration on the target node. This will change the intended configuration for the audit and synchronize operations