a system token is a string that is used to authenticate requests to the NSP REST API.  A system token can be obtained by sending a POST request to the /token endpoint with a valid username and password 1 . a system token is valid for  60 minutes  before expiring.  After expiration, a new system token must be obtained by repeating the authentication process 2 .

Intent is a high-level description of the desired outcome or state of the network. It allows users to specify what they want to achieve rather than how to achieve it. The intent is then translated into network configurations and policies that are used to configure the network infrastructure. Intent-based networking provides a higher level of abstraction than traditional network configuration methods, making it easier for users to specify their requirements and automate the configuration process.

NSP APIs allow for supervision of network elements, help with the definition and activation of network services, and allow for an OSS and NSP server to talk to each other. However, they do not support GraphQL, which is a query language for APIs. 

According to Nokia NSP IP Network Automation Professional guide, NSP APIs support REST/RESTCONF, SOAP/XML and GraphQlll, and help with the definition and activation of network services, and they also allow for supervision of network elements and an OSS and NSP server to talk to each other. Therefore, statement B is false as it states that NSP APIs support Kafka which is not mentioned in the guide as a supported API.

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 CLI 2 .

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 Engineering 2 .

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 equipment 3 .

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 management 2 .