Which combination of strategies ensures cost efficiency while maintaining performance in IBM Cloud? (Select two)

Question

Options

• AUtilizing IBM Cloud Auto-Scaling to dynamically adjust resources
• BPurchasing reserved instances for predictable workloads
• CDeploying all resources in a single region to simplify management
• DScaling up instances manually in response to monitoring alerts

• A
  78% (49)
• C
  6% (4)
• D
  16% (10)

Explanation

Auto-Scaling (A) and Reserved Instances (B) together cover the two core cost-efficiency patterns: dynamic resources for variable workloads, and discounted pricing for predictable ones. Auto-Scaling ensures you never pay for idle capacity during low-demand periods, while reserved instances give you significant cost savings (compared to on-demand pricing) when you can commit to consistent usage. Option C is a trap - single-region deployment creates a performance bottleneck and single point of failure, which hurts both performance and resilience with no real cost benefit. Option D (manual scaling) is slow, error-prone, and introduces human latency into what should be an automated response, making it neither cost-efficient nor performant under sudden load spikes.

Memory tip: Think "auto + commit" - automate the elastic part (A), commit upfront for the stable part (B). If a choice involves human intervention or architectural shortcuts, it's wrong.

No community discussion yet for this question.