What is an essential consideration when designing a migration solution to migrate data to DBaaS on IBM Cloud?

Question

Options

• AEnsuring that the database uses the same language as the application code
• BMatching the specific features and performance characteristics of the target DBaaS with the
• CChoosing a database solely based on the lowest cost option
• DMigrating all data at once to minimize the migration window

• A
  6% (2)
• B
  71% (25)
• C
  6% (2)
• D
  17% (6)

Explanation

Matching the target DBaaS's features and performance characteristics to your workload requirements (option B) is the cornerstone of any migration plan - a mismatch in capabilities like indexing, replication, or throughput limits will cause failures or degraded performance that no amount of tooling can fix after the fact.

Why the distractors fail:

• A is a misconception - databases communicate via drivers/connectors, not the application's programming language, so language alignment is irrelevant to DBaaS selection.
• C is a classic pitfall; choosing only on cost ignores fit-for-purpose, which leads to re-migration costs that far exceed any initial savings.
• D is operationally risky - a "big bang" migration maximizes downtime and rollback complexity; phased migrations are the industry standard for minimizing risk.

Memory tip: Think of B as the "Cinderella principle" - the DBaaS must fit your workload (features + performance), not just be available or cheap. If the shoe doesn't fit, the whole migration fails.

No community discussion yet for this question.