4A0-AI1 Exam Dumps - Nokia Certification Questions and Answers

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

CLI is not used in Model Driven Telemetry. Model Driven Telemetry is a technology that uses YANG data models, NETCONF, gRPC and KAFKA to monitor and collect data from network elements. It provides an abstracted view of the network element and is vendor agnostic.

Model Driven Telemetry is a method of collecting real-time data from network devices, allowing for more efficient network monitoring and troubleshooting. It uses a variety of protocols and standards, including NETCONF, gRPC, and Kafka. However, CLI is a text-based user interface used for issuing commands to a device, and it is not typically used for collecting telemetry data.

According to the Nokia Network Services Platform for industry and the public sector datasheet1, NSP model-driven telemetry framework supports the Nokia SR OS and third-party devices in configuring and collecting performance statistics using gRPC, SNMP, NETCONF and accounting files such as SAP QoS1. It also enables data to be persisted in a database and be made available (e.g., over a Kafka bus) for a variety of use cases1.

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.

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.

orchestration is the automated configuration, coordination, and management of computer systems and software. Orchestration takes advantage of several tasks that are usually automated to create a more complex workflow.

An orchestrator is a software tool that is used to automate the configuration, coordination, and management of large virtualized systems, middleware, and services. The other three options are not related to the automated configuration, coordination, and management of large virtualized systems, middleware, and services.

Orchestrator is described as "the automated configuration, coordination, and management of large virtualized systems, middleware, and services." The orchestrator is a key component of network automation, enabling the automation and management of complex network functions across multiple devices and platforms.

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

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

• OPTIONS: Used to retrieve the communication options available for a resource.
• GET: Used to retrieve a representation of a resource.
• PATCH: Used to apply a partial update to a resource.
• POST: Used to create a new resource or trigger a specific action.

The HTTP method TRACE is not supported by REST/RESTCONF.

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.

According to the Nokia NSP Intent Manager Application Help2, Intent Manager has the following benefits:

• It allows programmable and flexible logic. You can use scripts to define how intents are translated into network commands and how they react to network events.
• It provides concepts for finding misalignments. You can use audit and synchronize functions to detect and resolve any discrepancies between intents and network states.
• It provides flexible capabilities for achieving high-level business goals. You can use intents to express complex network behaviors such as service protection, bandwidth optimization, or latency reduction.

Therefore, based on these sources12, the correct answer to your question is:

A. Allows the parallel execution of many workflows.

This is NOT a benefit of Intent Manager because workflows are not related to intents. Workflows are sequences of tasks that can be executed on NSP using Workflow Manager.

The statement that best describes the Intent Manager application is: "It generates and validates the configuration of the network." Intent Manager is responsible for collecting the user's intent, verifying the user's input, and converting the user's intent into a device-specific configuration. It uses a high-level language to abstract the network complexity, enabling the network operator to define intent in simple terms. Once the intent is defined, Intent Manager automatically generates a device-specific configuration for each network element. It then validates the intent by checking the network's current state against the user's desired intent. If there is a mismatch, it will take corrective action to bring the network to the desired intent state.