When identifying tools and methods to migrate workloads to IBM Cloud, which approach is recommended for stateful applications?

Question

Options

• AStateless migration tools that do not consider the application's data
• BCustom scripts written from scratch for each migration
• CTools that support both application and data migration for consistency
• DAvoiding the migration of stateful applications to the cloud

• A
  7% (2)
• B
  3% (1)
• C
  80% (24)
• D
  10% (3)

Explanation

Stateful applications depend on persistent data (databases, session state, files), so any migration tool must handle both the application logic and its data together - otherwise you risk inconsistency, data loss, or broken application state after the move. Option A is wrong because ignoring data during migration would leave a stateful app broken or out of sync. Option B is impractical and error-prone - reinventing migration logic from scratch for every workload is inefficient and introduces unnecessary risk. Option D is simply incorrect; stateful applications are routinely and successfully migrated to cloud environments using the right tooling.

Memory tip: Think "stateful = state must travel with it." If the tool doesn't move the data and the app together, you've only moved half the problem.

No community discussion yet for this question.