Which options would be selected to manage the lifecycle of a version of a Product?

Managing the lifecycle of a Product version in IBM API Connect involves transitioning it through states such as published, deprecated, and retired. A critical part of this process is migrating existing subscriptions from an older version to a newer one. The "Set migration target" option is the specific function used to facilitate this transition. By setting a migration target on a deprecated or retiring Product version, you enable application developers to seamlessly move their subscriptions to the new, superseding version, thus managing the end-of-life phase for the old version.

1. IBM API Connect 10.0.x Documentation

"Migrating subscriptions to a new Product version": This official document states

"When you have created a new version of a Product to supersede a previous version

you can migrate any subscriptions from the old Product to the new one. To enable migration of subscriptions

you must first set the migration target on the old Product." This directly links "Set migration target" to the version lifecycle.

2. IBM API Connect 10.0.x Documentation

"Deprecating and retiring a Product": This section details the lifecycle states and notes

"When you deprecate a Product

you can specify a target Product to which application developers can migrate their subscriptions." This confirms that setting a migration target is a core part of the deprecation lifecycle stage.