What factors should be considered when designing a migration solution to move complex workloads to containers on IBM Cloud? (Select two)

Question

Options

• AThe specific cloud region to use for cost efficiency
• BThe compatibility of the workload with containerized environments
• CThe brand of hardware the containers will run on
• DStrategies for container orchestration and management

• A
  18% (7)
• B
  73% (29)
• C
  10% (4)

Explanation

When designing a migration solution for complex workloads to containers, workload compatibility (B) is essential - not all applications are container-ready, and factors like stateful dependencies, OS-level requirements, or legacy APIs can block or complicate containerization. Container orchestration strategy (D) is equally critical because managing containerized workloads at scale (scheduling, scaling, networking, health checks) requires deliberate design decisions, typically around platforms like Kubernetes or OpenShift on IBM Cloud.

A is wrong because while cost efficiency matters broadly, the specific cloud region is an operational/billing concern, not a core architectural factor in designing the migration solution itself. C is wrong because containers are hardware-agnostic by design - the entire value of containerization is abstracting away the underlying hardware brand, making it irrelevant to migration design.

Memory tip: Think "Can it run? Can we manage it?" - Compatibility (B) asks can the workload run in a container, and Orchestration (D) asks can we manage containers at scale. Those two questions drive migration design; region and hardware are distractors that sound relevant but operate at the wrong level of abstraction.

No community discussion yet for this question.