For a complex workload that requires transformation before migration, what is a pivotal step in the migration process?

Question

Options

• ADeciding to keep the application on-premise due to its complexity
• BImmediately migrating the workload without assessing its architecture
• CConducting a thorough assessment and planning phase to identify necessary changes
• DChoosing the same environment in the cloud as on-premise for simplicity

• A
  8% (2)
• B
  16% (4)
• C
  72% (18)
• D
  4% (1)

Explanation

Conducting a thorough assessment and planning phase (C) is the pivotal step because complex workloads requiring transformation cannot simply be "lifted and shifted" - you must first understand the existing architecture, dependencies, data flows, and what needs to change before any migration work begins.

Why the distractors fail:

• A is wrong because complexity alone isn't a reason to avoid migration; it's a reason to plan carefully.
• B is wrong because skipping assessment on a complex workload is a recipe for failure - you'd be migrating something you don't fully understand.
• D is wrong because replicating an on-premise environment in the cloud defeats the purpose of transformation and misses opportunities for modernization.

Memory tip: Think of it as "measure twice, cut once" - the more complex the workload, the more critical the assessment phase becomes before touching anything.

No community discussion yet for this question.