Which of the following is NOT supported by the Workflow Manager out of the box?

The Nokia Network Services Platform (NSP) Workflow Manager (WFM) is an engine for automating network operations. Out of the box, it is equipped with a suite of adapters and tasks designed specifically for network device and service interaction. These include native support for REST/RESTCONF APIs, CLI command execution on Nokia (SROS) and third-party devices, and TL1 for optical equipment integration.

Executing arbitrary shell commands on a server's operating system is considered a general-purpose IT automation task, not a core network management function. While this capability can be added by developing a custom Java task (a "bean"), it is not provided as a standard, pre-packaged feature within the Workflow Manager.

A. REST/RESTCONF APIs: This is incorrect. WFM has built-in tasks to act as a client for REST/RESTCONF APIs, which is essential for interacting with modern network elements and controllers.

B. Optical integration using TL1: This is incorrect. WFM provides a dedicated TL1 adapter out of the box to automate and manage optical transport network elements that use this protocol.

D. CLI command execution on SROS and third party routers: This is incorrect. The CLI adapter is a fundamental, out-of-the-box component of WFM, enabling automation of device configuration via command-line interfaces.

1. Nokia Network Services Platform (NSP) Workflow Manager Guide, Release 23.5

Reference: Chapter "Workflow task reference".

Details: This chapter provides a comprehensive list of all out-of-the-box tasks available in the Workflow Manager. It details tasks for CLI (cli:run), REST (rest:post, rest:get, etc.), and TL1 (tl1:send). There is no corresponding built-in task listed for executing operating system shell commands.

2. Nokia Network Services Platform (NSP) Programmer Guide, Release 23.5

Reference: Chapter "Workflow custom Java tasks".

Details: This section explains that for functionality not covered by the standard tasks, developers can create custom Java beans. Executing a shell command would fall into this category of custom development, confirming it is not an "out of the box" feature. The guide states, "You can create custom Java tasks to perform functions that are not available in the standard WFM task library."