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

According to the NSP Network Services Platform Release 20.9 User Guide1, the attribute of the target-component that determines the component name displayed in the UI is i18n-text.

The i18n-text attribute specifies a key for a localized text string that is displayed as a label for this component in the UI. The actual text string is retrieved from a resource bundle file based on the user's locale.

For example, if i18n-text is "Port Id", then the UI will display "Port Id" as the component name.

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.

The main sections of an abstract YANG module file are arguments and statements.

An argument is a string that provides additional information about a statement. A statement is a keyword followed by an argument and optionally enclosed by braces ({ }) containing substatements.

For example, an abstract YANG module file could start with:

module ibn-intent { namespace "urn:nokia.com:ibn:intent"; prefix ibn;

This defines the module name, namespace and prefix as arguments for the module, namespace and prefix statements respectively.

The script-content.js file contains all the back end implementations required for Intent configurations to be performed.

The script-content.js file is a JavaScript file that defines the logic for creating, updating, deleting and synchronizing intents. It also defines the validation rules and error handling mechanisms for intents.

For example, a script-content.js file could contain:

function createIntent(intent) { // logic for creating an intent }

function updateIntent(intent) { // logic for updating an intent }

The Framework file contains helper functions that can be leveraged by the scripts of many different

Intent types.

The Framework file is a JavaScript file that provides common utility functions for Intent operations. It is located in the /opt/nokia/nsp/intent/scripts directory on the NSP server. It can be imported by other script files using the require() function.

For example, a Framework file could contain:

function getNfmpTemplate(templateName) { // logic for getting an NFM-P template by name }

function getMdTemplate(templateName) { // logic for getting an MD template by name }

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.

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

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