Which combination of strategies is critical when transforming and migrating complex workloads to containers on IBM Cloud? (Select two)

Question

Options

• AAssessing the compatibility of existing applications with containerized environments
• BMigrating all workloads without modification to speed up the migration process
• CLeveraging IBM Cloud Kubernetes Service for orchestration
• DIgnoring security and compliance considerations during migration

• A
  84% (38)
• B
  4% (2)
• D
  11% (5)

Explanation

A (Compatibility Assessment) is correct because migrating to containers requires evaluating whether existing applications are stateful/stateless, have hardcoded dependencies, or rely on OS-specific features - skipping this step causes failures post-migration. C (IBM Kubernetes Service) is correct because IKS provides the orchestration layer needed to manage containerized workloads at scale, handling scheduling, scaling, and availability in IBM Cloud's ecosystem.

B is wrong because "migrate without modification" (lift-and-shift for containers) is a common anti-pattern - containers often require refactoring to be truly cloud-native. D is wrong because security and compliance are non-negotiable during migration, especially in regulated industries where IBM Cloud's compliance certifications (SOC 2, HIPAA, etc.) must carry through to workloads.

Memory tip: Think "AC = Assess then Containerize" - you must assess compatibility first (A), then containerize with proper orchestration (C). Anything that says "skip steps" or "ignore security" (B, D) is always a distractor on cloud migration questions.

No community discussion yet for this question.