How are Knowledge Accelerators deployed?

IBM Knowledge Accelerators are deployed (installed) from the Cloud Pak for Data marketplace. This is the designated central location for users to discover, access, and add industry-specific accelerators to their Cloud Pak for Data environment. Once an accelerator is added from the marketplace, its content, such as business terms and data classes, can then be imported into Watson Knowledge Catalog, typically via an API call, to populate the governance catalog. The initial deployment step, however, is acquisition from the marketplace.

A. Deployed as part of the sample assets. Knowledge Accelerators are comprehensive, licensed industry models, not simple sample assets included by default for demonstration purposes.
C. Deploy by IBM support upon request. Deployment is a self-service task performed by an administrator through the Cloud Pak for Data user interface, not a manual process requiring intervention from IBM support.
D. Deploy from the IBM Knowledge Accelerator API. The API is used to import the content of an already installed Knowledge Accelerator into a catalog, not for the initial deployment or installation of the accelerator component itself.

1. IBM Cloud Pak for Data 4.8 Documentation

"Knowledge Accelerators":

Section: Installing Knowledge Accelerators

Content: "You can install the Knowledge Accelerators for your industry from the Cloud Pak for Data marketplace. To install a Knowledge Accelerator

you must have the Manage catalog permission. 1. From the navigation menu

select Marketplace. 2. Select the Knowledge Accelerator that you want to install." This explicitly states the marketplace is the source for installation.

2. IBM Cloud Pak for Data 4.8 Documentation

"Importing Knowledge Accelerator items":

Section: Importing Knowledge Accelerator items

Content: "You can import the Knowledge Accelerator content by using the importitems API call." This confirms the API's role is for importing content after the accelerator has been made available

distinguishing it from the initial deployment step.