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

Question breakdown

Tests

Manage Product version lifecycle

Difficulty

Easy

Key idea: Setting a migration target on a Product version lets subscriptions move to a superseding version as the old one is deprecated or retired.

How to reach the answer

1. The clue is 'lifecycle of a version of a Product', which concerns moving between versions.
2. Lifecycle actions on a Catalog Product include publish, deprecate, retire, supersede, replace and set migration target.
3. Set migration target points an older version at its successor so subscribers can migrate.
4. Rate limit, burst limit and endpoint are Plan or API settings, not lifecycle actions, so B is correct.

Each option

• AIncorrect. Endpoints are configured at the API or Catalog level, not as a Product lifecycle action.
• BCorrect. Set migration target is a Product lifecycle action that links an old version to its replacement for subscription migration.
• CIncorrect. Burst limits control short-term traffic within a Plan and do not manage version lifecycle.
• DIncorrect. Rate limits govern call volume per Plan, not version transitions.

Common trap: Rate and burst limits are configured on Products and Plans, so they can seem like 'Product management' options even though they have nothing to do with lifecycle.

In practice: When releasing v2 of a Product, providers set v2 as the migration target on v1 and then deprecate v1. App developers can then move their subscriptions before v1 is retired.

Remember: Version lifecycle uses the deprecate/retire/supersede/replace/set-migration-target actions, not throttling settings.

Drafted with AI assistance and checked against the answer key.