Explanation
Intent Types have four life-cycle states: Draft, Released, Phased-Out, and Deleted. The Created state is not a life-cycle state for Intent Types; instead, it is an intermediate state used to create an Intent before it is moved to a life-cycle state.

Explanation
Good coding principles aim to make the code more maintainable and easier to debug. Offloading code and using logging to debug code are both good coding principles, as they make the code more efficient and easier to debug. Adding notes and comments into code is also a good coding practice, as it makes the code more readable and understandable. However, using hard coded values is not a good coding practice, as it makes the code more difficult to maintain and debug.

Explanation
This syntax assumes that there is a previous task that returns an object with an attribute named rtt that contains the round-trip time value1. The expression <% task().result.rtt %> evaluates to this value and assigns it to the variable rtt in the workflow context

Explanation
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.

Explanation
Service Fulfilment API does not provide alarm monitoring; rather, it allows customers to quickly and easily order and provision services from a single interface, allowing for increased service agility and reduced human error.
According to the Nokia NSP Service Fulfilment API User Guide, Service Fulfilment API offers the following benefits:
Increases service agility by providing a programmable interface for automated service provisioning and management, allowing network operators to quickly respond to customer demands and network changes.
Reduces human errors by automating the service provisioning process, which minimizes the risk of manual configuration errors and improves service quality.
Allows multi-vendor service provisioning by providing a vendor-agnostic interface that supports different types of network equipment and technologies, reducing vendor lock-in and enabling greater network flexibility.