4A0-AI1 Sample Questions Answers

Comparing the actual and desired state of a network and taking action if they are not in sync. Intent-based networking is a method of managing a network by defining the intent of the network and then continuously comparing the actual and desired state of the network. If the two states are not in sync, the system will take action to bring the actual state in line with the desired one. This is different from manual processes of configuring networks or reacting to network issues. It also differs from dynamically changing the network infrastructure in real-time through one centralized location, or automatic discovery of cross domain links between IP and optical networks.

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.

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

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

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

According to the Workflow Manager User Guide from Nokia, the correct answer is C. Published. When a workflow is in the Published state, it can be executed by users who have the appropriate permissions. The Draft state is used during the creation of a new workflow, while the Deprecated state indicates that a workflow is no longer supported and should not be used. The Released state is not mentioned in the context of workflow execution.

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.

the input that is optional when using the std.ssh action is cmd. This parameter specifies the command to be executed on the remote server1. If this parameter is not provided, the action will only establish an SSH connection with the remote server and return its output1. The other parameters are required to authenticate and connect to the remote server.