Users can adjust the elastic public network IF or shared bandwidth through the flexible bandwidth function of the elastic scaling service. Which of the following policy types are supported when…

Question

Options

• ACycle strategy
• BTiming strategy
• CResource strategy
• DAlert strategy

• A
  85% (33)
• B
  15% (6)

Explanation

Elastic scaling bandwidth policies support three types: Cycle strategy (A), which triggers scaling actions on a repeating schedule such as daily or weekly intervals; Resource strategy (C), which adjusts bandwidth based on the current state or utilization of associated resources; and Alert strategy (D), which triggers scaling actions in response to monitoring alarms when metrics like bandwidth usage cross defined thresholds. These three together cover time-driven recurring actions, resource-driven conditions, and metric-driven alerts.

Option B, Timing strategy, is the distractor. While a one-time fixed-time schedule sounds plausible, elastic bandwidth scaling policies do not include a standalone single-occurrence timing type as a distinct policy category -- recurring schedules fall under the Cycle strategy instead.

Memory tip: Think "C-A-D" -- Cycle, Alert, and the odd one out "resource" rounds out the three. The one NOT supported is a pure one-shot timing trigger, because bandwidth scaling is designed around patterns (cycles), conditions (resources), and events (alerts), not single scheduled moments.

No community discussion yet for this question.