4A0-AI1 Questions and Answers

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.

According to the NSP Intent Manager Application Help1, an intent type consists of four components: general metadata, target, YANG model and script. The resources component is used to store files that are required by the script component1. Therefore, A. Framework files is NOT a category of files found in the intent-type resources directory.

nsp.sr_cli is a nodal communication action that uses the network element’s NE ID to establish communication. It is one of the NSP actions and expression functions that can be used to design workflows for network automation

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.

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.

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.