An Adobe Commerce on cloud infrastructure project is experiencing high traffic, and the merchant wants to ensure the site can handle load spikes without manual intervention. The project is on a Scaled

Question

Options

• AAuto Scaling
• BFailover Cluster
• CLoad Balancing
• DManual Upsizing

• A
  82% (32)
• B
  5% (2)
• C
  10% (4)
• D
  3% (1)

Explanation

Auto Scaling is correct because Adobe Commerce on cloud infrastructure's Pro Scaled Architecture plan includes built-in Auto Scaling functionality that automatically provisions and de-provisions web nodes in response to traffic load - no manual intervention required, which directly addresses the merchant's need.

Failover Cluster (B) is about high availability and redundancy during failures, not dynamic resource allocation in response to traffic spikes. Load Balancing (C) distributes existing traffic across available servers but does not add or remove resources - it requires something to balance to. Manual Upsizing (D) is the opposite of what the question asks for; it requires human intervention and doesn't respond automatically to spikes.

Memory tip: Think "Auto = Automatic, Scaling = size changes." The word "automatically" in the question is your direct clue - only Auto Scaling has "auto" baked in. The Scaled Architecture (Pro) plan name itself hints that scaling is the core feature being tested.

No community discussion yet for this question.